How to Enable and Disable User Account by Epicor Function

[klincecum (Kevin Lincecum)]

[mbayley (Michael Bayley)]

Can someone explain why BeforeImage is required on some services, but not with others? Seems totally random

[klincecum (Kevin Lincecum)]

@mbayley

Can someone explain why BeforeImage is required on some services, but not with others?

It’s how Epicor, or (YOU) determine if a field has changed.

You can get away with it, if Epicor isn’t checking, or if you aren’t checking conditions in a bpm.

In this case, I don’t have any BPMs checking, but the base obviously must be checking.

@josecgomez has a larger write up on it, let me see if I can find it.

[klincecum (Kevin Lincecum)]

Kinetic, UBAQ, BPM works in classic but not web (Hints)

There’s a few posts on the Before Image stuff that might be helpful: But basically the before Image snapshot (from progress) was at one point adapted into the SQL Uplift and its how epicor does the “Field Changed from X to Y” it just means you get the same row twice one with and one without changes. Sometimes in BPMs you have to even do it yourself like in the above example. Then Epicor literally does a little LINQ query comparing the Before and After fields to see if it changed. This was don…

Update BO Deleting PackSlip

Sooooooooooo… you don’t just wanna take it at face value? The explanation is long winded (and my memory is spotty) lol So back in 9 or possibly 8 (6???). Progress had these shadow records called BeforeImage https://knowledgebase.progress.com/articles/Article/P17959 Its basically a transaction which keeps track of what’s changed in case there is an error. Some of Epicor’s logic used this BeforeImage records to figure out if something changed. For example on a BPM when you say Condition of Fie…

[mbayley (Michael Bayley)]

@josecgomez

@hmwillett

I’ve been a certain combination of lucky/naughty because I didn’t even know that was thing

We have all been doing it, it works 89% of the time without it, but that 11% is a pain in the ass.

So the safest way is to always add those 3 lines of code to do the BufferCopy. Is this something we should be doing? I guess we’re lazy and omit this step until it bites us.

[klincecum (Kevin Lincecum)]

@mbayley

I guess we’re lazy and omit this step until it bites us

That’s exactly what happens lol.

We just had a discussion on getting bit a few days ago.

@mbayley

So the safest way is to always add those 3 lines of code to do the BufferCopy.

Not sure which specific code you are referring to, so not exactly sure, but as a general idea, yes, I believe all the things should have a BeforeImage.

[mbayley (Michael Bayley)]

@klincecum

//UnModified Record -> BeforeImage...
var userFile = dsUserFile.UserFile.FirstOrDefault();
  
//Get a new Record, this will be our updated Row
Ice.Tablesets.UserFileRow updatedUserFileRow = (Ice.Tablesets.UserFileRow)dsUserFile.UserFile.NewRow();
  
//Copy the unmodified row to the new row
BufferCopy.Copy(userFile, updatedUserFileRow);

I have something similar to this in a function template library somewhere for our other devs to copy.

Thanks for the links. Now at least I know why

[tpynepeak (Tim)]

@klincecum

uf.Update(ref dsUserFile);

Thank you Kevin.

I was going crazy. I have a function that adds and sets users so I copied it down and stripped it down to just change UserDisabled and RowMod and it would throw generic object errors. This fixed it. Same code now but I buffer add a row before I do so and it just works now

Ha I didn’t have to do it with disabling employees.

Making a tool to quickly onboard and offboard users and employees.
The onboarding one is functional, just need to test all the case combinations then on to offboarding.

[Hally (Simon Hall)]

So does your onboarding process use the new copy user?

[tpynepeak (Tim)]

I had no idea there was such a function. Thanks for bringing it up. I took a quick peek to see how it works. On investigation I do not use the copy user BO.

My screen goes a bit further. It will set up the user, their system access, groups and work forces.

If you specify employee options it will also set up an employee, their access and their resource in a resource group - warehouses etc.

The next and last piece I will be adding is a buyer component to set up their purchasing access and approver (if needed).

I did a trial run of what I have so far and it set up the user, their workforces, employee and resource in a few seconds from picking a few options (Department, Manager, are they a machine operator etc).

When I tried Epicors Copy user it was slow, did not do as much and glitched out. I had to restart the user screen to see if it worked which it did but it did a lot less than what I am building.

The other module that I am trialing now is offboarding. I can deactivate a user.