Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers!
Enter the sweepstakes now!Prepping for a Fabric certification exam? Join us for a live prep session with exam experts to learn how to pass the exam. Register now.
Hello All,
I created a pipeline in the MS Fabric environment and added an additional column on the source tab.
My pipeline fetches data from a lakehouse and loads that data to a warehouse.
This column is integer type, as I have assigned it an integer variable.
However, when I go to the mapping screen, I notice that the column type is shown as a string. How can I get this mapping to change? I am curious because a couple of videos that I have seen on youtube demonstrated the column type change on this screen. On the screen, the name of this column is "LeaseStatusKey".
Solved! Go to Solution.
Hi @abhidotnet ,
Thanks for using Fabric Community to post your query.
Thanks @suparnababu8 for your prompt response.
Currently, when an additional column is added directly in the source tab of the Copy Data activity, the UI does not provide an option to explicitly define or override the data type. In such cases, the system may infer the column as a string by default, even if the value appears numeric.
In the scenarios you’ve seen in youtube videos, it’s possible that the column was added at an earlier stage , such as within a Lakehouse view or Dataflow , where the data type was already strongly defined. This typically results in the correct type being reflected automatically in the mapping screen.
As a workaround, defining the column in the Lakehouse itself (for example, via a view) and then using that as the source in your pipeline can help ensure more consistent behavior during mapping.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to assist others with similar issues and a kudos is always appreciated.
Thank you.
Hi @abhidotnet ,
Thanks for using Fabric Community to post your query.
Thanks @suparnababu8 for your prompt response.
Currently, when an additional column is added directly in the source tab of the Copy Data activity, the UI does not provide an option to explicitly define or override the data type. In such cases, the system may infer the column as a string by default, even if the value appears numeric.
In the scenarios you’ve seen in youtube videos, it’s possible that the column was added at an earlier stage , such as within a Lakehouse view or Dataflow , where the data type was already strongly defined. This typically results in the correct type being reflected automatically in the mapping screen.
As a workaround, defining the column in the Lakehouse itself (for example, via a view) and then using that as the source in your pipeline can help ensure more consistent behavior during mapping.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to assist others with similar issues and a kudos is always appreciated.
Thank you.
Firstly, thank you for replying. I do not wish to add additional columns, but I will look into it.
Hello @abhidotnet
I think whatever you saw in youtube videos, it's chnaging bcz of they are copying the table first time from lakehouse to warehosue. That's the reason to chnage the data type.
I also replicated the same scenirio, but it's showing the same for me.
But when you add a new column in source tab, I hope there is no provision to chnage the data type. I may correct or not. But you can see the following image, there is a option called faltten type. But it's not showing for me.
I think it supported for only above connectiore in the image, if am correct.
If you need more infoe pls go thorugh below links. It might helps you.
Data type mapping in a copy activity - Microsoft Fabric | Microsoft Learn
How to copy data using copy activity - Microsoft Fabric | Microsoft Learn
Data types - Microsoft Fabric | Microsoft Learn
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
User | Count |
---|---|
35 | |
32 | |
18 | |
8 | |
6 |
User | Count |
---|---|
52 | |
48 | |
16 | |
13 | |
11 |