Compilation error in AX 2012 - Variable has not been declared.

(0) Share

Report

Posted on by krishna.rao@dax

3,022

Hi Team,

I'm getting below compilation error in customized class, where it's calling reference /TransformAXIntegrator//

Error: /Variable TransformAXIntegrator has not been declared./

1. TransformAXIntegrator is a reference, I could see in References node. This error is coming only in UAT not in production.

2. I could see TransformAXIntegrator in both client and server bin folders

3. I tried a) adding this reference again from AOT client bin folder, restarting AX service. not worked b) deleted reference file in UAT, copied TransformAXIntegrator file Prod to UAT, adding this reference again, restarting AX service. not worked

Can someone here please guide on this issue..

Find below screenshot for reference of the error and reference.

I have the same question (0)

All responses (4)

Answers (2)

Sort by

Verified answer

Martin Dráb 239,660 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Compilation uses the file on client. If it's there, make sure it's the right version. Also, it's possible that this assembly is fine but what can't be loaded is one of its dependencies.

If you can't see anything suspicious, Assembly Binding Log Viewer might tell you more.

Was this reply helpful? Yes No
Verified answer

krishna.rao@dax 3,022 on at

Like (0)

Report
Copy link

Link copied!

This issues is due to missing installation of third party services.

Was this reply helpful? Yes No
Francesco 524 on at

Like (0)

Report
Copy link

Link copied!

Hi Krishna,

Did you get this resolved? I'm having the exact same issue with a new AX server using Transform.

Was this reply helpful? Yes No
d365solutiosn 2 on at

Like (0)

Report
Copy link

Link copied!

I have the same problem with this DLL from Bottomline Technologies for Precision Forms and cannot get around the problem either. The DLL properly exists in all required directories. The other DLL's from Bottomline work, but not this one. It is most likely due to incompatibility with later versions of AX 2012 because the DLL's are from AX 2012 RTM days.

Was this reply helpful? Yes No