[Job.UserEmail] stays empty

[mireille]

Hello everyone,

It's probably a newbie question, but I've got a strange problem with my Job Variable [Job.UserEmail].

In my first flow the 3 variables

[Job.UserEmail]
[Job.UserName]
[Job.UserFullName]

are perfect accessible throughout the whole flow in different folders, connections or metadata properties.

But when I pack the job, transfer it to the next flow and unpack the job, only [Job.UserName] is present.
[Job.UserFullName] and [Job.UserEmail] got lost and remained empty.

In my opinion it has nothing to do with the pack/unpack action, because when I tried that working in the first flow, the 3 variables were present after the unpack configurator.

Does anybody got a solution for this? How can I transfer my job to the next flow and preserving the job.variables at the same time?

Hope to hear from you soon.
Thanks in advance !!!

[sander]

I have this issue too, but without pack/unpack between it.

Via a Submit Job all three variables are available. However via a checkpoint all information is lost, except [Job.UserName] like in your case.

My Switch users are added via Active Directory.

Looks like a bug..

[gabrielp]

Sounds like a bug to me. I haven't really used those variables, but if you want a band-aid, you could write those values to PrivateData within your first flow and it sounds like they will be available in your other flows since the rest of the metadata is fine.