Skip to main content
Solved

Modern UI issue with attributes used as parameters in RPX

  • Jun 22, 2026 7:13 PM UTC
  • 6 replies
  • 106 views
  • Translate All

Forum|alt.badge.img

Hello Community!!

In classic UI, We used to have an attribute (InventoryItem.PAM0000151_Attributes) as a parameter, so that user would be able to filter the results in the report by this parameter. In classic UI the user could view the parameter as a drop down field:

Now with modern UI, the parameter won’t show up.

This is how the parameter is set in the report designer:

Any help is really appreciated.

Best answer by albertobello83

Thank you all for your answers. I confirmed with Acumatica. This is a known issue that will be fixed for 26R2.

The work around is to use the particular report in classic mode.

View original

6 replies

mohammadnawaz51
Varsity I
Forum|alt.badge.img+8

​@albertobello83 Can you check the below information.

 

Translate

Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • Jun 22, 2026 7:23 PM UTC

Thank you ​@mohammadnawaz51, The difference in my case is that the values of the dropdown come dynamically  from  product’s attributes values. 

Translate

dgodsill97
Varsity II
Forum|alt.badge.img+6
  • Varsity II
  • Jun 23, 2026 1:38 PM UTC

Did you refresh schema?  Sometimes it seems an attribute does not appear in the schema and refreshing the schema may fix it?

Translate

Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • Jun 24, 2026 2:04 PM UTC

Did you refresh schema?  Sometimes it seems an attribute does not appear in the schema and refreshing the schema may fix it?

Thanks ​@dgodsill97. I refreshed the schema. But the attribute parameter won’t show.

 

Translate

dgodsill97
Varsity II
Forum|alt.badge.img+6
  • Varsity II
  • Jun 24, 2026 2:46 PM UTC

Sometimes it takes a few tries because you are using a client and it needs to pull it from the web site. Make sure to do the Load Schema first before the refresh.

Translate

Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • Answer
  • Jun 30, 2026 2:32 PM UTC

Thank you all for your answers. I confirmed with Acumatica. This is a known issue that will be fixed for 26R2.

The work around is to use the particular report in classic mode.

Translate