Answered

Publish all customizations in power platform solution fails with error

(0) Share

Report

Posted on by GargKr

Hello,

We have an environment where all keyusers can create or manage their PowerApps, Automate. So we assigned all keyusers with "Basic User" and "Environment Maker". With these roles they can create, share apps or flows.

However if they want to create a solution and publish all customization before export, they are getting an error "Commands.Publish failed: SecLib::CheckPrivilege failed. User: 9102436e-03a6-ec11-b3fe-000d3a4a569f, PrivilegeName: prvWriteEntity, PrivilegeId: 2a4e96d7-7bf9-4578-9d4e-1e494c33c1bf, Required Depth: Basic, BusinessUnitId: 31dd1cf1-7fa1-ec11-9840-00224884cc5d, MetadataCache Privileges Count: 3643, User Privileges Count: 940"

I know if we assign them "system admin" or "customizer" role then they won't have this error. However this role we don't want to provide to KeyUsers.

Please suggest if anything we can do except assigning the "System admin" or customizer role.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (1)

christophraidl 38 on at

Like (2)

Report
Creating a role that includes these privileges (,marked in red) should do the trick.

Please give a thumbs up and/or mark this as a solution if the post was helpful.

Was this reply helpful? Yes No
subsguts 1,259 Moderator on at

Like (0)

Report

I got this error after publishing many times. Why would it stop working?

Was this reply helpful? Yes No
christophraidl 38 on at

Like (1)

Report

Maybe someone removed some of your privileges or changed an existing role?
Can you verify that you got the needed privileges mentioned above?

Was this reply helpful? Yes No
SteRe 254 on at

Like (1)

Report

At the same page in your role definition you can also find the different objects to customize. According to the posted error message, your users also require write permissions on <entity>.

Was this reply helpful? Yes No
Verified answer

subsguts 1,259 Moderator on at

Like (0)

Report

I reported this to administrators, and they were able to publish. After that, I was able to, so they think it was something on Microsoft's side since my permissions were changed. Thanks for your suggestions and help.

Was this reply helpful? Yes No