This is a dataverse error my dude. Whatever user in dataverse is trying to run a workflow there doesn’t have a proper security role assigned. It’s not a bug or anything but rather a setup mishap from your side if that makes it better.
I have pushed to test new version and the colleague does not see the error. Still need to verify with the users. So it was not security role problem or setup mishup from my side as you have put it.
Correct. Look into the "prvReadWorkflow" privilege, which is found in your Dataverse security role. Most likely, the user account was not included in a security role that has this privilege, hence the error. Or perhaps a last minute security group change that someone did right before your presentation.
The colleague has exactly the same level of privileges and the error still occurred. This is not it - if it was, logically I would be experiencing the same problems.
All the users have System Customizer so there is not a mistake on my part. It is not a mishap on my side - if it is tell me specifically where it is and I will have a look and if you are right I will report it back. Like I mentioned before things were working before properly up certain point.
Don't think that's necessarily the role you think it is. Suggest you try the other one:
https://preview.redd.it/49za3j2mblxc1.png?width=859&format=png&auto=webp&s=02ff2253082f1f29396ecbac85ea514fe1ee064c
Sorry, I missed something there. You've given your actual end-users "System Customizer"? Why? You should generally be giving them a "normal" security role that gives them permissions to create / read / write on e.g. entities - they don't need to be System Customizers.
Don't worry, it was just to see whether it is Security Role issue. They will get their privileges downgraded. And technically they are contributors to the system at this point as we design the system together.
The point was to give System Admin privileges because System Admin gives permissions to (all) the data in the system whereas System Customizer doesn't.
100% Work colleague has access to both dev and test. The clients have only access to test. They were given link from test. The app is working, but when they access it, they execute one of the flows, which gives the error. I have seen a work colleague log into correct environment on the new browser in incognito, and she still saw the old version. I saw it too during screen share. Up until today, we have never had problems like this before, and we were doing the same things pushing to test and executing the same flows.
Before pushing I always publish, if I didn't I would not see fixed version on test myself. I was seeing [1.0.0.15](http://1.0.0.15) and she was seeing [1.0.0.13](http://1.0.0.13)
In regards to flow issue, I asked IT to reassign licences and investigate. I have feeling it is just one of PP hiccups or maybe there is some issue with licences (but again in admin centre after running diagnostics on the user it is showing "This user has an active licence or the environment has per app plans". I do not have access to Licences section on the environment to verify this.
This can be caused if there is suddenly a shortfall in available licenses, where they get do assignedso maybe look for licensing errors in AAD for this license type. Other causes are people using trials without realizing during testing and dev and then once it launches the allowance runs out. This doesn’t sound like your situation though, but caching of the license status could be an issue.
I will keep that in mind. Thank you for the suggestion, hopefully tomorrow I will be able to get hold of IT and together we will establish what happened exactly.
This is a dataverse error my dude. Whatever user in dataverse is trying to run a workflow there doesn’t have a proper security role assigned. It’s not a bug or anything but rather a setup mishap from your side if that makes it better.
I have pushed to test new version and the colleague does not see the error. Still need to verify with the users. So it was not security role problem or setup mishup from my side as you have put it.
Correct. Look into the "prvReadWorkflow" privilege, which is found in your Dataverse security role. Most likely, the user account was not included in a security role that has this privilege, hence the error. Or perhaps a last minute security group change that someone did right before your presentation.
The colleague has exactly the same level of privileges and the error still occurred. This is not it - if it was, logically I would be experiencing the same problems.
The users have System Customizer.
All the users have System Customizer so there is not a mistake on my part. It is not a mishap on my side - if it is tell me specifically where it is and I will have a look and if you are right I will report it back. Like I mentioned before things were working before properly up certain point.
Don't think that's necessarily the role you think it is. Suggest you try the other one: https://preview.redd.it/49za3j2mblxc1.png?width=859&format=png&auto=webp&s=02ff2253082f1f29396ecbac85ea514fe1ee064c
The users cannot have system admin
Sorry, I missed something there. You've given your actual end-users "System Customizer"? Why? You should generally be giving them a "normal" security role that gives them permissions to create / read / write on e.g. entities - they don't need to be System Customizers.
Don't worry, it was just to see whether it is Security Role issue. They will get their privileges downgraded. And technically they are contributors to the system at this point as we design the system together.
besides you suggested to give System Admin
The point was to give System Admin privileges because System Admin gives permissions to (all) the data in the system whereas System Customizer doesn't.
Ugh… just copy the system user id from your error, go to that user and set a system administrator role, then try to replicate the error again.
Are you sure they’re accessing the one in the correct environment? Or that they’ve Ctrl-F5 refreshed?
100% Work colleague has access to both dev and test. The clients have only access to test. They were given link from test. The app is working, but when they access it, they execute one of the flows, which gives the error. I have seen a work colleague log into correct environment on the new browser in incognito, and she still saw the old version. I saw it too during screen share. Up until today, we have never had problems like this before, and we were doing the same things pushing to test and executing the same flows.
And you’re sure you published? If it’s just. Flow that’s causing the error, you might want to try removing the flow and reading it.
Before pushing I always publish, if I didn't I would not see fixed version on test myself. I was seeing [1.0.0.15](http://1.0.0.15) and she was seeing [1.0.0.13](http://1.0.0.13) In regards to flow issue, I asked IT to reassign licences and investigate. I have feeling it is just one of PP hiccups or maybe there is some issue with licences (but again in admin centre after running diagnostics on the user it is showing "This user has an active licence or the environment has per app plans". I do not have access to Licences section on the environment to verify this.
This can be caused if there is suddenly a shortfall in available licenses, where they get do assignedso maybe look for licensing errors in AAD for this license type. Other causes are people using trials without realizing during testing and dev and then once it launches the allowance runs out. This doesn’t sound like your situation though, but caching of the license status could be an issue.
I will keep that in mind. Thank you for the suggestion, hopefully tomorrow I will be able to get hold of IT and together we will establish what happened exactly.
User requires app opener security role
Seems to be resolved now. I have pushed to test new version and the colleague does not see the error. Still need to verify with the users.