on ‎2020 Mar 26 7:39 AM
Request clarification before answering.
is there some limitations (for global assignment, Contingent worker or concurrent assignment) when using userAccountInfo ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If you are having some logic to create the username like a running number series or combination of some alphanumeric number then you can use business rule to populate this at Add New hire screen.
For this you have to enable the 'userAccountInfo' section of Succession data model and this will make the username editable in the Add New Hire screen.
But if you are not looking for the above solution then you can use the integration center or Background provisioning job to update the username.
Username is part of the basic profile (UDF). You can use either of the above to have SFTP based scheduled job to update the Username field.
You can also use the SF OData api to update the user name. The username field is part of the Odata API entity 'User'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.