Command Error - Export Objects command fails when object has slashes in the name #58
Description
Hello! Love this extension, it's super helpful!
I ran into an issue while trying to export some objects that appears to be caused by objects names that contain slashes, either forward or back.
In this example, the forward slash in "LYNX Accountant Credit-CSFQR/CCR - IT" seems to be the culprit. We have several object names with backslashes in them that do not fail on my machine, but will fail on a Windows machine. (Please don't ask why we have so many object names containing slashes and other such characters 😄 )
This functionality seems to be fairly similar to that of the Sailpoint-provided XML Object Exporter task. In the documentation for that task, there's a relevant quote with regard to naming:
Illegal characters (anything that is not an alphanumeric character, dot or hyphen)
and spaces will be replaced with underscores, unless the default format is selected,
in which case spaces are removed.
Would you be interested in implementing this for object names?