Answered

Error when trying to create a record: SystemUser With Id = GUID goes here Does Not Exist

(0) Share

Report

Posted on by rmarquez

Hi,

I'm trying to use Create a new row to add a record to a table. One field, Person Assigned (Users) is a Lookup field. This field is giving me grief. I used Get user profile (V2) to get the Id from the user profile and assigned the id to a variable, which is then used in the Person Assigned (Users) field as follows: systemusers(varPersonAssignedID). When the Flow runs, I get the error message in the subject line (left out the actual GUID). I know the user exists. So I'm not sure why I get the error. By the way, I also tried users(varPersonAssignedID). That also generated an error: Resource not found for the segment 'users'. Other variations tried that failed include /users/varPersonAssignedID; /users/(varPersonAssignedID); /systemusers/(varPersonAssignedID).

Any assistance is much appreciated.

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (11)

Answers (3)

Sort by

Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @rmarquez

Looks like you are confusing the user’s Office 365 ID with their Dataverse record ID. Instead of using the Get User Profile action, use the Get Record or List Records action from the Common Data Service connector. This will give you the correct ID for the users record in Dataverse

Was this reply helpful? Yes No
Anupam.Khasia 368 on at

Like (0)

Report
Copy link

Link copied!

Hi @rmarquez ,

It looks like you are getting office 365 user instead try to get Dataverse user Id (System User ID) .

Let me know if you face same error afterwards.

Thanks
Anupam

Was this reply helpful? Yes No
rmarquez 75 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for your response. Appreciate it. I used Get Record (Dataverse) but I'm still getting an error that basically says the user doesn't exist. Let me explain what I'm trying to do with the hopes that it adds more clarity and sets me in the right direction. I have a Sharepoint list that is approaching 5000 records. To mitigate, I planned to copy the records to Dataverse tables.

My flow is manually triggered, initializes variables, and uses Get Items (Sharepoint) to get the list of Sharepoint records to be processed. It's at this point where I begin mapping over choice values to variables in addition to attempting to get the right value to map to the field in Dataverse called Person Assigned, which is a lookup field in Dataverse.

Now that I've described what I'm trying to do overall, does this change your recommendation? I'm beginning to wonder if systemuser is really the right entity to use with the GUID? The related table in Dataverse for that field is User, and it seems to work fine when I use an edit form against the table in Dataverse. So not sure what could be wrong here.

Thanks

Was this reply helpful? Yes No
Anupam.Khasia 368 on at

Like (0)

Report
Copy link

Link copied!
Hi @rmarquez ,

There are two possible solutions for your problem :

You need to have same Users which you have in your sharepoint list called "Person Assigned". Its mostly Person assigned users are not available in System user table in Dataverse.
Second, Before creating records in Dataverse , you can search for System user records based on "Person Assigned" - Name field (not GUID). If you find Person Assigned from System user than you need take its GUID and set when you are creating records.
Let me know if you have any questions.

Thanks
Anupam
(Please like/resolve if it helps you really.)

Was this reply helpful? Yes No
Verified answer

Fubar 8,501 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

As the others have pointed out, systemusers is the CDS/DataVerse user unless your Person is also a Data Verse user you need to do something else.

If your Person are DataVerse users then you can use their email address to find then in CDS/DataVerse (just make sure that in CDS/DataVerse they have a Security Role with appropriate privileges assigned).

Entities/Tables that are User or Team owned required an actual user or team to be assigned (no way around it), Organisation entities do not require record owners (most out of the box are User or Team owned). If not in DataVerse, if you are just looking for something generic to own the records in CDS/DataVerse one option is to create a Team (and assign it a Security Role with enough privileges to own the records), the other is to create another generic User and use it (you can set this user to being non-interactive so it doesn't consume a licence, but you have to initially assign it a licence to push it into the instance and in the instance you can then set it non-interactive and then you can pull the licence off the user in Office 365).

If the Person needs to be recorded against the data but is not a CDS/DataVerse user, then look at either creating another entity (for the list of names) that you lookup, or just put a text field on the entity and populate it with their name - either case you would still need to set the record owner to a valid user or team.

Was this reply helpful? Yes No
rmarquez 75 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for your response. I am able to see the person in the Dataverse lookup field. The entities are currently organization-owned. I successfully loaded the person in a text field, but don't want to go that route since I won't have the ability to have the user lookup a person when using that field. I'm passing the user's GUID in the Create new record step. So not sure why it's giving me the error.

Thanks

Was this reply helpful? Yes No
Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @rmarquez

Are you able to share some screenshots of the flow actions where you are looking up the user’s ID and then when you are trying to set it (and getting the error)? I think this will help us advise better.

Was this reply helpful? Yes No
rmarquez 75 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Sure. See below and let me know if you have more questions. Again, really appreciate everyone's help. I should note the number of users to be looked up is less than 10. So no need to worry about the Switch that was set up to ensure the right email address is used. It's basically my team members that should be selected in the Person Assigned field--not anyone in the company.

The error is on the Get record step. Also, I've gone into Security>Users and do see the employee that is causing the error in the User table.

Thanks

Was this reply helpful? Yes No
Verified answer

Fubar 8,501 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
In your Flow you are trying to put the Office 365 Guid as the Dataverse GUID as already pointed out this is not the same.

The essence of what you need to do:
From the Profile step you need to grab the email address (there's also another item you can use but off the top of my head I can't remember what it is - UPN or something).
After the Profile step you need to do a datavers/common datat service List Records (for the Users table) and in the query filter based on the email address from the Profile step.
Then you grab the first record found from the List Records and use its GUID (field will be something like something like systemuserid)

Was this reply helpful? Yes No
Verified answer

rmarquez 75 on at

Like (0)

Report
Copy link

Link copied!

Hi Fubar,

Thanks for the guidance on that. I got everything to work based on your input. I used CDS List Records and set a filter on internalemailaddress eq varPersonAssigned (hold email address from Get User Profile (V2)). Then I used Get record (CDS) with the Item identifier of User followed by setting another variable to hold the value of User. This was the tie back to the right GUID for the Person Assigned lookup field. All worked flawlessly. Many thanks for everyone's help.

Thanks

Was this reply helpful? Yes No