3812162 - Why did the Request Header copy the wrong Employee ID?

This issue can occur when a Request Header is opened while acting in one profile and then switching to another profile in a different tab or window. When the original Request Header is saved, it will use the profile you last switched to before saving. In other words, by design, when a Request User switches to another profile in a given browser, all actions triggered by the connected user in Request via this browser will use the active user profile. This behavior explains the discrepancy in the saved Employee IDs.

It's important to note that Concur does not support multiple sessions, and this limitation also applies to the "Acting as" feature. You can only act as one person at a time.

I'm wondering why the Request Header copied the wrong Employee ID. What might have caused this issue and how can we prevent it from happening in the future? , KBA , CON-EXP-ADM-FOF , Forms and Fields , Problem