Forum Discussion

mark_carlisle's avatar
mark_carlisle
Icon for Advocate IV rankAdvocate IV
6 years ago

Deployment Pipelines Unsupported Items Error but why?

I've tried to use the new Deployment Pipelines feature today. I've assigned our existing Customer Services workspace to the pipeline and set it to Production deployment stage, however, I get the following error;

 

 

This workspace does not contain dataflows. I also get the following error when attempting to deploy to a previous stage.

 

Can't start the deployment
There's a problem deploying the content. Please try again later. If the problem continues to occur, contact Power BI support.
Please check the technical details for more information. If you contact support, please provide these details.
Activity ID: 6e79afe6-2b9d-4dd2-b9f5-9f8428c68819
Request ID: e2381822-4304-54c0-25c6-5f249cf9165c
Correlation ID: 19fa3fd0-b503-9ca5-54c0-7197ec50c8ca
Time: Fri May 22 2020 05:08:50 GMT+0100 (British Summer Time)
Service version: 13.0.13322.215
Client version: 2005.2.01092-train
Cluster URI: https://wabi-us-east2-redirect.analysis.windows.net/

 

 

Most of the reports in this workspace use a shared dataset that resides in another workspace called Core Datasets, that workspace does have dataflows.

 

Three of the reports in the Customer Services workspace have their datasets in the Customer Services workspace and those datasets have dataflows as some of their datasources.

 

I understand that dataflows are an unsupported item, but I took that to mean that the dataflows themselves were unsupported, not datasets using dataflows.

 

Nimrod_Shalit can you explain the issue I'm facing here? As the documentation is written I seem to be using a supported configuration.

7 Replies

  • Managed to do I little more testing with this.

     

    I no longer get the error about unsupported items. I do however still get the second error;

     

    Can't start the deployment
    There's a problem deploying the content. Please try again later. If the problem continues to occur, contact Power BI support.
    Please check the technical details for more information. If you contact support, please provide these details.
    Activity ID: 824e786f-1652-4114-b312-b4b013c63717
    Request ID: 0816fcdf-26aa-8756-e370-b4829ae591fe
    Correlation ID: 138d81f5-72a9-126f-76c5-4a642c4500e0
    Time: Fri May 22 2020 16:00:43 GMT+0100 (British Summer Time)
    Service version: 13.0.13322.215
    Client version: 2005.2.01092-train
    Cluster URI: https://wabi-us-east2-redirect.analysis.windows.net/

     

    With a potential answer here. If this does work in a few days then I'll mark this as an answer.

    • mark_carlisle's avatar
      mark_carlisle
      Icon for Advocate IV rankAdvocate IV

      I've finally resolved this error and determined that all datasets in the workspace must have the preview feature 

      Store datasets using enhanced metadata format enabled, which does make sense.

       

      This requirement is missing in the documentation though.

      • Nimrod_Shalit's avatar
        Nimrod_Shalit
        Icon for Power BI Team rankPower BI Team

        This is not accurate, please don't check it as a solution. 

        we have solved some bugs that came up in the first days, and working on few additional bugs that customers are facing now, which should just solve most of the errors you have experienced.

        However, we are not dependent on checking the 'enhanced metadata' preview for datsets.

        It is supported, but not a must.