Blog Post

How to Fix the Acumatica 2018R2 Release Project Summary Error

Published on

April 17, 2019

By

by

Troy Vars

If you are getting the error “Invalid field namePOLine.CuryOpenAmt has been specified” upon running the included Project Summary report in 2018R2 release of Acumatica below is the steps for a hot-fix. This report is most noticeable if you have an open PO against your project. For example, “Project TMR02” in the Demo Data.

Below, I’ve outlined the steps for you to take in order to get rid of the error. (Or if you’d rather, get help from one of our experienced team by contacting us here.)

a screen shot of the Invalid field name POLine.CuryOpenAmt has been specified error

How to Clear “Invalid Field Name POLine.CuryOpenAmt” Error in Acumatica

1.      Open Report Designer for the report. If you are using the “Edit Report” note that the report opens the Main Report and we need to do the next step to get to the sub report.

A screenshot of the Acumatica Report Designer

2.      OpenReport From server

3.      Next,we need to Open the sub-report. Click on File=> Open Report From Server. In the pop-up box, fill in your credentials, and click on the Load Reports List button and find the file “pmpos.rpx” in the List Box.

a screenshot of the open report from server pop-up box

4.       With the Sub-Report open, we need to edit two areas. In Detail Section 1, click on the far right box and change the Value field from “=[POLine.CuryOpenAmt]” to “=[POLine.CuryUnBilledAmt]”. You may need to do this from the Properties window to the right, depending on your screen size.
Note: you can’t selectPOLine.CuryUnBilledAmt from the Expression Editor nor will the editor return a successful validation. Make sure your capitalization is correct and the report will run just fine.

A screenshot of the detail section of the sub-report.
Acumatica project summary appearance and behavior

5.      Click on Detail Section 1 bar.

6.      Open the Variables Collection from the Properties by clicking the ellipsis “…” beside it.

A screenshot of the variables collection.

7.      Clickon the POOpenAmount.

8.       Change the ValueExpr field for POOpenAmt calculation from “=$POopenAmt+[POLine.CuryOpenAmt]”to “=$POopenAmt+[POLine.CuryUnbilledAmt]”.
Note: you can’t selectPOLine.CuryUnBilledAmt from the Expression Editor nor will the editor return a successful validation. Make sure your capitalization is correct and the report will run just fine.

A screenshot of the ReportVariable Collection Editor inside of Acumatica

9.    Save detail report to server without version.

10.  Refresh the Browser.

11.  Run your Report with any project to test error is gone.

A screenshot of a successful project summary report inside of Acumatica

Success! The error should no longer come up. However, if this doesn’t work for you, rest assured you’re not stuck. CS3 can help you (it’s what we’re here for)! Contact a knowledgeable and experienced team member to get help now, and learn more about CS3 Technology’s Serv Access Plan here, so you will never have to worry about those errors again. We look forward to helping solve your problems.

Header image by Gerd Altmann from Pixabay.

Written By
Website Proudly Crafted by DSB Creative