Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Hello, We modified an existing user csv and corresponding SAV file, combining delimited attributes in a single field to free up user attributes needed for a different use case. We tested thoroughly in DEV and all works as expected. In PROD the job...
When we send a rest V5 UpdateUser API request to our DEV system, the first attempt fails (http 500), a second request sent immediately after succeeds. Any ideas of what the problem might be...?Payload: {
"propertytosearch": "employeeid",
"...
We have a requirement for unique user CNs as accounts can change OUs based upon their relationship to the organization (temp, contractor, employee,...). How do we check for existing new user CNs in AD and append a numeric suffix if it already exists...
The SAV file and an example row of the CSV are attached. I uploaded the SAV file (renamed from ProviderUSERS.sav) manually via File Directory. The CSV was delivered by Rhapsody, our ETL tool that delivers several files to Saviynt. The CSV is in a ...
Thanks for the response, Sivagami. It appears that the SAV file is loaded. The CSV is in a different format, not as many columns. Log entries attached - seem to show the csv format is the issue, is there around this, we need to re-purpose the att...
Thank you @rushikeshvartak. This is still an issue. I updated CHECKFORUNIQUE to: {"cn":"${user.firstname} ${user.lastname}###${user.firstname} ${user.lastname}1###${user.firstname} ${user.lastname}2###${user.firstname} ${user.lastname}3###${user.fir...
