Importing Information From PeopleSoft

Prerequisites

In Microsoft Azure (https://portal.azure.com/#home), the following folders must be available in the path Common\inbound:

  • peoplesoft-drop – To store the source file (.xlsx or csv) from which data will be imported.
  • peoplesoft-processing – To store the file when the import is in progress.
  • peoplesoft-processed – To store the file after the import is complete.
  • peoplesoft-error – To store a file that includes information of records that fail to import. The extension of the file is inherited from the source file, and it is named in the format <source file name>-Error.

When records are imported, their batch size is determined by the PeopleSoft Import Batch Size integration mapping record. By default, 100 records of each test can be imported in every import batch. The administrator can change this value in the Internal Option Value field in the above Integration Mapping record(s).

Importing Records

The Sample - FileImport - PeopleSoft Microsoft Flow includes logic to import records from PeopleSoft into Anthology Reach.

  1. To import records, place the source file in the peoplesoft-drop folder.
  2. The import operation will start on the next run of the Sample - FileImport - PeopleSoft flow. By default, the flow is set to run daily at 12:00 hours UTC. The administrator can change these settings and also run the flow manually.
    • During an import operation, the source file will be moved automatically from the peoplesoft-drop folder to the peoplesoft-processing folder.
    • After the operation is complete, it will be moved to the peoplesoft-processed folder.
  3. Records of the following entities will be created:
    • Contact
    • Address

    If the records are already available, they will be updated with new information.

Notes:

  • It is not recommended to edit default logic in the flow Sample - FileImport - PeopleSoft. Instead:
    1. Copy the flow and edit logic in the copied flow.
    2. Save and publish the copied flow in your institution’s implementation.
    • That way, the original flow with its default functionality will be available if the copied flow needs to be discarded. Additionally, as concurrency in the default flow is set to 1, it is recommended to retain this value in the copied flow because performance of the operation may be compromised if it is changed.
  • A record of the Integration Log entity is created for each file placed in the peoplesoft-drop folder. It indicates the status of the integration in the Integration Status field with the values Success or Failed.
  • To import content from the <source file name>-Error file:
    1. Delete all content from the errorRowNumber, errorDetails and flowURL columns, including the column headers. These will be displayed at the end of the file.
    2. Save the file with a unique name and then place it in the peoplesoft-drop folder.
      The import operation will start on the next run of the Sample - FileImport - PeopleSoft flow.