Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedJoin us at the 2025 Microsoft Fabric Community Conference. March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for $400 discount. Register now
In my pipeline I added a copy data activity with a OData endpoint as source and a Fabric datawarehouse as the destination without using the mapping functionality. I don't use the mapping because I want to use the copy data activity in a for each loop to get data from multiple endpoints dynamically.
When I run the pipeline with a single table or multiple tables the tables are succesfully created in the Fabric datawarehouse. The problem is that there is no functionality to suppress the OData metadata. The result is that every destination table has two extra columns with the OData url of the endpoint and every column header starts with the value value. It's no option to use an extra header Accept - odata.metadata=none because the use of this header is not allowed when you use the REST source connection.
Does anyone have a solution for this?
Solved! Go to Solution.
Hi @BastiaanKr
Thanks for using Fabric Community.
Currently, as you’ve mentioned, Fabric does not support the use of the Accept: application/json;odata.metadata=none header in the REST source connection.
Dataflow Gen2 can potentially be used in your scenario to achieve the desired data shaping without the extra OData metadata columns.
1. Utilize Dataflow Gen2 with Staging Storage:
https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-end-to-end-dataflow
https://learn.microsoft.com/en-us/fabric/data-factory/transform-data
https://www.youtube.com/watch?v=ZrDXzLQG7nI
2. Load Transformed Data to Warehouse:
Hope this helps. Please let me know if you have any further questions.
Hi @BastiaanKr
Thanks for using Fabric Community.
Currently, as you’ve mentioned, Fabric does not support the use of the Accept: application/json;odata.metadata=none header in the REST source connection.
Dataflow Gen2 can potentially be used in your scenario to achieve the desired data shaping without the extra OData metadata columns.
1. Utilize Dataflow Gen2 with Staging Storage:
https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-end-to-end-dataflow
https://learn.microsoft.com/en-us/fabric/data-factory/transform-data
https://www.youtube.com/watch?v=ZrDXzLQG7nI
2. Load Transformed Data to Warehouse:
Hope this helps. Please let me know if you have any further questions.
Hi @BastiaanKr
We haven’t heard from you on the last response and was just checking back to see if you got some insights regarding the query. Otherwise, will respond back with the more details and we will try to help.
Thanks
Hi @BastiaanKr
We haven’t heard from you on the last response and was just checking back to see if you got some insights regarding the query. Otherwise, will respond back with the more details and we will try to help.
Thanks
HI @v-nikhilan-msft,
I am aware that you can also use a dataflow gen2 for the ingest. I have tested this and the advantage is that I have no issues with the Odata metadata.
The disadvantage for me is that I have to manually set all column types correctly. This in itself does not have to be a problem if you want to do both the ingest and the transformation in one step.
Hi @BastiaanKr
Thanks for the reply. Unfortunately Fabric does not support the use of the Accept: application/json;odata.metadata=none header in the REST source connection. So the only way is using dataflow gen2.
Hope this helps.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Fabric update to learn about new features.
User | Count |
---|---|
6 | |
4 | |
2 | |
1 | |
1 |
User | Count |
---|---|
13 | |
10 | |
5 | |
5 | |
4 |