Finance | Project Operations, Human Resources, ...

Lookup Displays English but Stores Chinese After Changing String Fields to Memo

(0) Share

Report

Posted on by DrastiS_D365

Hi everyone,

I'm facing a strange issue in D365 Finance & Operations and would appreciate any help.

Initially, everything was working perfectly.

Earlier, my table fields were configured as:

Code – String (Size: 20)
Description – String (Size: 50)

Everything worked as expected. The lookup displayed English values, and after selecting a value, the same English value was stored in the database.

Later, I changed both fields to String with Memo size. After making this change, I started facing a strange issue.

Now:

The lookup still displays the values correctly in English.
However, after selecting a value, it changes to Chinese.
I checked the database in SSMS, and the value stored in the table is also Chinese, not English.

I have around 23 custom tables with the same structure (Code and Description), all added to the AutoLookup field group, and I created Data Entities for them. The data was imported successfully using Data Management, and the source data is in English.

Could changing the field size from String (20/50) to Memo cause this behavior? Has anyone experienced something similar or knows what could be causing it?

Any suggestions would be greatly appreciated.

Thank you!

Regards ,

Drasti

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Martin Dráb 240,181 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

If I understand it correctly, you have a table with Code and Description fields, which contains just English values.
But when you select a record in a lookup (when populating another table containing the Code as the foreign key), you get some Chinese texts that don't exist in your database at all. Is that a correct description of the behaviour?

Are the Chinese texts translations of English texts or you get something unrelated?

Isn't the replacement done by your web browser? It sounds unlikely that F&O just make up data that don't exists in the system; the idea that it returns correct data but it gets manipulated on the client seems more legit to me. First of all, try it in a different browser.

Also, note that the data shouldn't get stored to the database, because the reference to an non-existing record means data corruption. This should be normally validated by the system based on the table relation. You have something wrong there too.

By the way, do I understand correctly that you're trying to use Memo for the primary (or replacement) key (Code field) too? This is a bad idea; I believe it can't even be done, because the index creation would fail. This might indicate that your table isn't implemented correctly, because it's missing an index on Code.

Was this reply helpful? Yes No
Suggested answer

vishalsahijwani 280 on at

Like (0)

Report
Copy link

Link copied!

Hi @DrastiS_D365 ,

Try to clear aos cache , usage data for your user and its ok then for all the users. Try restarting your AOS web application and its related services.

Then please check that upon manually entering the value and saving it does it show the text in Chinese. Also after saving please refresh your browser page and then check.

Please try to do a Full Build of your model first and once done then try to do a full db sync. Don't run both processes in parallel as sometimes both build and sync does not perform compilation properly.

Check this field's data type in Sql Server and see if its showing nvarchar and in case of memo it should show nvarchar(max). Then do a select statement and see if the value shows in English or Chinese.

Most likely there can be a scenario that this field or the table itself has gone stale due to which after doing everything right also the values are not appearing properly. If its taking too much time better first try to create a new field and check if the same issue is happening with newly created field as well. If its still there please try to create a new table.

Please try to follow these steps in the exact sequence and then see if its working

Was this reply helpful? Yes No