Look up references also show up in Model Rights - New Objects. However the reference itself does not need any rights. If you do go to the object you get a screen which implies there are no roles in the project. Since there is no point in having this object appear in New Objects. Please hide these objects behind a pre filter.
When using the deployer you have multiple paths to set for the upgrade. If one path is wrong you go back to square one. A lot of time and frustration could be saved if a simple preview of the actual paths used would be shown. This way you can fix any errors instead of trial and error.
If you add a column/pre filter/etc, to an existing table or view you have to manually assign the rights. However 99% of the time you just want to give rights to whoever has the new sub object available. So in practice I go to the object, I filter only the roles that have available: yes. Then assign the rights. And go back to the new objects screen. In a big project you have to do this several times. It would be great if there was a task on the new objects screen: "Assign rights based on availability”. What this new task should do is give you the popup for the assign rights… task, but should be executed for all roles that have available: yes. This task should be greyed out if no roles have the object as available (then you probably need to do something on main level first.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.