web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Entity 'systemuser' Wi...
Power Apps
Answered

Entity 'systemuser' With Id = Does Not Exist on Add Row in to Table

(0) ShareShare
ReportReport
Posted on by 75

This is in a managed solution (production). This flow is meant to clean up some pieces after an update. The rest of the update has worked as expected.

 

I am getting this error message when trying to add a record to a table:

Entity 'systemuser' With Id = <GUID> Does Not Exist on Add Row in to Table.

 

I am not trying to do anything fancy, I am only making the value of the text upper case.

PattersonCA1_0-1715774218681.png

 

I have tried changing the connection reference to a new connection reference for the same account. I have tried deleting the step and recreating it. I deleted the ensuing unmanaged layer to ensure that wasn't the issue from the beginning. The account being used is the main (only) service account used to administer this solution.

I have the same question (0)
  • PattersonCA1 Profile Picture
    75 on at

    I have been able to determine that this is a permissions issue. But I am not sure why. This worked when I published from development (unmanaged) to stage (managed). This was approved and the same package was then published to production (managed). All 3 environments use the same exact service account, and it has System Administrator in all 3 locations. However, all tables that are new are not able to be edited by this admin account. They can be edited perfectly fine in stage, which should be exactly the same except for the data.

     

    When I look at the solutions, the tables all appears as expected as managed within the solution. Any ideas what could cause this permissions disconnect?

  • Verified answer
    PattersonCA1 Profile Picture
    75 on at

    This was resolved. It was due to a business rule that was in place to change the owner of the record to the service account which had a different GUID between environments.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 542 Most Valuable Professional

#2
Haque Profile Picture

Haque 206

#3
Kalathiya Profile Picture

Kalathiya 201 Super User 2026 Season 1

Last 30 days Overall leaderboard