Finance | Project Operations, Human Resources, ...

Cannot read a record in XXX(XXX). An unsupported NULL value has been selected from the database.

(3) Share

Report

Posted on by Migi

304

Hi,

I'm getting the following error when opening the form. A new field was added to it and problem started to occur in our test environment (tier-1). However the same form work fine in development env (tier-1).

Build package was successfully build and installed. I have also run manually dbsync without problems and restarted services on virtual machine.

Any ideas how to solve the problem?

Reset usage data didn't work either (I noticed the same error message in old AX posts and that was suggested as a fix).

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Mohamed Amine Mahmoudi 26,390 Super User 2025 Season 2 on at

Like (0)

Report
Hi @Migi,

this problem occurs when a field in the AOT is not null but the value in the database is null.
to solve this problem, you need to do a select in SSMS to find the null values and then update them.

this is an exemple where the field type of varchar.

UPDATE YourTable SET field= '' WHERE field is null;

Best regards,

Mohamed Amine MAHMOUDI

Was this reply helpful? Yes No
Suggested answer

Layan Jwei 8,097 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Check if this link helps:
https://axandhellisfunafterall.blogspot.com/2011/07/null-value-not-allowed-has-been.html

Thanks,
Layan Jweihan
Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future

Was this reply helpful? Yes No
Suggested answer

Deepak Agarwal 8,598 on at

Like (0)

Report

Hello,

Whats this table by any chance is it a parameter table and whats the property of this new field, like mandatory etc. Did you try to debug this at form or table level.

Was this reply helpful? Yes No
Suggested answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

if you know which field has null issue, try to fix it from the DB using select statement, in order to access the Test DB, you can check the below link:

https://dynamics365musings.com/how-to-connect-to-a-test-d365-database/

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Migi 304 on at

Like (1)

Report

I was managed to fix the problem temporarily by manipulating database:

UPDATE [dbo].[table]
SET [field] = ''
WHERE [field] is null
GO

However it breaks again if new record is created because it gets null value. I checked with SSMS the field in table and it looks like this:

[fieldname] (nvarchar(10), null)

The really strange this is that when I deployed the same package to another environment, it worked there and the field looked like this:

[fieldname] (nvarchar(10), not null)

Now I don't know if it's safe to put this into production because it might work or not. I'd like to fix it via development but don't know if there's a property that affects this null value?

Was this reply helpful? Yes No
Suggested answer

Mohamed Amine Mahmoudi 26,390 Super User 2025 Season 2 on at

Like (1)

Report

Hi @Migi,

I think you must flow these steps :

1. delete the field from table in AOT

2. build + synchro DB

3. re-add the field to table

4. build + synchro DB

Best regards,

Mohamed Amine MAHMOUDI

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (0)

Report

Hi Migi,

Looks like the field was created successfully in D365 FO but the db sync created a field with null type instead of field with the right types. It should created a field with nvarchar, int or bigint etc. in SQL. Looks like it created a field with null types. Have you checked the same?

Thanks,

Navneeth.

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Layan Jwei 8,097 Super User 2025 Season 2 on at

Like (0)

Report

Hi Migi,

If it's "not null" in other environments, then Can you please try and deploy the package again on your test environment?

Thanks,

Layan Jweihan

Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future

Was this reply helpful? Yes No
Migi 304 on at

Like (3)

Report

Thank you all for the replies. I'll update here the solution (if we manage to solve this)

Was this reply helpful? Yes No
Community member 2 on at

Like (0)

Report

I think you can check this link to find answers for yourself
https://dynamics365musings.com/candy clicker /how-to-connect-to-a-test-d365-database/

Was this reply helpful? Yes No