Skip to main content
Solved

Unbund Fields in "Condition" and "Grouping" tabs of Generic Inquiry Design


aaghaei
Captain II
Forum|alt.badge.img+9

Hello Community,

 

I have added a custom unbound field to APInvoice DAC. I see the field in the “Result Grid” of the Generic Inquiry I want to design and it shows the result as I expect. My problem is I do not see this field in the "Condition" and "Grouping" tabs of Generic Inquiry Design. I have other custom bound fields which are shown in these two tabs. Am I missing something or Acumatica doesn’t show the unbound fields in these two tabs and if ths is the case any idea why? Im testing on 2023R2 23.206.0006

Best answer by aaghaei

It seems my underestanding is correct and the issue is coming from the field being unbound. I do not underestand the logic of the GI allowing the Unbound Fields to be selected in the result grid but not in Grouping and Filtering. I changed the field to bound (although it is not what I want but just for testing pupose) and it showed up in Grouping and Filtering. If someone knows why I would like to learn too.

View original
Did this topic help you find an answer to your question?

5 replies

aaghaei
Captain II
Forum|alt.badge.img+9
  • Author
  • Captain II
  • 1179 replies
  • Answer
  • April 6, 2024

It seems my underestanding is correct and the issue is coming from the field being unbound. I do not underestand the logic of the GI allowing the Unbound Fields to be selected in the result grid but not in Grouping and Filtering. I changed the field to bound (although it is not what I want but just for testing pupose) and it showed up in Grouping and Filtering. If someone knows why I would like to learn too.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2657 replies
  • April 7, 2024

Thank you for sharing your findings with the community @aaghaei!


  • Freshman I
  • 2 replies
  • August 1, 2024

How do you bound a field?


aaghaei
Captain II
Forum|alt.badge.img+9
  • Author
  • Captain II
  • 1179 replies
  • August 1, 2024

Bound means the Field should exist in the Database. Unbound means a field that its value is driven from other fields without field itself being exist in DB. each has their own advantages and disadvantages and depending on the situation you will need to pick the appropriate type. If you want to a field to be bound then in DAC declaration you should use PXDB...and if unbound then PX…. If you want to declare a field as bounded then you will need to add it to the corresponding table in your package.


Forum|alt.badge.img
  • Freshman I
  • 13 replies
  • December 13, 2024

I have hit a similar wall today -- I am working on a custom GI, where POVendorInventory features heavily. The IsDefault field is non-persisted (not a customization). If the field is not persisted, how does the app remember this information when the app is restarted? Obviously that bit has to be saved somewhere...right?

I can configure a workaround with another GROUP BY and a filter after the fact, but I would love to see if there is another way to make the filter invisible to the rest of the company.

 

Thanks,

Aaron


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings