December 2016 Release Notes


Dependent Dropdowns will allow end users to enter information faster and more accurately.  Let’s use an inventory management use case as an example.  In this scenario specific parts only come from one vendor.  While writing a PO to order more parts, TrackVia can now filter parts for only those provided by the vendor on the PO.  That means, no more guessing or accidentally picking the wrong part!

To set up the dependency, admins will go from the form designer and edit the field they would like to filter.  (In the image above, the field happens to be a Multi-Select Widget).  

From the Form Designer, edit the field that is going to be filtered:

There is a new tab called “Rules”.  Select that tab:

In the “Create a New Rule:” drop down select “Apply Filter” and the below setup screen will appear:

There are 5 major elements on this setup screen to be aware of.  They are numbered in the image above and explained here accordingly:

  1. Conditional Filtering - Just as you can select specific conditions for show/hide rules, you can also apply specific conditions for when the dependency is active. “Always” will leave the applied filter criteria active at all times.

  2. Field to filter by - This is the field that will be filtering the choices.  In the current version of dependent dropdowns, only the Record ID of the table will be available. Be careful, this can get confusing as Record ID up the relationship chain (Parent, Grand Parent, Great Grand Parent etc.)  will all be available for filtering and may not reflect the field on the form that the users will be choosing.  

  3. Field that is being filtered -  This is the field that will be filtered.  In the current version of dependent dropdowns, only the Relationship Field will be available to be filtered.

  4. Preferred View - This selection will be more for permissions purposes.  And will only need to be selected from this screen in a handful of cases.

  5. Reference sentence -  The reference sentence is to help make it more clear as to what field is filtering what information and will automatically populate from selections made in 2 and 3.  The sentence in the above image states:  

“Show all Parts where [Parts] Link to Vendors is identical to [Vendors] Vendor ID”

That means: Show all parts from the parts table where the relationship to the vendor matches the Vendor ID that will be selected in the PO.

To learn more and get a more in depth tutorial, please visit the knowledgebase article here:

Here is a video for additional reference:


Maintenance Release
  • Maps Update: Allow users to type in an address instead of just the Lat/Long coordinates:

  • Copy/Highlight Calculated Fields: Users will now be able to copy and paste the values from a calculated field. This includes calculated fields and trigger fields. This does not include fields that have been marked as read only.

  • Added a Checkbox to enable/disable an App Script:

  • Allow support for empty placeholders and fixed some placeholder custom text issues:

  • App script import fixes

  • Drill Down on line charts fixes

  • Usability and error handling fixes

Product Release Notes

  1. App Script Constants!
  2. Entity Relationship Diagram Improvements
  3. Improved Lanes View!
  4. December 2018 Release Notes: Web Maintenance
  5. Custom Mail Settings!
  6. November 2018 Release Notes: Platform Maintenance
  7. October 2018 Release Notes: Maintenance
  8. Improved User Management
  9. Views & Quick Filter Updates
  10. July 2018 Release Notes: Maintenance
  11. June 13, 2018 Release Notes: Maintenance
  12. May 25, 2018 Release Notes: Sandbox Environments
  13. May 2018 Release Notes: Deprecating TLS 1.0 & 1.1
  14. April 23rd Release Notes: Maintenance
  15. April 18th Release Notes: Maintenance
  16. April 10th Release Notes: Maintenance
  17. March 2018 Release Notes: Maintenance
  18. February 2018 Release Notes: More Intelligent Saving & Other Notes
  19. January 2018 Release Notes: Maintenance
  20. December 2017 Release Notes: Offline Editing on Android
  21. November 2017 Release Notes: Timeline | Calendar and Conditional Formatting
  22. September 2017 Release Notes: Maintenance
  23. August 2017 Release Notes: Maintenance
  24. July 2017 Release Notes: Maintenance
  25. June 27, 2017: TrackVia Introduces Flows!
  26. May 22, 2017: TrackVia Apple Watch App
  27. May 2017 Release Notes
  28. May 5, 2017: Better Connectivity Handling
  29. April 2017 Release Notes
  30. March 2017 Release Notes
  31. March 27, 2017: Single Sign On
  32. February 23, 2017: Winter Polish
  33. February 2017 Release Notes: Session Timeouts
  34. January 2017 Release Notes: Number Display Options & Min / Max
  35. December 2016 Release Notes
  36. November 2016 Release Notes
  37. October 2016 Release Notes
  38. September 2016 Release Notes
  39. August 2016 Release Notes
  40. July 2016 Release Notes
  41. June 2016 Release Notes
  42. May 2016 Release Notes
  43. April 2016 Release Notes
  44. March 2016 Release Notes
  45. February 2016 Release Notes
  46. January 2016 Release Notes
  47. December 2015 Release Notes
  48. November 2015 Release Notes
  49. October 2015 Release Notes
  50. September 2015 Release Notes
  51. August 2015 Release Notes
  52. July 2015 Release Notes
  53. June 2015 Release Notes

Feedback and Knowledge Base