By using this website, you agree to our Terms of Use (click here)
Acumatica Side Panels are a great way to show additional information on a screen.
You can add Side Panels to existing screens in Acumatica, either to Generic Inquiries using the Generic Inquiry (SM208000) screen or to data entry screens using the Customization Projects (SM204505) screen.
Here is a screen where I've added multiple Side Panels to the right-hand side of a data entry screen:
As you can see in the screenshot, the Side Panel options are presented as icons.
For the first 3 Side Panels, I selected meaningful icons. For the last 3 Side Panels, I didn't select any icons which is why the generic folder icon is displayed.
For data entry screens, adding Side Panels is often something done by a developer.
How can the person requesting the Side Panels know what icons are available?
The easiest way that I know of to see what icons are available for Side Panels is to try to edit the Acumatica menu. We don't need to make any changes to the menu, we just want to see the icons that are available.
The icons that are available on the Acumatica menu are the same icons that are available for Side Panels.
To see the list of icons that are available on the Acumatica menu, just do the following:
1. Go to ... -> Edit Menu in the Workspace area on the left-hand side. See 1st screenshot below.
2. Hover over any Workspace and click the pencil icon (Edit workspace parameters). See 2nd screenshot below.
3. Click the down arrow in the Icon field to see the list of available icons. See 3rd screenshot below.
All of the icons that you see in the previous screenshot are available to be used as icons for Side Panels in Acumatica.
You just need to tell the developer the names of the icons that you'd like to use for your Side Panels.
Hi Tim,
I'm currently working with a client that was surprised with the amount of development work required to reach the integration level they want to hit. Interestingly enough, side bars came up and I was a bit surprised they didn't bind these objects to security roles like most screens can be. It would have been an easier user experience to remove undesired buttons via a role that removed view access. Do you happen to have any insight into that design choice? i.e. the client wants to remove three of the side buttons that occur on the project screen.
Online Members
