Skip to main content
Nintex Community Menu Bar

Format of person via LookUp-query

  • April 20, 2020
  • 1 reply
  • 20 views

Forum|alt.badge.img+1

Hello,

 

I want to query a person via a LookUp in a Nintex form.

A Calculated Value I have the following formula:

lookup("Employees", "Name", applicantInputPreferredName, "Manager")

Explanation:
Employees - LookUp list
Name - field with the users (person field)
applicantInputPreferredName - This is the user whose manager I want to query
Manager - "Person or Group" field in which the manager appears

 

The query works perfectly.

 

My problem: The result is the manager in the format 10;#Mueller Steffen
But I would like to have the format i:0#.w|global[userID].

 

Is there a way to specify the desired return format for a lookup() of a person field?

 

All posts about similar topics, want to find out the display name, email address or other information, but they all have my desired format as starting point. But with 10;#Mueller Steffen I can not do a userProfileLookup(), right?


Background: The manager should be inserted into a person field via "PeoplePickerApi". I can cut off the "10;#" with JS and search for "Mueller Steffen", but if there are two employees with the same name in the company, the wrong one might be inserted. Therefore I would like to search for the unique login (or whatever the format is called above).

 

BTW: If somebody knows a page that lists all formats for a person variable with the formats name, I would be very grateful. I never know what to look for when I need a certain format and also don't have the right words to describe it correctly here.

 

Greetings
Steffen

1 reply

Forum|alt.badge.img+1
  • Author
  • July 27, 2020

Hello,

in the meantime, I have asked a Nintex trainer about the mentioned problem: He was not aware of the phenomenon, but said it could well be that a field in the background would be stored in a different location or in a different way if the initial parameters differed.

Unfortunately once again one of those SharePoint head-shaking moments...

Nevertheless, I would still be interested if somebody knows the problem and maybe can even explain it.

Greetings
Steffen