Business Central 2023 Spring Update, 22.0.54157.54644, Permissions Identified - GET READY!
What are the Permission Changes coming in Business Central Version 22?
Permission changes can take your organization down if you have custom or tenant Permissions at an update time if you are not prepared. An example: You are on Business Central Online, version 21. In your database, you have customized Permissions by either making Permission Sets from scratch or copying Permission Sets. Everything is going great. Users are restricted to their Roles, and life is safe and nice.
Then along comes an update that you did not prepare for. Microsoft rolls out the "new" Permissions overnight to their system Permission Sets in your database. These new Permissions are not applied to the customized Permissions you have made (how could they be, they are yours!). Morning comes, and some of your Users cannot even log in! What is happening?!
A Super User notices that Microsoft has put some new Permission Requirements on the Home screen of the Role Center they are using. You rush to fix it but cannot record Permissions, not on the Home screen. What do you do? Alas, you throw in the towel... you assign the Super Permission Set to the Users with issues, and all is well (except they have Super access!). Now what do you do? You can engage your Partner, figure it out yourself.... or you could have planned for this. Here is what I do, plan ahead and enjoy your update stress-free, even with custom Permission!
I have identified the new Objects, when comparing Application Version 21.5.53619.53813 to 22.0.54157.54644.
1. Go to the All Objects Page in your current Production Database and dump it to Excel (21.5.53619.53813 in this example).
2. Go to your Business Central Administration Center and create a new Sandbox, Preview Version.
3. Go to the All Objects Page in the Preview Version and dump it to Excel (22.0.54157.54644 in this example).
4. Compare both in Excel to determine what Objects are new Objects in the new Version (look at type: Table, Report, Codeunit, XMLport, MenuSuite, Page, Query, System).
5. In your existing Production Database (21.5.53619.53813) create a new Permission Set; I named mine "BC22 Permissions".
6. In your existing Production Database, create a RapidStart Package for Table 2000000166. Import your new Permissions (sample file attached). Notice that I turned off Validation on the Object ID field. The new Objects you just identified in the Update Preview version do not exist in your current Production Database, so you have to turn off that Validation.
7. Notice in your new Permission Set; there are no "Object Names." This is because they do not exist yet; they will sync right up when the update happens!
8. Review your new Permission Set and Excel spreadsheet (it has the Object Names in it) to ensure there are no new Permissions (based on names) you want to keep from Users. If there are, simply copy your set and reduce the access.
Now, assign your new Permission Set(s) to your Users directly or to their User Groups.
Please do let me know if this is helpful, and any cool Permissions tricks you know of.
