Hello Salesforce community,
I have 2 vf pages, and 1 vfp component.
Each page wraps the same component. The only difference in the pages is that one apex:page tag has readOnly="true" whereas the other page uses readOnly="false".
The visualforce component has
sforce.connection.updateroutines defined within it which ideally would be toggled off when the page's readOnly="true". That seems to not be the case so I'm looking for an alternative way to cleanly deliver a page that reuses my component but disables all sforce.connection.update calls.
The confusing part is that despite readOnly="true" the sforce.connection.update DML updates are somehow allowed to occur (for what its worth im a system admin)
Given the setup above and without changing Profile object or field security, how can I cleanly/more-fully disable DML from occurring in the component on the page that has readOnly="true"?
Here are related articles, but I still am unsure why my readOnly="true" hack is not disabling DML.
- DML Statement from @readonly page
Thanks in advance for any ideas / suggestions,