If you recall, transactional surveys are used as a means to collect feedback after a specific transaction - such as a support ticket, onboarding, project, event etc. It is differerent than NPS and is called CSAT in many circles. When using transactional surveys, it is expected to associate a transactional object such as the link to the support ticket, or the onboarding project specific to the customer being surveyed.
- While working with Survey 2.0, and selecting the survey type = transactional in the dropdown, I tried to look for an object to associate the survey with, which in this case was an object called 'Support Tickets' in salesforce. I could not access this object as in it did not show this object in the list of the objects that I can use in my transactional survey.
- So my first instinct was to see if I really have the permissions to access this object at all. And so I went to the report builder and to my surprise I was able to add that object in the report builder and build reports off it. This was puzzling - how can I access one object from one functionality of the product and not other?! Any guesses??? I bet you are wrong.
- The reason was that in Survey 2.0, the system looks for the permission from the OAUTH user and not the Logged in user. If the OAUTH user have the permission to access the object, only then will it be visible to the logged in user. So in this case, the OAUTH user A was different and that profile did not have permissions to access the Support Ticket object in salesforce. Even though I was logged in as user B, who had the permission to access this object, it was being overruled by the permissions of the OAUTH user.