SharePoint user mapping -

When a user name or e-mail is assigned to a user column like `Modified By` or `Created By` validation for existence is performed.

When a user name do not exist then by default the user name associated with the SharePoint Connection is used instead and a warning is issued.
You can specify a specific user name and validate that it in fact exist.
Also, you may use a Variable in place of a hard coded name.

*The validation is done using API call to SharePoint.Client.EnsureUser()
Notice that Microsoft has its own user lookup algorithm and a non-unique username may resolve to a user that was not the intention. So ALWAYS specify a unique username like an email address instead of a users real name.

What happens when assigning a username to a user column like [Created By]
The associated Transformation is executed (if any)
A non case sensitive lookup in the built-in Value mapping list named “SharePoint user mapping”. If a match is found, the “Replacement value” is used in stead. If no match is found, an entry is added to the list with the username in the “Search value” column and the “Replacement value” column blank.
The SharePoint API method EnsureUser() is called to resolve the username to a valid user reference. If the call FAILS, then the “default user” as specified on Options tab is used instead.
An entry is added/updated to the “Validated SharePoint users” report with the validation result and if validated OK, the User/Group Title

*For M365 you can just let the name pass through even it does not exist as a valid user.
On the Options tab specify the default user to Allow any user name (Only M365)
(Se Specific to SharePoint Online (M365) below.)

*Test job for user validation prior to actual transfer
You can verify the usernames BEFORE the actual data is transferred by running the job in test-mode. Then all validations are done but no data is transferred to SharePoint.
Then you can edit data transformations and user mappings to meet your mapping requirements.
Notice that the Value mapping list “SharePoint user mapping” automatically get populated with all user names that do not validate thereby enabling you to identify missing mappings.

Specific to SharePoint Online (M365)

Specific to SharePoint Online (M365)
Apply user names that do NOT exist. You may use the option `Allow any user name (Only M365)` to allow any user name that do not exit to “pass through”. So basically you can use any string value as a user name when this option is selected. This is also true for creating a Folder or Document Set based on Variables or hard coded values. To dynamically enable this feature you can use a Variable having the value AcceptAllUsers@SharePoint Notice that this feature can only functions when a file is created or replaced and is only supported in the Step class File Management
You may use the built system in user account app@sharepoint. You can select the SPO system, account from the Drop-Down-Menu

Apply user names that do NOT exist.
You may use the option Allow any user name (Only M365) to allow any user name that do not exit to “pass through”. So basically you can use any string value as a user name when this option is selected. This is also true for creating a Folder or Document Set based on Variables or hard coded values. To dynamically enable this feature you can use a Variable having the value AcceptAllUsers@SharePoint
Notice that this feature can only functions when a file is created or replaced and is only supported in the Step class File Management

You may use the built system in user account app@sharepoint. You can select the SPO system, account from the Drop-Down-Menu

Last modified: 9 December 2022

SharePoint user mapping

When a user name or e-mail is assigned to a user column like Modified By or Created By validation for existence is performed.

When a user name or e-mail is assigned to a user column like `Modified By` or `Created By` validation for existence is performed.