By using this website, you agree to our Terms of Use (click here)
Rather than try to export User Role Security from one Tenant and import it into another Tenant, I personally find that it's easier to do it with an Import Scenario.
This method allows you to maintain all security changes in one Tenant, then publish them out to other Tenants.
1. Create a separate Customization Project for User Security in the main Tenant using the Customization Projects (SM204505) screen:

2. Open up the Customization Project, go to Access Rights on the left, and click the + button on the top:

3. This part is really tedious. You’ll want to click the Select box on every single screen. I prefer the keyboard rather than clicking, so I just keep doing <Down Arrow> <Space>, <Down Arrow> <Space>, etc. But it takes a while so put on some music or a podcast:

4. Keep in mind that you don’t get to grab User Roles and all the Screens related to those User Roles (which really stinks). You have to select a Screen and it grabs all User Roles related to that Screen. That’s why you have to select all the Screens to get all of the possible security that’s defined.
5. Once you add all of the screens, they will be listed in the grid and the number of screens will be shown in parentheses on the left-hand side (I only did 4 screens in my screenshot below). The good news though is that, once you have your screens listed, all you need to do is click RELOAD FROM DATABASE and it will pickup all current security for all screens. If you have any new screens though that you add to Acumatica, you’ll have to click the + button to add them.

6. You’ll want to create the Customization Project in the main Tenant where you actually make security change. Click the RELOAD FROM DATABASE button above to update the Customization Project with the current security. Then, you can publish the Customization Project to the other Tenants. You only need the Database data though (no front end stuff) so you can click PUBLISH (down arrow) -> Publish to Multiple Tenants, select the other Tenants, check the Apply Changes Only to Database (Skip Website Update) checkbox, and click the OK button:

Why did I say “Tenant” instead of “Company” above? Well, it’s because Acumatica renamed everything which gets confusing, although personally I like the new names better. Hopefully this helps explain:

I just tried this and when I hit the "+" to get the list of available screens to select, only 291 screens showed up. It was missing the majority of AP, AR and probbaly others but AP/AR were real obvious as it only loaded in 3 or 4 screens for each. What am I doing wrong? Where is that list coming from?
Not sure. I didn't have to do anything "special" for them to come up. Does your user have access to those screens on the menu? Did you try sorting on Screen ID to see if maybe they are sorting out of order by default for some reason?
Regarding step #3, you could use a simple Autohotkey script to program the act of hitting the spacebar then the down arrow several hundred times to quickly check those boxes. That is, if you don't have a backlog of podcasts to listen to.
The script is below will process the Space + Down arrow routine 200 times after hitting ctrl+t:
^t::
Loop,200 {
Send {space}
Sleep 10
Send {down}
}
return
Nice Autohotkey trick Tony!
I followed all of the steps above, through publishing the customization project. The display shows 97 items, which I have to suppose are all of the Objects. When I return to the Customization Projects window to publish to all companies, the Publish button is grayed out.
Did I miss a step?
I used Pulover's Macro Creator. I attached the script. To use:
- Download and install PMC from above link.
- Load the macro file attached to this post
- Navigate to the window where you select all the screens
- Press the play button in the PMC main screen
- Click on the PMC icon in tool bar when near the end.
- Select any missing screens by filter for fals on the Select field
- Save
- Reload from database
- Publish to all tenants
