Forum Discussion

BastiaanKr's avatar
BastiaanKr
Regular Visitor
2 years ago
Solved

Metadata ODate endpoint

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?

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    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:

    • Instead of directly writing to the Fabric data warehouse, use a Dataflow Gen2 for transforming the data.
    • Within the Dataflow, employ transformations to exclude the desired columns. 
    • Rename the desired columns according to your preference.
    • For more information on how to transform the data please refer to these links:

    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.

    • Anonymous's avatar
      Anonymous
      Not applicable

      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

      • Anonymous's avatar
        Anonymous
        Not applicable

        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