Post Upgrade – Updateable BAQ error popup. Problems in BAQ update processing

Post Upgrade – Updateable BAQ error popup.

*Solution is remove and fresh install of client This is an FYI after several days on another post.

We upgraded from 2022.1.13 to 2022.1.16 in November. After that change, our updateable BAQs give us a popup when we Analyze or Test it. The BAQ functions. The update happens. We get “Syntax is OK” when we Analyze.
This is a simple updateable BAQ from years ago.

Below is a small piece of the popup.

We did not have this error when we went from 10.2.600 to 2022.1.13. (manual install from server).
I have recreated the BAQ. The BAQ works fine until I attempt to make it updateable.
The Updateable BAQ functions fine when we run it from an app server.
This error occurs when we run it from 3 different clients, with 2 different Epicor users.

POPUP

Problems in BAQ update processing

Input mapping expression for ‘PartTran.Company’ field is invalid: Predefined type ‘System.Void’ is not defined or imported
The type ‘Object’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’.
Predefined type ‘System.Object’ is not defined or imported
Predefined type ‘System.String’ is not defined or imported

This repeats referencing many fields. I am attaching .docx with the full text.

BAQ error popup.docx (14.3 KB)

1 Like

Have you completed the .NET6 installations as specified in the installation guide? It is possible that the issue may not be present on the server but only on your client PC. Could you please check to see if this is the case?

Thanks
We have solved the problem as noted in post. This was just an FYI.

You are correct in the problem was only on the client. Worked fine on server.
The solution was complete removal of the client (which was updated from 2022.100.13 to .16 automatically).
Then a fresh install from the server. Fixed two clients so far.

From another post, we seemed to have the sdk and runtimes on the server.
We even started guessing and installed the sdk onto the client.
Scott

I guess I spoke too soon.

The two clients that function properly with an updateable BAQ only have runtime
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App].

Other clients with runtime Microsoft.NETCore.App 6.0.xx [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] still have the popup problem.

All clients and servers have the .NETFramework, Version=v4.8

I will start asking questions on what did and did not get covered from the instructions.

Scott