Sorry, either the data doesn't exist or you don't have access

[Diogo Luz]

Hello,

I have a record producer that allows users to submit a new Demand via portal, for them, or in behalf of another user.

When the user submits a demand for himself it works fine, in the end there is a page confirming it was submitted and a demand number is shared.

But when the user is submitting for another one a message appears "Sorry, either the data doesn't exist or you don't have access" (attachment) and nothing else is showing. The demand itself is submitted, but users normally re submit a second one because they think an error occurred.

I'm kind of lost on what's happening, is it ACL related or maybe it's a widget issue? How can I solve this situation?

Thanks.

[John Gilmore]

@TD11 its most likely an ACL on the table or a security policy that restricts read permissions. If your experience is exactly as described by the original poster then its likely there is a rule that allows read access only if the session user is the same user the demand was submitted for. This would explain why users see it when they submit it on their own behalf but not when it is submitted on behalf of someone else.

If you want the submitted to be able to view records they submit then you would need to update the rule to also allow read access if the created_by field matches the session user. If you are getting a very similar message to the orginal post that state the record doesn't exist or you don't have access then its likely to be an ACL associated with the table. If the message is more vague and just says you don't have permission then i would tend to look towards a security policy or ui policy.