1. Configuring a Flat File-Based Application
  2. Known Issues and Workarounds

11 Known Issues and Workarounds

These are the known issues and workarounds associated with this release of the connector.

11.1 Multicharacter Delimiters Are Not Supported

If a delimiter containing more than one character (for example, $#) is specified in the flat file and in the main configuration lookup definition, then this error is encountered.

Only single character delimiters are supported with the exception of "tab" and "space".

This is an issue associated with the connector.

Workaround: The connector supports only single character delimiters. You must either provide a file delimited by a single character or use a preprocess task to parse the file and replace all multicharacter delimiters into a valid character.

11.2 Ignore Event API is Not Called

Suppose a target resource or trusted source reconciliation run is performed to reconcile ten accounts or users from a flat file, the reconciliation run is successful. However, if a target resource or trusted source reconciliation run is performed after copying the same file, then the same number of events is created again, and the Ignore Event API is not called.

This is an issue associated with Oracle Identity Manager.

Workaround:

  1. Log in to the Design Console.

  2. Expand Administration, and then double-click Lookup Definition.

  3. Search for and open one of the following lookup definitions:

    • If you performed a target resource reconciliation run:

      Lookup.FlatFile.Configuration

    • If you performed a trusted source reconciliation run:

      Lookup.FlatFile.Configuration.Trusted

  4. Click Add.

  5. In the newly added row, enter the following values:

    • Code Key: Ignore Event Disabled

    • Decode: true

  6. Click Save.

11.3 StartDate and EndDate Values Not Populated in Child Form

If a child form contains fields such as Startdate and Enddate, then after a reconciliation run, data for these fields is not displayed in the UI. However, data is populated correctly in the Oracle Identity Manager database.

This is an issue associated with Oracle Identity Manager.

Workaround: Rename the Startdate and Enddate child attributes so as to not match (case insensitive) the parent attribute names. For example, rename the Startdate and Enddate attributes to From and To, respectively.