Apex Code Development You need to sign in to do that
Don't have an account?
VF and SF Sites public access to Standard Object Update.
I started a thread over on the Sites board but there doesn't appear to be much traffic over there so I'm posting a link here--
I researching doing a SF Site in VF that allows a public access user to both create a Cost Proposal in Opportunity and come back later an edit it.
Of course the sticky wicket is that Sites public access allows only Insert to Opportunity and OpportunityLineItem and not Update.
I do have what I think is a viable work around and post it with screenshot and sample code in the other thread.
I'm wonder if any other VF developers have run into this issue and found any other work arounds.
Feel free to comment here are on the other thread. (Might be better on the other other thread as that's where the details are.)
-Ken
See the suggessions below,
Topalovich
Option 1: include an authentication mechanism so that licensed users with the appropriate CRUD permissions in their profiles can make the change.
Option 2: abstract the process by writing values to a custom object, and then have a process at the system level (trigger or class) update the appropriate field on the standard object using the values written to the placeholder object.
https://developer.salesforce.com/forums/ForumsMain?id=906F000000099oJIAQ
Regards,
Ashish
Option 2 works but I like my other work around better.
The other work around is to either use input tags attached to non-sObject merge variables or attache merge variables to dummy Opportunity objects that don't have the ID filled in. I've observed that it appears it is VF inputField tag supporting the read-only limit. Either don't use inputField or use it with a dummy Opp that hasn't been saved and copy the values to a new record.
https://developer.salesforce.com/forums/ForumsMain?id=906F00000009B3YIAU
https://developer.salesforce.com/forums/ForumsMain?id=906F00000009B3YIAU
Thank you very much for updating this over the board.
Regards,
Ashish