History of Changes
I am working on building a new CRM and Project management application for my company. I am pretty far along but one of the features of our old system that everyone liked and we are trying to keep is t...
Forum Discussion
With script it is possible to use a Text Append/Prepend Logging field to keep track of changes to other fields. Normally a logging field keeps track of changes to text input into the logging field. However, with script you can prevent human input into the logging field and instead arrange for other fields that are that are modified to be formatted and automatically inserted into the logging field.
There is actually a demo I created of this that if you are interested I will attempt to locate.
Found it here:
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=305
There is actually a demo I created of this that if you are interested I will attempt to locate.
Found it here:
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=305
BTW, you can use a Service Worker to log any changes you make anywhere in the application. For example, you can log all changes to a form, report or web hook definition. This is not an exaggeration - using a Service Worker is god mode for QuickBase.
The great part is that it works in all cases not just those few cases where you have "less than 10 fields to track".
Why bother with native Rube Goldberg Machine solutions which have arbitrary limitations and clunky setups when you can just use a Service Worker? Come on it is almost 2018!
The great part is that it works in all cases not just those few cases where you have "less than 10 fields to track".
Why bother with native Rube Goldberg Machine solutions which have arbitrary limitations and clunky setups when you can just use a Service Worker? Come on it is almost 2018!