No. It’s possible the dll(s?) it recompiles either did for some reason not compile completely because something was in use, or, the files did not get replaced properly on the app server because it was in use.
I’m not saying that’s what happened, but something to look for.
These
How to determine the last time the data model was regenerated?
The Data Model Regeneration Log can be found in this location on the Application Server:
C:\Users\username\AppData\Local\Temp\Epicor\DataModelGenerator\DataModelGenerator.log
How to check the date of the last data model was regenerated?
You can also check the dates on the Data Model files by looking in the
\inetpub\wwwroot\”ERP10/Kinetic 202x Application”\Server\Assemblies folder. The two data model files are:
Erp.data.999999.dll
Ice.data.Model.dll
This KB
https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=787816cddb00f68c4b91fb5aaf96198e
Greg, we’re gonna start calling you “The KB Finder”.
This all looks fine. I am going to do another regen this morning with everyone out of the environment and see if anything changes.
Run SQL query to check row counts of the base table and ud table are the same or not.
Good thought but they are the same
Fresh regen yielded no changes.
I removed the new fields that were added right before the issue and reverted to the last Customization on the Part screen and the error still persists.
And you’ve double checked that the field idxCategory_c in your dataset is not null before it calls update?
Yes I have confirmed that it is either blank but not null or has the previous value and is being passed correctly.
Do you have any SQL table triggers or BPMs that trying to update other company’s data?
Could you explain what you mean by this? I am not sure I understand the question.
You dont have any mappings or anything like that?
Try setting a default value in UD Column and run a regen and refresh app pool. See what happens.
This is actually an interesting thought I will try this in the morning.
Mapping or needed default value?
I think neither technically. I set the default value which fixed it, and then set it back to blank and all was well. Guessing something somewhere got corrupted.