Data is empty when creating a table with an OData Expand feature RRS feed

  • Question

  • Hello,

    I need to create a table from a OData query. This is working correctly with a simple OData query.

    However this is not working when using Expand OData Feature. Is this a bug or a limitation? If this is a limitation, do you know if this is planned in the roadmap? If not do you know an alternative way for me to still do the extraction?

    Why do i need to do this? Because the OData Service I am using is not exposing technical tables for multilink.
    For example I have

    Table A
    Record A1
    Record A2

    Table B
    Record B1
    Record B2

    There is a technical table that is making the link like this

    Table A-Table B
    Record A1 - Record B1
    Record A1 - Record B2
    Record A2 - Record B2

    Content of this multilinked table is today only visible via the expand feature.

    Thanks a lot for your help

    Monday, November 19, 2018 5:34 PM

All replies

  • Hi Boisnic,

    Please share the copy data activity code so that we can check the query and other parameters. Also, please share the error that you are getting.

    Tuesday, November 20, 2018 12:28 PM
  • Hello

    Please find below data activity code

    { "name": "ODataResource1", "properties": { "linkedServiceName": { "referenceName": "OData1", "type": "LinkedServiceReference" }, "type": "ODataResource", "structure": [ { "name": "UserName" } ], "typeProperties": { "path": "People?$expand=Trips" } }, "type": "Microsoft.DataFactory/factories/datasets" }

    In this example, there is no error but the issue is that no trips data is retrieved with the expand (Data is empty)

    Thanks for your help

    Thursday, November 22, 2018 12:53 PM
  • Hi Boisnic,

    I tried out an exactly similar data copy activity using the example from the tutorial in the link :


    I can confirm that $expand is not working as it would normally do when you use it in the REST API format. I do see data, but not trips data. 

    Its a limitation as of now. However there's a workaround for it. You can compose your queries and use an HTTP source (with the REST API) as the data source for your activities. Check this link out :

    Tuesday, November 27, 2018 10:49 AM
  • Thanks a lot 

    i am going to try this.

    Do you know when this behavior will be changed in the standard product ?

    Tuesday, November 27, 2018 2:30 PM
  • Hi Boisnic,

    I would suggest you to provide your suggestion or feedback on your experience with Azure Data Factory here:


    All of the feedback that you share on these forums is monitored and reviewed by the Azure Data Factory team. 
    Wednesday, November 28, 2018 11:30 AM