Has anybody experienced this with a suiteapp? We ...
# sdf
m
Has anybody experienced this with a suiteapp? We use custom records that use the permission list. When we update the xml of the object and push an update, it removes the user’s custom role permission on update and the user then has to go back and add it to their custom role?
b
are you using the permissions structured field
m
yes
b
what does it look like
m
Copy code
<permissions>
  <permission>
    <permittedlevel>FULL</permittedlevel>
    <permittedrole>ADMINISTRATOR</permittedrole>
    <restriction></restriction>
  </permission>
  <permission>
    <permittedlevel>FULL</permittedlevel>
    <permittedrole>[scriptid=customrole_nact_administrator]</permittedrole>
    <restriction></restriction>
  </permission>
</permissions>
b
that looks like the custom record should be updated to have 2 rows in its permission list, one for administrator and one for customrole_nact_administrator
m
yes but what about when a customer sets the permission on their own custom role and it adds it to the permission list. I don’t want to overwrite it. is their a way to preserve? I can’t deploy without the permission for our custom role in the list
b
dont think so, its a replace sort of deal
m
I’m going to create a support ticket then, it should be an option as it’s not an issue with bundles. Our clients have to update their role permissions after each update if the record definition is changed
b
you can try playing around with Overwriting Custom Record Types, though to my knowledge that only applies to instances
m
yeah. I tried adding a permissions and it didn’t work