Getting the Object reference not set to an instance error while creating the sales order.

(2) Share

Report

Posted on by spidey1010

201

I am getting the "Object reference not set to an instance of an object" error while creating the new sales order. On debugging its hitting to the standard code. Steps already that I tried - rebuild model, get latest of code and rebuild model. remapping of the branching. But all in vain.

Can you please tell any way of resolving this ?

Categories:

Microsoft Dynamics AX

I have the same question (0)

All responses (5)

Answers (0)

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

Like (0)

Report
Copy link

Link copied!

As you see, just knowing that the exception is thrown somewhere in the standard code tells you nothing about the actual cause, therefore you need to keep debugging to find the place where it happens.

Which version of AX are you using? Knowing that will allows to give you advice relevant to the your version. You mentioned a model, so it sounds like AX 2012, or maybe you've selected a wrong category and you actually mean F&O.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Spidey1010,

Despite the debugger stopping with the error in standard code, this might be caused by a customization. I think to understand that you have customizations in this environment. If so, check if you fill in some values with invalid data or no data at all.

If you have customizations, please share more details, such as the coding.

Was this reply helpful? Yes No
spidey1010 201 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre,

I am not sure about customisations because, the code is fully latest with the same code working on other VMS. Even in call stack no customisation code is coming in the error.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Spidey,

Do you have the same issue in an environment without customizations? When you start debugging, forget about the fact that coding is standard, try to check which parameters are send to methods in the standard application before the error is raised. You can then see if some values are missing or if wrong data is passed.

Was this reply helpful? Yes No
Sagar121 1,160 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @spidey1010,

I will check the same behavior in another environment. If the issue doesn’t occur there, it’s likely due to a recent customization which blocking SO creation you can remove and then verify. There could be issue with Data as well try to refresh you AxDB.
If you have Dual-write is enabled, it sometimes gives silent error.

You should also check the data entities for SO.

Was this reply helpful? Yes No