By using this website, you agree to our Terms of Use (click here)
Hi,
Don't know if it is something I may have caused with an improper join or whatnot?
But "some" values rendered on "some" lines appear to be multiples of the correct value, or in some cases the columns in which the the value appears seem to be incorrect. The row counts however, appear to be correct.
For example, ARTran.NetSalesAmount may render as $700 which is double the expected value. Oddly enough, when I change the output to a simple formula [ARTran.NetSalesAmount] * 1 the expected value of $350 is rendered.
Also had an issue where on "some" lines ARTran.UnitPrice and ARTran.Qty values appeared to be rendering in each others column (i.e., UnitPrice was showing in the Qty column and vice versa). Once again multiplying the values by 1 appears to have fixed it.
Anyone ever run across anything resembling this scenario?
Thanks!
Hi Rob,
You can try cleaning up your mixed up field displays by resetting your column configuration to default. I had some users with similar issues pop up and this solved it for them.
I think the first two suspects for your first issue with ARTran.NetSalesAmount would be caused by either a Group By (if you have any) or due to the field being a calculated DAC field.
You can check if Group By is an issue pretty easily. Does your GI use any Group Bys? If yes, try adding ARTran.NetSalesAmount into your Group By.
If that doesn't work, and assuming there aren't other issues with the query, I feel like the strange behavior could be due to the field being calculated and the way Acumatica builds the SQL for the GI. You can investigate further if you use Trace to grab the generated SQL for the GI after running it both with and without the * 1 workaround.
If you are interested in seeing if your fields are Calculated or not, without official schema documentation, you'll have to check out attributes in the DAC code. Look for [PXDecimal] instead of [PXDBDecimal] attributes on the fields.
Good luck!
I experienced behavior like this a couple of months ago when trying to use Acumatica Dashboards to deliver KPIs based on Calculated Columns (with Formulas) in the underlying Generic Inquiry. The SQL that got generated was bizarre and I couldn't figure out how to trick it into doing what I wanted. But I personally haven't run into this problem yet myself in a Generic Inquiry itself.