profile() only accepts properties from UserProfileProperties

[YakQin]

To implement the enhancement in #38 you have made changes to sprLib.user(options).profile(). Now it seems we cannot provide any Properties from Person Properties like 'DirectReports', 'DisplayName' etc

sprLib.user(options).profile('DirectReports') -->this is not working, error: DirectReports"DirectReports property does not exist in SP.UserProfiles.PeopleManager.UserProfileProperties"

sprLib.user(options).profile('Department')-->this is working fine, 'Department' is part of the UserProfileProperties

[YakQin]

i saw this has been fixed in the latest (26th Dec 2018) build

[YakQin]

if the property is an array like below ones, we cannot put it in like profile('DirectReports')

DirectReports
ExtendedManagers
ExtendedReports
Peers

error:
ExtendedManagers"ExtendedManagers property does not exist in SP.UserProfiles.PeopleManager.UserProfileProperties"

[gitbrent]

Hi @YakQin

I see what you're saying, and it did indeed used to work differently.

However, when a UserProfile property name is provided, it's used in a specific query to UserProfile:

SP.UserProfiles.PeopleManager/GetUserProfilePropertyFor(propertyname='SomeProp')

Therefore when using another top-level property name (ex: 'DirectReports') zero returns are returned - as it doesn't exist.

So the fix for your issue would be that the code would have to be aware of which ProfileProperties are "genuine" values so we could query all UserProfileProperty values and filter the one being searched for, which is an ugly solution.

Long story short, I'd prefer users to pull all profiles, then select the [key] they want if it's not a real UserProfileProperty... e.g.: everything not highlighted:

[YakQin]

noted, thanks a lot