Known Issues for Data Integration

When the conflict resolution is set to Retain for a copy project operation, if a source object is not present in the target project, the target object might not be created in some cases.

We are aware of the issue and working on a resolution.

After creating a project by copying from an existing project that has a pipeline, the error Failed resource detail: Type TASK, Key <key value> displays when attempting to select a published task for a task operator in the pipeline.

We are aware of the issue and working on a resolution. Meanwhile, after you make sure you have updated any copied data assets and published the copied tasks to an application, do the following in the copied project:

1. Open the pipeline.
2. Select a task operator in the pipeline.
3. In the properties panel, click Select.
4. Select a published task. Ignore the error notification that displays.
5. If there are other tasks in the pipeline, repeat step 2 through step 4 for each task.
6. Click Save and close to save the pipeline.

When you reopen the pipeline, you will no longer see the errors for the updated task operators.

In a REST task for a long-running API operation, when the success condition uses the ${PARAMETER_NAME} syntax, the evaluation of the success condition during running of the task fails.

We are aware of the issue and working on a resolution.

In a data flow where the Object Storage source type is Excel, and the check box to Fetch file metadata as attributes is selected, file metadata attributes such as file_name and object_size are missing on the Attributes and Data tabs of the data flow.

We are aware of the issue and working on a resolution.