If you know the loginid you could try to log a ticket/SR against Internal Services, add the LoginId as a hidden field using the Employees pick list then use the $([OtherObject]RecId) to obtain the correct RecId for your user. Then a QA or workflow to Search and Link the correct user?
Where is the loginid coming from another BO, email or import?
From 2016.1.x you can import a name directly to the ProfileLink field and it will look up the user and correctly link them to an object, I havent tried a loginid but that might be possible as well if your importing.
Depending on context, it should be something like: $([Employee#. where LoginId = "jaystapleton"]RecId)
Not sure if that would translate, since LoginId is inherited from the Identity Contract, not native to Employee#
I get a syntax error when trying your approach. Are you saying we should be able to query a BO dynamically like that?
Error: Field ProfileLink_RecID: The relationship reference
[Employee#.]is ambiguous; possible references are
It's related to what i'm trying solve in this thread: Linking a SR to a different user in a RO workflow
I collect the First and Last name and generate a new employee, and based on my business rules I know my login Id is generated in a particular way (ex: John Smith = jsmith).
I'm confused by what you mean on the Search and Link the correct user, is this a particular Quick Action or Workflow block???
Also I tried entering the expected login name (ex jsmith) and full name (ex John Smith) in the Contact_Link (aka Profile_Link in a SR) but neither seemed to have triggered the automatic lookup and link. Perhaps i'm entering it wrong? Should it be in quotes?
I see in your other thread what you're trying to do.
I've started a similar process. I created a new relationship between SR and Employee "EmployeeSubjectSR"
At that point, you can keep the link between the Subject employee separate from the link to the Owner/Submitter.
Once this relationship is established, you can use the Search and Link quickaction to fill it.