Forum Discussion

ahmedshalabyy12's avatar
ahmedshalabyy12
Helper V
7 months ago
Solved

Paginated reports error - getting data from semantic model

Hello , I receive this error while I try to create a paginated report and fetch the data from a certain workspace (A), however it works fine with another workspace (B), therefore what's the reason...
Need Help
  • ahmedshalabyy12's avatar
    ahmedshalabyy12
    7 months ago

    Hello AshokKunwar ,

    Thank you for your efforts problem is solved what I did I connected from another VM
    cuz checking if the vpn in my pc blocking the connection and it worked .

    I don't know how the vpn blocking the connection despite I can connect to another workspace .

ahmedshalabyy12's avatar
ahmedshalabyy12
Helper V
7 months ago

I am an admin in the workspace but how to check this solution

  • ​Workspace Type: Ensure Workspace A is a V2 (New) workspace. Legacy V1 workspaces can cause retrieval errors.
AshokKunwar's avatar
AshokKunwar
Continued Contributor
7 months ago

ahmedshalabyy12 

If you are an Admin, you can tell by looking at the Workspace Settings:

  • ​Open Workspace A in the Power BI Service.
  • ​Click on Settings (the gear icon near the top right) or the three dots (...) next to the workspace name.
  • ​Look for a "Contact list" or "Workspace ID" in the General tab.
  • ​The Key Indicator: If you see the "Manage access" pane where you can assign roles like Contributor, Member, or Viewer, you are on a V2 (New) workspace. Legacy V1 workspaces relied on Office 365 Groups for permissions and lacked these specific Power BI roles.

​2. Check the Licensing (Capacity Settings)

​Paginated Reports require specific capacity settings to work correctly across different workspaces. Even if you are an Admin, if the workspace is not backed by the right capacity, Report Builder might throw a "Null" error when trying to fetch the list of datasets.

  • ​In Workspace Settings, go to the Premium tab.
  • ​Ensure the workspace is assigned to Premium Capacity, Premium Per User (PPU), or Fabric Capacity.
  • ​If Workspace B is on a Premium capacity but Workspace A is on "Shared" (Pro), this is likely why Report Builder works for one and not the other.

​3. Check for Service "Orphans"

​Since the error in Report Builder was IsMyWorkspace failing, it could be that the "Owner" of the workspace or the specific semantic model has been deleted from your Entra ID (Active Directory).

  • ​Go to the Semantic Model settings in Workspace A.
  • ​Check the Gateway connection and Data source credentials.
  • ​If the "Owner" listed is no longer with the company, you must click Take Over to become the owner of the model. This often resolves "Object reference not set" errors because it "re-links" the object to a valid user.

If checking the workspace owner or re-signing in fixes the connection for Workspace A, please mark this as the "Accepted Solution"!