Can we add Side Panel for Processing screens?

Hey Naveen,

It’s not perfect, but you should be able to open side panels from the graph with the following code:

throw new PXRedirectToGIRequiredException("Component Inventory", parameters) { Mode = PXBaseRedirectException.WindowMode.Layer };

This for example, will open the “Component Inventory” GI in a side panel because it’s window mode is set to Layer.

Unfortunately however, I cannot figure out how to house this logic in a nice way that creates the side panel buttons like you would see when you create side panels on GIs or other screens via the project browser wizard. As far as I know, you’d have to house this logic in a standard button, which when pressed would then open the side panel which feels kind of clunky in my opinion, especially if you need multiple side panels. If you or anyone else figures out how to do this more elegantly, I’d love to know as well.


As a side note for general information for the curious, if you use this code segment on a screen that already has side panels configured, this code will simply redirect your current side panel according to your Redirect Exception.​​​​​​​ When used in conjunction with a javascript script to identify which panel is currently open, this can be very useful to update side panels automatically! This also allows for side panels to accept detail level parameters. Very Handy!

@Naveen B Yeah, that’s what I meant by it being clunky. As far as I know you’d have to make a menu folder for all your side panel actions, and users could change the side panel with those buttons, but I don’t even know how you’d hide the side panel with this kind of method.

I imagine it’s possible to make a nice looking side panel from code considering we can get this far, but I couldn’t figure it out. figured I’d share as far as I got.

Hey @Naveen B I’ve actually been digging around myself and found some interesting information. I think we may be able to find a creative solution with this. Anyway, I tried creating a side panel navigation action by directly editing the XML through the customization project browser. When I did this, I got a side panel to appear properly with all the buttons as it would be  when you create the action with a wizard. The issue is the buttons were dead, they didn’t do anything.

But here is where things get interesting. This is the same functionality that these buttons have on any other screen when creating a new record, but once the record is saved the side panel button behave as expected. This leads me to believe the side panel buttons require a reference to an instance of the screen’s graph’s primary DAC. Without one the code probably receives and catches a null reference exception, which would explain why the buttons are dead while creating a new record. And that’s why the processing screens likely have side panel navigation disabled, since their primary DAC’s are always filters.

Knowing this I have a few ideas that might make this functional.

first, we could try to find and directly override the logic that catches the null exception (if that is what’s actually happening)

or we could use javascript to listen for side panel actions to be called and run the code snippet I showed earlier to force a redirect with custom logic. Since I now know we can create the buttons for the side panels with the XML, this solution seems a lot more viable to me.

I’m sorry Naveen, my company doesn’t actually use Replenishments so I’m not even familiar with this screen.

Also, my javascript solution doesn’t seem to work either / :
I build a mock-proof of concept project. I am able to get the side panel with buttons, and the side panel even opens, but only for a brief second. It then automatically closes itself and gets stuck that way. Sorry I wasn’t able to help more

@Dana Moffat, I would like to do this as well.  It would be beneficial to have this on the “Dead Stock” and “Prepare Replenishment” processing screens so that the user does not have to bounce around to see open and historical transactions while reviewing the item data on these screens.

Hi @Naveen Boga  were you able to find a solution? Thank you!

@Dana Moffat 

Is Acumatica planning to add functionality to pass parameters from form details to side panels? I know its possible with some messy mix of C# and JS workaround but I am asking for out-of-box possibility if is in the road map.

@Dana Moffat 

I was in this meet-up session last year which is why I mentioned in my previous comment “mix of JS and C#”. Acumatica really needs to take something like this seriously with all these demands and needs raised from multiple sources.