Open Data

The Open Data action opens the following databases:

  • Access 97-2003 Database (*.mdb)

  • Access 2007-2010 Database (*.accdb)

  • dBase III Table (*.dbf)

  • Comma-Delimited Text File (*.csv, *.txt)

Note: The Actions Quick Reference provides a complete list of actions that you can print for easy reference.

  1. Click Data in the Actions menu.

    The Actions list expands.

  2. Click Open Data.

    The Action Builder opens.

  3. Select the Source Database File.

  4. If you selected a dBase III Table (*.dbf) file, click OK to save the action.

  5. If you selected an Access Database (*.accdb, *.mdb) file, enter or select the Table to open and then click OK to save the action.

  6. If you select a Comma-Separated Value file (*.csv, *.txt) file, follow these instructions:

    Note: Because Nintex RPA LE does not work directly with Comma-Separated Value (*.csv, *.txt) files, you must import the data into a dBase file (*.dbf).

    1. Select the Destination data file, which is the database that will house the data imported from the .csv file. If the destination file already exists, select Overwrite existing destination file.

    2. Specify the range of records to import from the Start at and Stop at settings. You can choose to start importing from the beginning or from a specific row number.  You can also choose to stop importing at the end of the file or at a specific row.

    3. If the first imported row contains field names, check the Start Row contains Field Names.  This tells Nintex RPA LE to use those field names rather than generating generic field names (Field1, Field2, etc).  Generic field names will be generated if the field names are not included in the data being imported.

    4. Specify the delimiter used in the .csv file. This is how Nintex RPA LE knows where to split the data.

    5. Click Define Fields to control which fields are imported and to customize the name, data type, and length of each field.

    6. Click OK to save the action.

  7. If the action is inside of a Before Task, from the Run drop-down list, select to run All records or to run Once when the action is executed. If the action is outside of a Before Task, inside of an After Task, or inside of a Normal Task, it will only run once when it is executed.

  8. If needed, adjust the Run Error Task settings to fine tune how the action runs:

    1. Click Run error task.
    2. Open the On Error drop-down list and select the required setting:
      • Run error task: A botflow containing an error task automatically runs the error task in the event of an error. If the botflow does not contain an error task, the botflow stops in the event of an error.
      • Stop on error: The botflow stops in the event of an error.
      • Ignore errors: The action is skipped in the event of an error and the botflow attempts to execute the next action.
    1. Click X to close the drop-down and save the setting.