Skip to main content
Answer

How to Automatically Display Parameters in a Grid Across Custom Screens

  • December 19, 2024
  • 4 replies
  • 96 views

Forum|alt.badge.img

I created a custom screen (Screen 1) with a custom DAC, which includes a grid.

There is another custom data entry screen (Screen 2) used to input parameters. I want to display all the parameters entered in Screen 2 within the grid of Screen 1 and allow users to enter and save the corresponding values for those parameters.

I tried this, but currently, I have to select each parameter individually to add it to the grid. Instead, I want all the parameters to automatically display in the grid of Screen 1 when the user navigates to that screen.

How to do this?

Any detailed instructions, tips, or code snippets would be greatly appreciated. Thank you!

Best answer by darylbowman

You’d have to select all the screen 1 parameters/values and compare to the screen 2 parameters. If there are parameters on screen 2 that don’t exist on screen 1, insert them into screen 1.

You can read about data view delegates here.

4 replies

MichaelShirk
Captain II
Forum|alt.badge.img+5
  • Captain II
  • December 19, 2024

Hi ​@RKarunarathne51 , Have you completed the T-Series developer courses available from Acumatica Open University? 
You’re project seems fairly simple, and I believe the courses should provide the knowledge needed to complete this task. 
If you’ve gone through the developer courses and are looking for step-by-step instructions specific to your project requirements, a contract Acumatica developer such as ​@darylbowman might be able to provide customized consultation for you.

 

Regards,


darylbowman
Captain II
Forum|alt.badge.img+15
  • December 19, 2024

It depends what functionality you’re hoping for. If there’s nothing wrong with parameter records being saved to the screen 1 grid without values, I’d use a data view delegate to select any existing parameter records. If there are parameters that haven’t yet been added to screen 1, I’d insert them in the delegate. From there, it’s simply a matter of the user adding values and saving.

If the screen is more complicated than that, you could try inserting values into the cache when the screen is loaded and removing the empty ones when saving (so as not to save parameters with empty values). This can be tricky.


Forum|alt.badge.img

Hi ​@darylbowman,

As you mentioned above, this is my scenario.

“If there’s nothing wrong with parameter records being saved to the screen 1 grid without values, I’d use a data view delegate to select any existing parameter records. If there are parameters that haven’t yet been added to screen 1, I’d insert them in the delegate. From there, it’s simply a matter of the user adding values and saving.”

How to use a data view delegate to identify the existing records? Because, initially there should be all parameters without assigned values. Users can then enter values for these parameters. When the screen is opened again, these entered values should be displayed.

 


darylbowman
Captain II
Forum|alt.badge.img+15
  • Answer
  • January 7, 2025

You’d have to select all the screen 1 parameters/values and compare to the screen 2 parameters. If there are parameters on screen 2 that don’t exist on screen 1, insert them into screen 1.

You can read about data view delegates here.