We use a custom tab in Ticketing Set up to enter relevant show data for our ticketing staff. It's been our process for years, but our ticketing managers have noticed that if they enter/update a row on the custom screen and save it with the little floppy disk icon, and then go back to edit it without tabbing off and back on to the custom tab first, they get the below error and the updated data row doesn't save.
I've run some traces and the first edit does save to the table successfully. The second update also is formatted appropriately, and if I run it in SSMS while the window is still open I have no trouble. So it seems that the Infomaker object is holding something in memory and barking whenever we try to do a second update without refreshing the window.
The workaround is to just tab off and tab back on whenever in between changes, but when creating dozens of rows (hello Hamilton!), it is quite a nuisance. Any Infomaker wizards out there know what's happening here?
Thanks a bunch!
Nancy
Nancy,
I do not fancy myself an InfoMaker expert, so take these statements with more than a grain of salt, but I have dabbled in the InfoMaker world enough to know some of its eccentricities.
I do not believe that custom/InfoMaker screens pull the data again unless the screen itself is refreshed. I just ran a test in our database using profiler, and it looks like there is another select call between the two saves when I try to do it on a regular Tessitura InfoMaker based screen. Is there a way to add in a select call post save?
John
I could be wrong, but that looks like a REST API error triggered because the API server thinks the data was updated since you pulled it to display in the custom screen.
This in theory protects against someone else simultaneously updating the data, but it could mean either a time discrepancy between the client and the server or that some process (trigger, LP_CUSTOMER_RANK) is firing on the row before the save can complete.