Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exiting assets (people) are ignored #4

Open
Tan-DE opened this issue Feb 10, 2022 · 1 comment
Open

Exiting assets (people) are ignored #4

Tan-DE opened this issue Feb 10, 2022 · 1 comment

Comments

@Tan-DE
Copy link

Tan-DE commented Feb 10, 2022

Since in most cases the field "primary_mail" in the People Asset is empty (in our case at least after an IT GLUE migration), it might be helpful to make the additional field for the email address configurable as a parameter.

Example:
#$HuduUser = $People | where-object { $_.primary_mail -eq $user.UserPrincipalName }
$HuduUser = $People | where-object { ($_.fields.label -eq 'E-Mail') -And ($_.fields.value -eq $user.UserPrincipalName) }
@lwhitelock
Copy link
Owner

The issue with this is every integration can store the email in a different place. The primary email is what should be set now we can do it via the API.
The other issue would be that, that is the mechanism which contacts created by the integration can then be matched so you would also have to add logic to extend it to adding the email to that filed on creation.
The better solution I can think of would be running a one off script to loop through all the imported assets and just update their primary_mail attribute based off the field that is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants