Has anyone had this issue? I created a UD field for the OrderHed table, regenerated the data model the field shows up in App Studio, I place the new field on the OrderHed form. All looks great, I have the field on the form, it can be typed in and looks/as normal. I have a BPM the checks to make sure the field isn’t empty (Make it required) that works well, the issue is this, I put data into the custom field, save the record and if I do a refresh the data is gone as in not saved? WTH, If I save and go to another record and return to the record I just updated the field is still blank. It’s hard to believe that native functionality doesn’t automatically handle the save? Is there something else I’m missing? Any insight would be appreciated. Thank you. FYI, It acts the same if I use orderhed.userchar1 as well, so I’m stumped?
I can say I had issues many moons ago with UD columns where I used underscores in the names. This was prior to our Go-Live and while working with Epicor consultants. We ended up scrapping those fields and recreating them without underscores, and all was happy.
However, I’ve seen others use them without issue. So, even though that was our “solution” at the time, it may have just been a red herring.
The fact that you said UserChar1 also won’t update points to something else going on.
Yes, quite interesting… I have other UD fields working on other forms (Parts) which is why I’m stymied? I have tried to create A New layer and apply the customization only to be faced with the same results. Browser or the smart client, it makes no difference. FWIW, we are on prem, 2024.1.7.
Using the browser trace utility I can see the field change from it’s default to my entered data and the record gets it’s “U” designator but looking at the server response it looks like it is just re-reading the original value.
I’d turn on debugging and expand the update call itself to see what values are being sent. I’ve seen on busy forms before where there are multiple views (similar) views and I was surprised to find the actual one being used for update was different that the one I expected.
