Can we delete a UD field?
I thought there was time (way back when) where we could add a UD field but not delete it after the data model regen was run.
I don’t think that is still true but I was hoping someone could correct me.
The field is unused - i,e. no data so we do not need to preserve any info.
Comments welcome,
DaveO 651-246-3281
You would still need to regen the model. The issue will be if any BPMs or customizations use it you could be breaking something in the system.
What @Doug.C said plus if there is any reports with that table it could break the report until it’s modified to remove the field.
Mr. Randy: Thank you for the reminder.
I would like to show a new Epicor customer how to add a UD Field – but I do not want to “pollute” his test DB – so I thought I would make sure I could “undo what I do”.
Thanks again,
DaveO
If I recall correctly, you can also back up the full database and restore it afterwards, which might be another useful lesson.
My process has been to add the UD Field, exit the Epicor client, open the Epicor Admin Console, Stop the App Pool, regenerate the data model, start the app pool, and then verify the UD table is synced. You could show them the field is visible in a BAQ too.
To undo, you delete the unused UD Column, then repeat the same process with the app pool and regenerating the data model. Our regen’s are fairly quick, about 2-3 minutes.
Mr. Chris: Thank you for the suggestion. That is a good idea also.
Mr. Andris: Thank you for the process refresher – that should work perfect for this customer.
DaveO
This is my process for UD fields too.
My process for the last 4yrs has been, add them, change them or remove them and recycle IIS on App Server and Agent Server, and I usually leave the Client running. There was 1x it didnt want to show in the drop-down until I restarted the Client. But I have also done this process while production was running in broad day-light, everyones client becomes laggy after you Recycle IIS (not restart), but no one ever disconnects. Highly recommended of course after hours, and if I am touching on lets say the Part table, then I do restart the Task Agent Service atleast. But Recycle has been working fine for me on multi app servers. No issues, with 500+ active sessions.
For deletes, id also take in account somehow forcing clients to restart, if someone has lets say the Part Entry screen cached and you remove a field, their customization layer might still expect it.
Just pointing out that Epicor is flexible, and it wont kick the bucket either way. But if you want to be safe - the Epicor recommended way is IIS Restart.
Haso,
I assume you also regen the data model.?.? Do you regen before or after you recycle IIS on App Server and Agent Server? I am guessing you regen before you recycle IIS.