Skip to main content

I have a dsp which saves the data as part of the postactivate (setstate?) trigger. The data is held in non-db (DSP) subtypes of the entity, and is saved and re-loaded using struct with /reconnecttags. Just before the websave, the entities all show as $occstatus "est", and $occmod is 0. 

Following the webload in the next preactivate, the $occstatus is "", and then during the reconnect they all become "mod" and $occmod  = 1. I thought webload & reconnect preserved the modification status of the entities. 

Only some actions on the page are capable of modifying the relevant items (the others are navigation etc) and I'd obviously like to minimise the number of times (and time spent) saving unchanged data. 

Am I wrong that the state should be preserved? What could I be doing wrong to cause it to change? (I've watched the reconnect through the debugger, and there's a formatfordisplay trigger, which does nothing, then the postdeserilaise trigger and in between the two the status changes. )

Alternatively, is there any sane way to reset the items on or post load, so I can spot them being modified again. 

Regards, 


Iain

Be the first to reply!