What causes Fabric Copy Activity Error 20747?

The 'invalidFileName' skipErrorFile setting was applied to a sink connector that does not support it. A pipeline template or cloned activity carried over skipErrorFile settings incompatible with the target sink. The sink connector was changed after initial pipeline authoring without updating the skipErrorFile configuration

How do I fix Fabric Copy Activity Error 20747?

Step 1: Open the copy activity in your Fabric Data Factory pipeline editor and navigate to the sink Settings tab.. Step 2: Locate the 'skipErrorFile' configuration block in the sink settings or the advanced JSON payload.. Step 3: Remove the 'invalidFileName' property from the skipErrorFile object in the sink configuration.. Step 4: Save and republish the pipeline, then re-trigger the copy activity to confirm the error is resolved.. Step 5: If invalid file name skipping is a business requirement, evaluate alternative sink connectors or pre-validate file names before the copy step.

Medium severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Copy Activity Error 20747

What does this error mean?

The 'invalidFileName' option in skipErrorFile is not supported for the specified sink connector. This setting must be removed from the copy activity payload.

Common causes

1The 'invalidFileName' skipErrorFile setting was applied to a sink connector that does not support it
2A pipeline template or cloned activity carried over skipErrorFile settings incompatible with the target sink
3The sink connector was changed after initial pipeline authoring without updating the skipErrorFile configuration

How to fix it

1Step 1: Open the copy activity in your Fabric Data Factory pipeline editor and navigate to the sink Settings tab.
2Step 2: Locate the 'skipErrorFile' configuration block in the sink settings or the advanced JSON payload.
3Step 3: Remove the 'invalidFileName' property from the skipErrorFile object in the sink configuration.
4Step 4: Save and republish the pipeline, then re-trigger the copy activity to confirm the error is resolved.
5Step 5: If invalid file name skipping is a business requirement, evaluate alternative sink connectors or pre-validate file names before the copy step.

Frequently asked questions

Is error 20747 the same as error 20746?

They are closely related but distinct: error 20746 refers to an unsupported 'invalidFileName' skipErrorFile setting on the source connector, while error 20747 refers to the same unsupported setting on the sink connector. The fix is the same — remove 'invalidFileName' from the relevant side of the copy activity.

Will removing 'invalidFileName' from the sink cause data loss if invalid file names are encountered?

No data loss occurs from removing the setting — it simply means the activity will no longer attempt to skip files with invalid names on the sink side. You should implement upstream validation logic if handling invalid file names is a requirement.