Unable to edit destination type field pipeline copy data in fabric

[Anonymous]

Problem Description: 

In Fabric's pipeline, one of the copy data activities allows user to edit the type in the destination, but another copy data activity does not allow editing of the type. 

User described: 

• If I create a new pipeline and add just the 1 copy data for exactly the same dataset, it will show these fields (OK)
• In the same pipeline but for other datasets, it shows these fields.
• If I reset the fields, clear unmapped and re-import the schemas on this activity with the issue, it does not allow to edit the field.
• If I create a new copy of the pipeline using the save as function, issue still there.
• It really feels like a bug or maybe hitting some type of limit in the pipeline? There’s are multiple linking pipelines and I can’t really rebuild from scratch.

  

  

  Troubleshooting:

  I attempted to create a copy data activity in my Fabric pipeline and found that I am unable to edit the type in the Mapping section.

  

  Ask: 

  1 Whether this problem is a bug or by design?

  2 When can the 'type' be edited in Fabric's copy data activity, and when can it not be edited?

[v-sgandrathi]

Hi @Anonymous,

I wanted to check if you had the opportunity to review the information provided by @nilendraFabric. Please feel free to contact us if you have any further questions. If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[nilendraFabric]

Hello @Anonymous 

Generally, the ‘type’ field in the Mapping section of a copy data activity should be editable. However, there are some scenarios where editing may be restricted:
Editable Scenarios:
• When creating a new copy data activity using the Copy Assistant or adding it directly to the pipeline canvas.
• When the source and destination data types are compatible and allow for type conversion.
• When using the Mappings tab to configure type conversion settings.
Non-Editable Scenarios:
• When dealing with certain data stores or file formats that have strict type requirements.
• When using staging in copy activities, as the data types may be predetermined by the staging process.
• In some cases involving incremental loads or append operations, where changing the data type might conflict with existing data.

However, the behavior described by the user, where the type is editable for some datasets but not for others within the same pipeline, does not align with these typical scenarios. This inconsistency suggests a bug in the system.

Please accept this solution if this resolves the query 

[Anonymous]

Hello @nilendraFabric  @v-sgandrathi , I'm so sorry to disturb you. 

To better understand and confirm whether this is a bug, could you please provide some relevant proof? For example, images or examples that you believe demonstrate this is not a bug. I appreciate your assistance.

[nilendraFabric]

Hi @Anonymous 

In my answer conclusion I am suggesting that this inconsistent behaviour looks like a bug.

please accept the answer if it was helpful 

thanks

[Anonymous]

Hi @v-sgandrathi @nilendraFabric ,
Thank you very much for your response.

I understand your conclusion. Could you please provide some images for comparison and reference? For example, you could provide some images of the normal situation compared to the ones I provided that show the bug. This will help us better understand and resolve the issue. Thank you very much for your cooperation!

[v-sgandrathi · Accepted solution]

Hi @Anonymous,

As requested, we have attached the comparison images to illustrate the behavior of the type field in the Mapping section.

A normal scenario where the type field can be edited in the Mapping section when the table action is set to overwrite.

A scenario similar to the one you described, where the type field is not editable when we change the table action to append.

Should this information prove useful, kindly mark it as a solution and consider giving us a Kudos.

Thanks for using Microsoft Fabric Community Forum.

[v-sgandrathi]

Hi @Anonymous,

I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.

Thanks for using Microsoft Fabric Community Forum!