Is there a best practice or best suggestion for having a field which stores the # days based on another field in the table reflect accurately in the UI without requiring a job scheduler to update daily - particularly for header tables?
For example, if we wanted to store the # days since a payable was posted, is the only way to do this currently via a job scheduler which runs daily to update a # Days field defined on the payables header table? Or, is there possibly another way to do this so we can have the field visible in both List View and HD Detail View (the value does not necessarily have to be available in logic blocks).
I know we can do this type of thing with a work field in an advanced list load event and on form init of a detail view where we set it in logic, but when you have the field on a header table, is there a way to set that field at run time in the list view to avoid having a daily job that runs to update? Or is there another way to keep the field in sync that you can suggest other than maybe creating an advanced list for the payables header table?
If anything I have said is unclear, please let me know.
As far as I know, there is not currently a way to store data on the table that will dynamically display Days Since.... There is, however, an equivalent to the advanced list’s Form Is Initialized action.
Using the event action Load Data On List Form on your Header application, you can populate a work field with that information. This action will work for all records displayed in the list view, so if a user is displaying 25 records, the associated action will run 25 times. Because of this, it’s best practice not to perform any database operations for performance purposes, but you can treat the Load Data On List Form action like a calculated column where you invoke logic to perform your calculations.
The same action could be taken for the Detail application inside of a particular record, as could Form is Initialized.
If you want something like this when making inbound endpoint calls to Nextworld (instead of only in the UI), you could use the outputProcessingLB feature. It was released in 24.2 - see attached release note RN-24.2-[Nextbot]-5560
