Skip to main content
Answer

Generic Inquiry Parameters Defaulting to NEW Value?

  • January 30, 2021
  • 5 replies
  • 1095 views

PaulMainard55
Captain I
Forum|alt.badge.img+2

In version 2020r2 v205 (I know… :rolling_eyes: ) I have a couple of GIs that I’ve created that are using the InventoryCD value as my parameter with standard parameters allowing for the display of all items if the parameter is Null.  

When I open the Inquiry, either from the UI or using the View Inquiry action from the Generic Inquiries screen, Acumatica is inserting the <NEW> value, as though it’s expecting me to create a new record.  

 Has anyone seen this before?

Best answer by ChandraM

Hi @freiter85 and @plmainard , Using =Null as the defualt value works for the Customer view that had the same issue.

Thanks

5 replies

Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • January 31, 2021

Hi @plmainard This is strange....Not seen this before…

Can you please export XML format of GI and share. We can dig into it and let you know if found anything


PaulMainard55
Captain I
Forum|alt.badge.img+2
  • Author
  • Captain I
  • February 3, 2021

Hi Naveen,

According to support, it’s because the GI is using InventoryItem.InventoryCD as the parameter filter while having auto-numbering enabled for the Inventory Item segmented key.  Seems a bit strange but I think it’s a bug.  I may need to use a different schema field for the query filter that’s not linked to the Inventory maintenance screen.  Doesn’t make much sense to me, but I will try to find another filter to make this work.  I think there’s one that can be used as a dashboard filter that may work.

 

Thanks for the response though.  


  • Freshman I
  • February 8, 2021

Try setting the Default Value of the paramter to =Null


Forum|alt.badge.img+8
  • Semi-Pro I
  • Answer
  • September 29, 2021

Hi @freiter85 and @plmainard , Using =Null as the defualt value works for the Customer view that had the same issue.

Thanks


Forum|alt.badge.img+1
  • Jr Varsity II
  • November 13, 2025

=Null worked for a while, but now the parameters are populating with =Null.

Any ideas how to prevent this?