CSV as a data source for automations

    ADManager Plus' CSV integration allows admins to import data from CSV files or folders for automations. There are two ways in which you can add CSVs and use them as a data source for automations. You can either directly enter the CSV path or integrate the CSV as an application.

    This way, admins can leverage CSV files or directories that support exporting identity data as CSV files for automating various AD, Microsoft 365, and other identity management tasks.

    What is the difference between a CSV file/folder added directly and one that is integrated as an application?

    When the CSV file/folder path is provided directly When the CSVfile/folder is integrated as an app
    During automation configuration, if you choose:
    • Full sync: All object records in the CSV file/folder will be processed for automation.
    • Incremental sync: Only the object records added at the end of the CSV file after the previous automation iteration will be processed.

      • For example, if the previous automation contained 5 lines and the current file contains 10 lines, only records 6 through 10 will be processed.

      Hence, users must add new records only at the end of the CSV file.

    		 During automation configuration, if you choose:
    • Full sync: All object records in the CSV file/folder will be processed for automation.
    • Incremental sync: Any changes made to the CSV since the last automation run will be identified as updates. Once these modified records are retrieved, depending on the action configured, they will be processed for automation.
      • For example, i f the selected task for automation is:
      • Create new users: The newly added records after the previous iteration, irrespective of line number will be processed for automation.
      • Delete users: The recently deleted records after the previous iteration in the CSV file will be processed.
      • Management actions or changes to an automation policy: Modified and newly added rows will be processed according to the automation policy or other specified actions.
    It's mandatory for the CSV header names to match with the Active Directory LDAP attributes. It's not mandatory for the CSV header names to match with the Active Directory LDAP attributes as they can be mapped later.
    The option to filter the data before it's used for automation is not supported. Advanced filter to view the desired attributes is supported.
    When the same object's record appears in more than one CSV file:

    The values will be processed for automation based on the alphabetical order of the records.

    		 When the same object's record exists in multiple CSV files:
    • If the same object record is updated with different values across different files, the most recently modified version will be used for automation.
    • If both a previously added record and a newly added record for the same object are updated in different files, the previous record will be processed for automation first, followed by the new record.

    Steps to provide the CSV file/folder path directly as a data source

    1. Log in to ADManager Plus.
    2. Navigate to Automation > Create New Automation.
    3. Under the section Tasks to automate, while selecting data source for automations, click Direct CSV and enter the CSV file/folder path.

    Steps to integrate CSV as an application in ADManager Plus

    1. Log in to ADManager Plus.
    2. In the home page, navigate to Directory/Applications Settings > Application Integrations > CSV.
    3. Now click the CSV tile and toggle the Enable CSV Integration button on.
    4. Under the CSV File/Folder Paths section, click the Add CSV button.
    5. You can add as many CSV file or folder paths as required. After adding each of the CSV file/folder paths, press enter.
    6. You can click the Response Field Settings icon and change the data type of CSV headers, if required.
      7. Note: Headers in the CSV file must not exceed 150 characters. Any headers exceeding this limit will not be saved or displayed.
    7. Now, under the CSV Header-LDAP Attribute Mapping section, click the Add New Configuration button to map the AD attributes with the CSV Headers and follow the steps outlined below.
      • In the Configuration Name field, provide a valid name.
      • Add a suitable description in the Description field.
      • In the Select CSV File drop-down, choose the CSV file whose headers will be mapped with the AD LDAP attributes.
      • In the Unique Key drop-down, select the attribute which holds unique values based on which the objects from the endpoint would be identified.
      • Select the type of automation from the Automation Category drop-down.
      • In the Attribute Mapping section, map the CSV headers with the LDAP attributes.
      • Once done, click Save.

    Don't see what you're looking for?

    •  

      Visit our community

      Post your questions in the forum.

       
    •  

      Request additional resources

      Send us your requirements.

       
    •  

      Need implementation assistance?

      Try OnboardPro

       
    Copyright © © 2020, ZOHO Corporation.All Rights Reserved.