CODEWITHSUNDEEP
c#acumatica
MarkJoel60
MarkJoel60

Reputation: 557

Acumatica Error Invalid Column Name But Field is not used in Customization

Here is the scenario:

I have a customer that needed a slight modification to a customized package my company did. So I:

  1. Made a backup of the customer's data from the SQL database.
  2. Setup a new installation of Acumatica using the same revision (Build 21.211.0033)
  3. Restored SQL database to the new Acumatica Site
  4. Ran simple tests, and I get strange errors.

When I try to navigate to a Service Order from screen: FS3001PL, I get the following error:

Error Message - Invalid Column Names

Here's the thing: Those fields do not exist on InventoryItem on the customer's site database where everything is running fine and I am not getting this error.

When I look at the source code of our customization, those fields ARE defined in the DAC extension. But they are never used (as far as I can tell) I tried commenting the fields out, same error. Put the fields back in, Same Error.

The wicked thing about the error, is that it does not throw anything that is catchable in the Visual Studio debugger. I am able to attach to the IIS process, and if I add an event to something like CacheAttached, my breakpoint is hit -- so I know I am in the right source for the DLL, this error does not get caught, even though I have the debugger set to break on any error. So I can't even see what the system is seeing that I am not.

Again This runs fine on the customer's site.

I don't even know how to debug this at this point.

Any ideas would be appreciated!

Upvotes: 0

Views: 522

Answers (1)

Brian Stevens
Brian Stevens

Reputation: 1941

The issue is that they are in the DAC but not the SQL database. Used or not, once defined as a PXDB type field in the DAC, the cache tries to sync the SQL tables for all PXDB fields of the DAC with the database. Hence, your error. You need to either add them back to the SQL table or remove them from the DAC extension.

Check case on the field names and that it is in the right table. There is something misaligned between your SQL and your DAC.

Upvotes: 1

Related Questions