You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have set up a custom workflow action taking a lookup to a security role (role). In the organization service of xrm Mockup the the role with the id from the custom workflow action argument is not present. A role with the same name name exists but the id seems to be random.
Steps to reproduce:
Create a custom workflow action having a role lookup as input argument
Create a workflow using this CWA and set the role lookup to any existing security role
Set up a xrm mockup context and try to find the role in the mock organization service using the id provided in the cwa lookup
Environment
CRM/D365/CDS version: Online 9.2.21012.00146
Tool version: 1.7.5
Other applicable environments
The text was updated successfully, but these errors were encountered:
Security role ids are not identical in a given instance. XrmMockup behaves correctly in my opinion in that it forces you to compare security roles by name
Security role ids are not identical in a given instance. XrmMockup behaves correctly in my opinion in that it forces you to compare security roles by name
I think custom security role id's are identical at least on the root business unit. Checked this on our staging environments and seems to be the case. Is it good practice to compare security roles by name? For me this sounds kind of dangerous...
Then I need to check that. I was always on the assumption that we had to check on name even though it sucks, because security role id's are not unique across environments
We have set up a custom workflow action taking a lookup to a security role (role). In the organization service of xrm Mockup the the role with the id from the custom workflow action argument is not present. A role with the same name name exists but the id seems to be random.
Steps to reproduce:
Environment
The text was updated successfully, but these errors were encountered: