This topic contains 2 replies, has 0 voices, and was last updated by James Magness 15 years, 11 months ago.
-
AuthorPosts
-
November 19, 2008 at 6:41 am #4348
James MagnessAfter installing a bundle I’ve then gone and added the required permissions to the different roles in my instance against the new custom records from the bundle.
Can anyone tell me off hte top of their head if I do a bundle update do I need to re-apply all these permissions?
On a more general note, the help docs hint towards most customisations being overwritten when an update is installed. Has anyone got any more information or stories of what happens?
This is a cached copy. Click here to see the original post. -
November 19, 2008 at 7:24 am #4349
James MagnessRE: Bundle Updates and permissions
After 30 minutes of testing and a very simple bundle…
Permissions are persistent
i.e. updating a bundle does not overwrite permissions set against a custom record of an installed bundle.
Note: The update does impact the Use Permissions Field of the custom record.
And an custom role assigned to the source bundle’s custom record was not included when the bundle was installed. This is the desired functionality for me so I was very happy.
Custom Forms are also persistent too!!
I created a custom form for the custom record installed by my test bundle. This form I marked as preferred. Upon updating the bundle the form is still the preferred form and I guess more importantly was not deleted.
Exciting stuff.
Iโm still after feedback, experiences and links to documentation for this stuff.
-
December 1, 2008 at 3:14 am #4350
James MagnessRE: Bundle Updates and permissions
I’ll use this thread to continue my Bundle Permissions experience.
I created a minor update to my bundle (a few lines of code in a suitelet) and republished my bundle the update went straight forward and I updated my config as per my other thread.
Everything looked good the change to the bundle wasn’t major at all, I was simply following best practice as opposed to hacking on Production.
However the Bundle upgrade has added an Unexpected Error for certain users trying to access one of the custom records. Other custom records in the bundle are fine.
The error does not affect Administrator or Full Access roles only user roles. This points heavily towards a permissions problem but I’ve removed all permission requirements for the custom record in question.
I was attached to an existing defect: 156366. Only Sev 2 so I’ve started my 60 day wait.
-
AuthorPosts
You must be logged in to reply to this topic.