locked
Copy data - 'Import schemas' fails when dataset is parameterised RRS feed

  • Question

  • I have created a single AzureSQLDatabase linked service and a single AzureSQLDataset to go with it.

    Each of these is parameterised - DatabaseName for the linked service and (SchemaName, TableName, DatabaseName) for the dataset.

    Doing this means a vast reduction in the number of datasets I need to maintain - which is great.

    However, when setting up a 'Copy data' activity and getting to the 'Mapping' section, the 'Import schemas' function gives the following error:

    • Failed to import sink schema. Please select a table for your dataset

    This error appears despite the SchemaName, TableName and DatabaseName parameters having valid values.

    Is this behaviour intentional? Ot should Import schemas work for parameterised datasets?

    If so, it makes pipeline development using parameterised datasets a lot more time consuming than it could be otherwise.


    • Edited by WookieePhil Friday, October 11, 2019 5:23 PM Spacing improvement
    Friday, October 11, 2019 5:21 PM

Answers

  • Hi WookieePhil,

    Thanks for your query. Yes this is an intentional behaviour and the error is valid when a dataset/linked service is parameterized. When the parameterization is implemented the actual values for the parameters are provided during the runtime execution, because of which the 'Import Schema' returns error when we try to do a manual 'Import schema'. It is recommended to use the actual dataset/linkedservice values while creating and test the connection or do a preview data and then replace the values with parameterization. 

    Please feel free to share your idea/feedback in Azure Data Factory feedback forum. All the feedback shared in this forum is monitored and reviewed by ADF engineering team and will take necessary action. Providing a feedback also help other users with similar idea to up-vote your suggestion which might increase the priority of the feature implementation.

    ADF feedback forum: https://feedback.azure.com/forums/270578-azure-data-factory

     Hope this helps. Let us know if you have any further query.


    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered"Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.


    Friday, October 11, 2019 10:26 PM

All replies

  • Hi WookieePhil,

    Thanks for your query. Yes this is an intentional behaviour and the error is valid when a dataset/linked service is parameterized. When the parameterization is implemented the actual values for the parameters are provided during the runtime execution, because of which the 'Import Schema' returns error when we try to do a manual 'Import schema'. It is recommended to use the actual dataset/linkedservice values while creating and test the connection or do a preview data and then replace the values with parameterization. 

    Please feel free to share your idea/feedback in Azure Data Factory feedback forum. All the feedback shared in this forum is monitored and reviewed by ADF engineering team and will take necessary action. Providing a feedback also help other users with similar idea to up-vote your suggestion which might increase the priority of the feature implementation.

    ADF feedback forum: https://feedback.azure.com/forums/270578-azure-data-factory

     Hope this helps. Let us know if you have any further query.


    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered"Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.


    Friday, October 11, 2019 10:26 PM
  • Hi WookieePhil,

    Just checking to see if the above reply was helpful. If this answers your query, please consider to click “Mark as Answer” and "Up-Vote" as it might be beneficial to other community members reading this thread. And, if you have any further query do let us know.


    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered "Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.

    Monday, October 14, 2019 9:01 PM
  • Thanks for the response. I've marked it as the answer, as it at least confirms my suspicions.

    But it does make development considerably more tiresome and inelegant, because of the need to temporarily create objects purely for design-time development.

    I'll submit a feedback item, as you suggest.

    Monday, October 14, 2019 9:24 PM
  • Thanks for the feedback, it really helps. Could please share the feedback link here so that it will give an opportunity to other members of the community with similar idea to up-vote your suggestion.


    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered"Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.


    Monday, October 14, 2019 9:44 PM
  • Thank you for sharing it. :)

    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered "Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.

    Monday, October 14, 2019 10:11 PM