Batch Request Error

Which IIQ version are you inquiring about?

On version 8.4 in prod and 8.5 in dev

Please share any images or screenshots, if relevant.

image

Share all details about your problem, including any error messages you may have received.

Using a csv file with headers as recommended, I get the same error message over and over. I have accounts that came in with a new application that are in the application-orphan identity type. I have hundreds that need to be saved as Service Accounts or External accounts with the same manager identity for all.

My file is set up as csv with an example:

operation userName manager identityType
modifyIdentity #MOD1 Kirk, Becky External

I’d recommend creating that CSV using NotePad++ or NotePad instead of something like Excel that can enrich the file with custom markers. Also, whenever I do a batch file, I grab the example from the Help page within IdentityIQ. In the top right corner between the Gear and the Alarm icon is the question mark that opens up the help page. Search for Batch request there and they will have several examples. Copy it and paste it using NotePad and it should work that way. Then you can work on adding additional columns. Also, once it’s working, you can open it with Excel and add to it, but make sure you save it as plain CSV since Excel will try to format it by default.

@bkirk123

Please check your file if it has some special characters in the operation column. Sometimes, the issue comes because of that.

Also, open the file in Notepad to make modifications and store it in CSV format.

Putting in notepad was what I needed. The next issue I am having is that the manager Identity is not correlating from my file - manager name lists as last, first and the comma in this I believe is the issue. Is there a different Manager attribute that I should use?

Figured it out!

Any tips on how to batch update orphans for exiting identity cubes - to associate?

Great to hear the initial problem is solved! The value for manager should be the manager’s identity name so it can properly reference the correct manager identity object.

The Identities Correlation page is useful for large correlation efforts. If possible, the application’s where these accounts reside can have their correlation logic updated to ensure it automatically correlates to the correct identities.

Otherwise, you can write a rule to automate it, but at that point, you could just inject that logic in the application’s correlation rule. Or you could write a rule to parse a CSV that would perform the correlation per its contents.

For Manager update, it is advised and better to use the manager correlation from the authoritative application.

Please configure manager correlation configuration or manager correlation rule to update your managers.

Thanks

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.