Skip to main content
Solved

Validation error while Publishing

  • December 12, 2025
  • 4 replies
  • 43 views
I
Freshman II

Does anyone know what might be causing this issue? I hadn’t published this project before on this instance. I downloaded it via Git, changed the site paths, built it, created a customization project, and uploaded the data from the folder.

On another PC, this project publishes without any issues.



Text:
[2025-12-12 08:23:41.342] Failed to load types from the PX.BarcodeProcessing assembly with the message: Method 'GetBqlTableSystemData' in type 'PX.BarcodeProcessing.ScanHeader' does not have an implementation.
[2025-12-12 08:23:41.369] Failed to load types from the PX.Objects.AM assembly with the message: Method 'GetBqlTableSystemData' in type 'PX.BarcodeProcessing.ScanHeader' does not have an implementation.
[2025-12-12 08:23:41.370] Failed to load types from the PX.Objects assembly with the message: Method 'GetBqlTableSystemData' in type 'PX.BarcodeProcessing.ScanHeader' does not have an implementation.
[2025-12-12 08:24:46.513] Validation failed.
 

Best answer by IlliaSheinAuditSoft

The issue was that the customization was compiled for a newer Acumatica version (24R1.11), while the instance was running an older version where PX.BarcodeProcessing.ScanHeader lacked the GetBqlTableSystemData method, causing a DLL version conflict.

I resolved it by updating the instance using the Acumatica ERP Configuration Wizard, after which the publish succeeded.

4 replies

I
Freshman II

The issue was that the customization was compiled for a newer Acumatica version (24R1.11), while the instance was running an older version where PX.BarcodeProcessing.ScanHeader lacked the GetBqlTableSystemData method, causing a DLL version conflict.

I resolved it by updating the instance using the Acumatica ERP Configuration Wizard, after which the publish succeeded.

A
Jr Varsity I
Forum|alt.badge.img+3

Hi ​@IlliaSheinAuditSoft 
Are the both instances (where package is publising succesfull and where not) are of the same version?
Just FYI: if a customization has dependencies on core libraries, it’s best to build the customization project using the libraries from the specific Acumatica instance where the package will be published. This helps avoid version-related issues.

I
A
Jr Varsity III
Forum|alt.badge.img+1

Hi ​@IlliaSheinAuditSoft 

These errors indicate assembly version mismatch or incomplete/corrupted Acumatica build. 

What's happening:

The PX.BarcodeProcessing.ScanHeader class is missing the implementation of the GetBqlTableSystemData method, which suggests:

  1. Version incompatibility between assemblies

    • Core Acumatica DLLs (PX.Data, PX.Objects) are from one version

    • Customization DLL referenced PX.BarcodeProcessing from another version

  2. Customization compiled against wrong Acumatica version

    • Your customization project references older/newer Acumatica assemblies

    • Need to recompile customization against current instance DLLs

I checked versions 24.201.0052 and 25.101.0153, in both cases the PX.BarcodeProcessing.ScanHeader class does not contain the implementation of the GetBqlTableSystemData method.

If you have the project and source code, you need to do the following:

  1. Open the Customization extension library project in Visual Studio
  2. Try to rebuild the project. If the project builds without errors - check which Acumatica version it was intended for.

Next, you should do the following:

  1. Replace the Acumatica library References with the version you want to install your customization on
  2. Fix the errors in the code
  3. Rebuild
  4. Try to install.
     

But...

Everything might turn out to be even more complicated, you may need some special version of Acumatica, for example Manufacturing Edition

Oleksii Sliusar | www.linkedin.com/in/oleksii-sliusar-679093250 | If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*
I
I
Freshman II

Hi ​@aleksandrsechin 

I had version 24.111.XXXХ. I’m writing ХXXX because I’m not sure what the exact number was. After updating this instance via the wizard, its version became 24.111.0011, the same as on the other instance, where I hadn’t made any changes.

Terms & ConditionsCookie settingsAccessibility statement
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved