More frequent or user initiated API query table rebuild
C
Cody Flagg
To add to this, this only seems to be required when we commit app updates by using a PUT on the Forms endpoint of the REST API. I know most other users might not follow this scheme, but we have Development (DEV), Certification (CERT), and Production (PROD) copies of our applications to stabilize our end user's experience with training and data collection. We implement and test out significant changes to DEV, then promote those changes via the REST API so that we don't commit typos from manual changes to our three versions.
A PUT on the the Form endpoint appears to create some kind of 'lag' in (a) how a form appears to the end user (e.g. new fields or changing the name of an existing field won't appear) and (b) how records appear to end users (e.g. the records disappear from the Map, Split, and Table views as well as in Record Links). This lag only seems to be fixable via a request to the Fulcrum Help Desk for a "query table rebuild".
I think it would be perfectly fine to have an SLA on this endpoint for the query table rebuild such as "query table rebuild will initiate X days after PUT" or something like that, if it were to be integrated into the rest of the process.
Thanks!