Exporting a paginated report requires permissions in both report and dataset workspaces

[nbudel]

Hi,

I can't create a Export for Paginated Report anymore.    It was working fine a few days ago.

{

  "error": {

    "code": "ItemNotFound",

    "message": "Exporting a paginated report requires permissions in both report and dataset workspaces"

  }

}

[asocorrocognex]

Same for me.  It started failing today after having run successfully for months.

[SSalaM]

Nice to hear that it's not only my problem :-)... I hope MS hasn't changed something.

[vdury]

Same problem for me.

My flow has been working for months, and it is now reporting this same error since mid-day March 6th (US Central)

{

  "error": {

    "code": "ItemNotFound",

    "message": "Exporting a paginated report requires permissions in both report and dataset workspaces"

  }

}

The paginated report works ok when run from PowerBI workspace, but raises this error when calling it from Flow/PowerAutomate.

What's weird is that I have other Flows with similar structure running OK.

[ntcomcaly]

I've also had the same issue. I have a flow that has been running perfectly fine for 5 months with no issue, and suddenly started failing March 6 with this error:

{
  "error": {
    "code": "ItemNotFound",
    "message": "Exporting a paginated report requires permissions in both report and dataset workspaces"
  }
}

[Sheilag04]

I have the same thing occur to me, but what is weird is that it works with one microsoft account but on another account I shared the flow with it throws this error. 

[nbudel]

Thanks for your feedback.   Today i had a teams meeting with somebody from MS automate.  The problem looks like it is comming from the BI side and not automate.   The have made a video of the error and environment. Hopefully tomorrow i will have contact with MS BI side that can help us 🙂

Keep you all posted!

[AmosHersch]

Hi,

I assume you're trying to export a paginated report which has a Power BI dataset as a datasource right?

If so, does the user calling the export have access to the report's workspace and to the dataset's workspace?

[SSalaM]

I assume you're trying to export a paginated report which has a Power BI dataset as a datasource right?

In my case yes, it's correct;

If so, does the user calling the export have access to the report's workspace and to the dataset's workspace?

Yes, the user is the same and have Admin right on report, Dataset and workspace.

Thanks

[asocorrocognex]

I think it's the same situation for all who have posted here: the flow was working fine and then stopped working for no apparent reason.

[AmosHersch]

Few additional questions:

1. Are the paginate report and dataset located in the same workspace?

2. Are you using "New experience workspace" (AKA workspace V2) or "classic" workspace? 

3. Anything else special about the setup?

Thanks

[SSalaM]

1. Are the paginate report and dataset located in the same workspace?

No, different workspace

2. Are you using "New experience workspace" (AKA workspace V2) or "classic" workspace? 

Paginated report is in a Premium Workspace, dataset is in a normal workspace

3. Anything else special about the setup?

Nothing special; only read dataset, populate report and export. The paginated report have 2 input parameters.

[ntcomcaly]

For me:

1. Are the paginate report and dataset located in the same workspace?

Yes, they're in the same Premium Per User Workspace.

2. Are you using "New experience workspace" (AKA workspace V2) or "classic" workspace? 

I think the classic workspace, but I can't tell.

3. Anything else special about the setup?

Nothing special for me. Just regular paginated reports with no parameters.

[vdury]

Yes, exporting a paginated report which has a Power BI dataset as a datasource and the export works ok for the user if called directly from outside PowerAutomate.

1. Are the paginate report and dataset located in the same workspace?

Yes

2. Are you using "New experience workspace" (AKA workspace V2) or "classic" workspace? 

Not sure what is "New experience", so would assume "classic"

3. Anything else special about the setup?

Nope. Was working ok for months, and suddenly stopped on March 6 with no change

[nbudel]

Hi all,

I just talked to somebody from MS- BI,  around the 15th there will be a update.  They are now looking for a workaround and also if the issue will beresolved with the update of the 15th.

When i get a status update i will keep you all informed. 

[SSalaM]

Today, same error.

[markrobinson]

I am having the same issue for past 2 weeks.

This was working fine for months previously.

What is ETA for resolution?

[nbudel]

I was waiting for the new Train release togetter with the support team of MS.  The release was succeeded today (North/West Europe) but it did not resolve this issue.  😞   
Tomorrow morning i have again a teams meeting for this issue.   I also would like to have this issue resolved!  

[nbudel]

Hopefully there will be a workaround... or it will take 2 of 3 weeks.

[Sheilag04]

thank you for this information ! Please let us know if they tell you anything.