Forum Discussion

Th0mc's avatar
Th0mc
Frequent Visitor
1 year ago

Pending Changes and Collection was modified... error on a downloaded PBIX file form PBI Service

Hello all,

 

I'm getting an issue on one specific report.

Here is how I'm deploying it in PBI Service :

- The report (visual+semantic model) is developped on my computer pointing to dataflows from Workspace 1 and sharepoint folders

- All changes are applied on my computer with a parameter reducing the numer of rows of each table

- I publish it on Workspace 1

- I change the parameter to get all the rows into consideration and then refresh it. All ok.

- I use a deployment pipeline to deploy it on Workspace 2

 

When I download it from Workspace 2 and open it on my computer, I get the top banner saying there are pending changes to apply (not expected as it was all applied).

Then if I try to apply, I get the error message "Collection was modified; enumeration operation may not execute".

If I open PowerQuery editor, it is all empty

After a new modification, I tried again with all the process, deployed again but still getting the same issue.

 

Any help appreciated

Thomas

Need Help

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi,Th0mc .I am glad to help you.
    It looks like you re-downloaded the deployed pbix file and are having issues opening it.
    I hope the following issue helps.
    URL:

    Collection was modified; enumeration operation may... - Microsoft Fabric Community

    Check the deployment pipeline: Make sure that no steps have been missed in the deployment pipeline, especially when changing parameters and refreshing data. Ensure that all changes have been applied and saved correctly

    How to deploy a program

    URL:
    Solved: Unable to process semantic model in lakehouse - Microsoft Fabric Community



    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
    Best Regards,
    Carson Jian,
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Th0mc's avatar
      Th0mc
      Frequent Visitor
      1 year ago

      Hi Carson,

       

      Thanks for your reply but sorry to say these links don't help.

      What I could check in the deployment pipeline? I have no rule on deployment and no error. The Semantic Model and report are working and refreshing fine in Service.

      I have exactly the same report for previous year and it is working fine including on the downloaded pbix file.

      the only difference is :

      - for the 2024 report I previously was not using deployment pipeline. Instead I was refreshing in Workspace 1, checking results, donwloading it and then uploading in the workspace2. Later I started using deployment pipeline.

      - for 2025 it was initially created in workspace2 through deployment pipeline. Then I understood that this way, it was not possible to download it later from workspace2. So I replaced it by a first upload and later moving my changes through deployment pipeline. So now I'm able to donwload it but seems corrupted somehow 😞

       

      Thomas

      • Anonymous's avatar
        Anonymous
        Not applicable
        1 year ago

        Hi,Th0mc .Thank you for your reply.
        I tried deploying the report and had a similar problem to yours, the report in the service was corrupted
        This is my test:

        Select the pbix report and corresponding semantic model that will be deployed later and need to be downloaded to another workspace.


        When I try to open the report from worksapce2, it gives an error:

        After the report was deployed, the gateway connection (data source credentials) needed to be reconfigured, which also didn't solve the problem
        And the original pre-deployment report was normal:

        There is a problem with the reports in the new workspace after deployment: there is a problem with the reports in the service (my gateway connection and data source credentials are configured correctly). I think this could be the reason why you have corrupted reports after downloading and deploying (deployment causes corrupted reports).

        You can create a support ticket for  free and a dedicated Microsoft engineer will come to solve the problem  for you.
        It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.
         

        The Link of Power BI Support:

        Microsoft Fabric Support and Status | Microsoft Fabric


         

         


        I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
        Best Regards,
        Carson Jian