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

GenerateUniqueValue conflict filter parsing starts-with #108

Open
FIMTooler opened this issue Apr 7, 2022 · 0 comments
Open

GenerateUniqueValue conflict filter parsing starts-with #108

FIMTooler opened this issue Apr 7, 2022 · 0 comments

Comments

@FIMTooler
Copy link

I have a somewhat uncommon situation where accountName is not used as the prefix with UPN and Email address. When I put in the conflict filter of /Person[starts-with(Email,'[//Value]@')] the workflow crashes within the SetAttributesToReadForConflictResources method.

I looked into the source code for that function and it seems that is expects the Starts-With to only include the [//Value] and not [//Value]@. In this case the @ is necessary since we're searching only the prefix of the email address. Without the @ included in the Starts-With, a unique value of JSmith may incorrectly return a conflict with an email address of JSmithfield@domain.com.

The code below shows the endToken where it expects only '[//Value]' and won't support '[//Value]@'.

string endToken = "'[//Value]'";

Could someone look at parsing the Starts-With in a better way? Simply removing the trailing ' would work for my situation. Consider using the first index of , after the "Starts-With" string (startIndex value) as another possibility.

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

1 participant