Review the following known issues and limitations before you begin working with plan.
Supported limits might vary depending on client resources, Fabric capacity, and Power BI XMLA query limits.
Plan doesn't support Microsoft Entra B2B IDs.
Plan items aren’t supported in workspaces or tenants that use private links.
You must have Admin or Build permissions on the semantic model.
Semantic models in Direct Lake mode require additional configuration.
Semantic model connections support only OAuth-based and service principal–based authentication.
Semantic models published in My workspace aren't supported.
Don't rename a semantic model that's connected to a Plan item. Renaming the semantic model breaks the connection, and the Plan item no longer works with the renamed semantic model.
Power BI Pro and Power BI Premium Per User (PPU) aren't supported for Plan scenarios that use XMLA endpoints and embed tokens. Similarly, lower-capacity SKUs that do not support XMLA endpoints are also unsupported.
PowerTable doesn't support user-specific database-level row-level security (RLS) when connecting to Fabric SQL tables through a database connection. As a result, users might see rows that differ from the expected RLS-filtered results. This limitation exists because PowerTable executes all database queries by using the identity associated with the database connection that the user configures during sheet creation, rather than the identity of the signed-in PowerTable user.
If you delete the DMTS connection that you configured for a PowerTable sheet, or if it becomes unavailable, you can't open the sheet to update the connection. The connection recovery screen doesn't appear, and you see the message "DMTS connection is deleted or not found."
To recover, create a new PowerTable sheet by using the Existing Table option and configure the same table again.
Users with the Contributor role can't create or share cloud connections.
Users with lower-level workspace roles, such as Contributor, can't create Plan artifacts that require embed token generation.
Automatic application database creation isn't supported when deploying plan items through CI/CD by using a service principal.
Don't rename a workspace that contains a Plan item. Renaming the workspace breaks the Plan item, and the item no longer opens.
Bulk data input supports a maximum of 1 million rows. Uploading more than 1 million rows from an Excel or CSV file isn't supported and might cause the upload to fail.
A Plan item supports up to 25 sheets. Keep the number of sheets within this limit to avoid problems when working with the item.
A Plan item supports up to 50 visuals. Keep the number of visuals within this limit to avoid problems when working with the item.
Each Infobridge query in a Planning sheet supports up to 1.2 million cells. Queries that exceed this limit might fail to load or process.
To work with larger datasets, split the data across multiple Planning sheets and append the queries. This approach supports a consolidated workbook of up to about 5 million cells (for example, across five Planning sheets).
Writeback supports up to 1.2 million cells per operation. Writeback operations that exceed this limit aren't supported and might fail.
Last updated
Was this helpful?
Was this helpful?
