By using this website, you agree to our Terms of Use (click here)
Our Billing department hit me with a GI request last night and I've been pulling my hair out over this for the past 12 hours 😥. Yesterday evening I was asked to pull the "unapplied balance" field into our Payments and Applications GI, and after a couple failed attempts + some forum surfing I found that this field "APPayment.CuryUnappliedBal" is simply not going to give me this information (because this is a calculation field). Â
I then stumbled across the post below, where this individual seems to be encountering the exact same issue. Naturally I was very excited to see the "best answer" providing a different route to accomplish what I'm after... but I have since attempted to use the fix provided in this thread, to no avail. Much like the "APPayment.CuryUnappliedBal" field, "APRegisterReport.DocBal" is also pulling a blank column into my GI. Â
"Instead of using APPayment.CuryUnappliedBal, join APRegisterReport with APPayement and using field APPayment.CuryDocBal, schema field is APRegisterReport.DocBal It will show the amount of unapplied"
Â
I'm at a loss and I'm very much hoping that someone in the AUG community has an answer to this problem.Â
Thank You,
Â
Apologies if bumping a thread like this is against the rules / bad practice.Â
@nscyoc Were you able to find a resolution to this issue? My accounting department is asking of me the exact same thing -- and I also encountered the same Acumatica forum link you did. The suggestion did not work -- and I've been having trouble getting the calculations onto the GI correctly.Â
@bmorgan I'm not an expert by any means, but I'll do my best to explain it as I've come to understand things... The CuryUnappliedBal Field is what's known as a "calculated field" in Acumatica. What this means is that the field does not have a permanent value, the values that are shown in these fields within Acumatica are populated on the fly based on a variety of factors. So what we see when we open an invoice or a sales order is a value that's being calculated in real time. When we try to reference these fields within a generic inquiry, they pull blanks because when SQL runs a query through the GI screen - the field it's referencing does not have a hard value to pull.Â
We have rectified theses issues in a couple different ways, depending on the situation.
A. Create a custom field within Acumatica through the customization editor, this allows you to run the calculation before the table is referenced; making the value a "hard value" and as a result, a discoverable value by your GI. This option is tedious and requires a bit of expertise, as I don't recommend jumping into the customization editor without a good understanding of what you are doing.
B. Find a field that (equates to/shares the same values as) the one you are attempting to reference in your Generic inquiry. In MOST (but certainly not all) cases... this is your best and easiest answer. I do however regret to inform you that in the case of this specific issue; we were not able to do so, and ultimately our answer ended up being the "A" route.Â
I apologize that this isn't more helpful, and I certainly hope with all the time that has passed - you folks have found a way to get the information you were looking for into a generic inquiry. Â
@nscyoc This was plenty helpful! I appreciate you taking the time to come back and explain the solution that worked for you and your team.
