VOLUME LXIV               12/15/2020

Client Showcase

By Dottie Worster, Media Manager

Kevin is the owner of Super Source DC, a restaurant supplier of cleaning and maintenance products and services to the hospitality industry.  Super Source DC is based out of Springfield and serves the greater DC community.  Kevin’s workers spend time in the field delivering products and tracking inventory as well as managing customer accounts using iPads.

 

As his business grew, Kevin decided it was time to find a better solution than just Excel spreadsheets and cookie cutter options.  He found Ninox, and The Nioxus Learning Channel.  After watching videos he decided the database needed to be in the hands of Nioxus experts.  After his initial meeting, he had about a two week turn-around time on the prototype for his project.  Kevin was glad to have finally found a solution that wasn’t going to cost exorbitant fees or require a sacrifice in quality or time.

 * Screenshot of an equipment dashboard for SuperSource DC

Nioxus is in Phase 1 of building a Ninox solution to cover accounting, customer management, and inventory that can run seamlessly on iPads while workers are in the field.  Kevin has already seen the benefits of time and financial savings by using the Ninox solution to organize and track every facet of his business experience. 

“Nioxus took the time to get me everything I wanted, in the timeframe I needed it.  I never heard “we can’t”.  It was a painless process; they are a great team to work with, delivering a high quality product with a quick turn-around time.”

-Kevin D, SuperSource DC

Planning On Attending Next Week's Learning Lab On Arrays?

Check Out This Article From Last Month

"I think of arrays as multiple data elements fitted into a single field. The data elements are separated by commas. An array can store any number of values from just a few to hundreds or even thousands..."

ReportsPlus

Report Parameter Filters

Watch Video

ReportsPlus

Using Parameters as Dashboard Filters

Watch Video

Nioxus Today

By Amelia Neighbors, GM Global Operations

Can you believe it is already mid-December? Time flies when you are building Business solutions, so Nioxus is busy as ever..

We strive to always grow and help others; speaking of – the learning lab last week was full of vibrant discussion and I think everyone learned something new, even Andy! We are so happy and proud to be able to host the global Ninox community each week and delve into the common and uncommon issues that people are seeing around the tools as we build our understanding of low code data management.

We continue to learn from all of you and hope to continue bringing value to your experience- thank you for being a member of Team Nioxus, and we look forward to seeing you soon – join us as we get to some advanced solutions and revisit some basics. We will be off for the next two weeks, so get your questions in via emails to our support desk or questions to your Nioxus rep. We’ll get back by the next couple of weeks – so see you then if we don’t hear from you before then.

Wishing you and yours a warm and joyful holiday!

This Week in the Learning Lab

Be sure to join Thursday on the 17th at 12:00pm EST for our Learning Lab on working with arrays!

Did you know that Nioxus has built over 125 templates which are available to all Standard, Deluxe and Premier Nioxus members?

Just Jim

By Jim Harris, The Stargazer

No  Stargazer this week, just Jim

This week as I was grabbing the Christmas storage (to decorate the home and yard), I began to think of all that has happened here at Nioxus. The first and most important was the “changing of the guards” so to speak. We went through some transitions with people to bring Nioxus to the next level. There are some members of the team that many of you already know, but there will be plenty of fresh faces as we grow. Everyone here at Nioxus has a specific role and each one is as important as the next.

We also had to make some hard decisions in how we were going to continue this path and vision of Nioxus. The foundation within Nioxus is the same but as we continue to grow, we still want to maintain the core standards in who and what we are to make you, our customers, happy.

As the System Testing Manager/QA,  I see things others may not see. What I love the most is that I get to work  with this excellent team.  I have to say, without a doubt, this is a place to work where each individual person in the team will help another when needed. This is not only a team of co-workers, but also a family.

In the spirit of the upcoming holidays, I want to honor the people I work with for all the hard work they do. And when I mean hard work, I mean 16 hours straight and sometimes through the entire night and into the early mornings. Without these people, Nioxus would not be what it is today. SO if you would also like to thank them,  please send an email to Jim@nioxus.com

Developer Tips of the Week

Ninox & Calendar Plus Tips

Build Better Back Buttons

By Jennifer Neighbors, Senior Consultant

Traditionally the BACK button on a form takes users to the most recently viewed screen. In Ninox, however, screens tend to layer on top of one another instead of forming a linear direction. Recently I’ve been working on a large project with lots of modules and tables where the user can easily get lost in the stack. Users of my database won’t be familiar with Ninox and won’t have any training in how to click on the “X” in the corner of the screen to close it. I decided to help the user go back – not to the previously viewed screen – but instead to where I think they are likely to want to go. And I wanted to use a button to do it, so novice users won’t be confused.
 
To do that, I needed to sort out Ninox’s methods of closing forms and navigating to others. Closing forms can be confusing because behavior of the same function can be different depending on how many screens are stacked underneath. Let’s take a look.
							
					closeRecord()				
			

This function closes a screen and, when used with a button, allows the user to press a button and return to the screen underneath the current screen. But what if there are no open screens under the current screen or what if
there are more than more than one? It doesn’t offer any real control over what the user sees when it is executed. All it does is close the top-most form and it provides a great alternative to the “X” close screen icon.

I wasn’t satisfied with this solution. In my large database, the user often has three levels of interaction. For example I have an Events Management dashboard at the Events module level where the user may search records and add new ones, an Events table that allows the user to create a detailed record about an Event, and nine more child tables from that which allow the user to define other things such as Attendees, Entertainment and Vendors.

In short, I have a grandparent table, a child table, and several grandchild tables. How would I allow the user to close any of these and navigate back up the stack?

							
					closeAllRecords()				
			

This function is very like the closeRecord() function, except that it closes each and every underlying record. It still doesn’t offer much control over where the user eventually lands, but it is very effective at closing all records that the user has left open while working. So far, so good. What about opening the screen the user wants to go to? There are a couple of options for that and when they are combined with the closeAllRecords() function, they provide a great solution.

							
					let xEventNum := number(EVENT);
closeAllRecords();
openRecord(record(Events,xEventNum))				
			

This code in a button’s on click function not only closes all the underlying open records, it also takes the user to a specific record in a specific table. In this case it opens the Events form for the event that the user is currently working with. The button’s name is EVENTS, so the user can easily see that to go “back” to their main form, which is Events, they simply have to press that button.

I have another button named “HOME”. You can guess what that button does, right? It takes the user to the grandparent level – the dashboard for the events module where they began when they searched for or added a new Event. Here’s the code for the HOME button:

							
					closeAllRecords();
openTable("Event Management", "Events")				
			

I use the openTable method here because I’m navigating to a dashboard. It doesn’t need to open a specific record in the table. It merely has to go to the table and expose the view I want the user to see.

My grandchild table forms all have EVENTS and HOME buttons allowing the user to close up and go back to a central location they have been to before. My Events table form only needs the HOME button so users can go up the stack to the dashboard. That’s it. Once I sorted these few functions, I gained a better sense of how to help my users go “BACK” and my novice users now have a good sense of direction and control.

Jennifer welcomes feedback and can be reached at jennifer@nioxus.com

Copyright 2020 © All Rights Reserved.

All logos, trademarks and names are the protected property of Nioxus Corporation or their respective owners.

“Ninox,” “Ninox Database” and the blue Ninox owl eye logo are the property of Ninox Berlin and are used with permission.