TracerPlus needs temporary fields/variables

[Tim Harvey]

The only way to currently retrieve and store data in a session is to create a permanent field in your session. As an application gets more and more complicated with many sessions the developer is constantly having to lookup information in other sessions. The problem is that to store this information for use in the current form you have to create a permanent field. This causes the database to grow very large (and breaks every rule for good database design) because each session has multiple copies of data from other sessions. There should be someway to indicate that you want a field to be temporary, It works just like a regular field except when the record is submitted that data is lost and not stored with the session table.

 

[Dan Peluso]

Hi Tim,

This is true. We do not (yet) have the concept of variables/non-saved data. You could override the standard Submit(Save) action with a button that executes custom SQL to only INSERT the field values that you want to save and simply bypass the TracerPlus standard Submit action altogether.

 

[Tim Harvey]

Yes, I thought about that but then if the user hits done and the form has been changed it prompts them to save and if they hit yes then it would perform the standard Submit. Unless there is a way to emulate the Done functionality - something like if FormChange then display dialog box with save message - yes performs a submit button click and no cancels and goes home. But that would be for the future when there is an Dialog box option for an Action.

 

[Dan Peluso]

In that case, you should be able to turn the Confirmation property to FALSE for the Done button. This will disable the prompting for "Save Data Yes/No"