A flow adds a record to dataverse, the record owner is set as the Flow execution service account.
Attempting to change, or set the owner to a user ID, only works if that users AD privilege is already reflected in the AAD Team
This can be forced if they use an app to add a record in the environment. I have now isolated the problem so it can be repeated.
Is there any way the user name can be forced from AD into the AAD team without them doing any dataverse activity?.
OR a way to override the default owner ID currently set as the Flow execution account.
Two attachments both show the initial successful record add to 'D003 Engagements'.
One fails as the 'T&S Power Apps' ID (which IS present in AD) has not been reflected in the Team group.
The same flow runs okay if the 'T&S Power Apps' ID is present in the Team group, as occurs if the user has used a screen App to add a record.
The owner setting is vital as users can only see the records they own. Desperate to fix as deploy pending to 300 users!Cheers, richard
[View:/cfs-file/__key/communityserver-discussions-components-files/117/PAD_2D00_23NOV22_2D00_123101_2D00_add_2D00_engagement_2D00_owner_2D00_change_2D00_succeed.txt][View:/cfs-file/__key/communityserver-discussions-components-files/117/PAD_2D00_23NOV22_2D00_122915_2D00_add_2D00_engagement_2D00_owner_2D00_change_2D00_fail.txt] 
