Service in Test environment fails

Ask the community
1

Hi all,

I’m running into a permission issue when calling an Appfarm service from Power Automate.

  • The same HTTP request works fine in Dev.

  • In Test, the service call reaches Appfarm (confirmed in DevTools), but the request fails.

  • The error log shows:
    InsufficientCreatePermissionError: User does not have permission to create objects in this ObjectClass
    and
    User tried to read from Object Class [X] without proper permission

Setup:

  • The Power Automate flow is identical in both environments, except URL has “test” instead of “dev”.

  • The same service account and API Key is used.

  • The two Environments have the same settings.

  • The service is deployed to Test.

image
image1211×183 23.5 KB

image
image607×166 19.6 KB

What am I missing?
Do Object Class permissions need to be separately configured per environment? If so, where?

(No schedule, just a service)

2

Hi!

The error sounds like either an incomplete setup, or missing deployement after changes to permissions.

Simplest first, have you deployed to Test environment after the Permissions were set up correctly?

Second: If so, check the Role belonging to the Service Account of that API key, that it has

  1. Login Access to Test environment (Permissions → Login)
  2. Access to the Service (Perimissions → Services) and Read/Create/Update to the correct object classes (Permissions → Object Classes). I know it works in Dev, but if the Service account has e.g. Maintainer permissions, those have effect in Dev, but are removed in Test.
3

I did several targeted deploys. Sigurd from Braver pointed out that it might need a complete/full deploy. Which seems to have solved it.

Thanks

4

Aha, very good catch :wink:

Yes, I believe when doing changes to Permissions you need to do a “Full deploy” to get the changes out. We have an improvement in the pipeline for that.