BPM - callContextClient.CurrentUserId

Epicor ERP 10
1

We have a BPM that will stamp a custom UD field for user tracking on the LaborHed record. It is a simple data directive that looks like the following:

Capture
Capture.PNG511×505 36 KB

This works fine for all necessary users but 5. After some troubleshooting I found that it fails on the callContextClient.CurrentUserId variable. If I override this to use “any text” it will write to the record but will not user the CurrentUserID variable for the 5 users. If I recreate the user with a different username it will work.

Any ideas on what would cause this?

Thanks,
Ross

2
  1. Are the userid values anything unusual? Do they contain spaces or other random (meaning non-alphabetic or non-numeric) characters?
  2. Can you put in a “display message” box, set up a test scenario, and have the BPM actually throw a message with what it thinks the values are?
3

Ernie,

The users are standard first initial, last name matching our active directory structure. No spaces, odd characters, etc.

When I did the message box it returns a blank. I forgot to include that in the initial post.

Thanks,

Ross

4

Interesting. Sounds like for some reason the BPM isn’t capturing a userid for those folks… are they following the EXACT same procedure for entering labor as everyone else is? What is the actual “approved true” condition logic?

5

A few thoughts:

  1. Epicor 10 stores User data in two tables, its possible one of the tables do no match the other.
    Check and compare the contents on these two tables:
    ERP.UserFile
    ICE.SysuserFile
    After upgrading from Epicor 9 I had some problems with new users that were only created in Epicor 10.0 where after a password reset the user could not login and it gave a funky error. Got a workaround but the issue apparently was between these two tables, I do not recall the details.

  2. Are the users with the issue using a different type of client, say MES or Handheld?
    Perhaps there is a session bug with those modules?

6

Same exact process. I have done it to verify and troubleshoot. The approved logic is “field: Approved_C has changed from any to TRUE”

Thanks,

Ross

7

Thanks, Rick. I will investigate those tables and see if I can find anything. They are new users created in E10 but it is worth a look.

The users have been in both scenarios…some with main client sessions only and some with MES, handheld and/or main client.

I will report back what I find.

Ross