Power BI Report Resolution for Databricks
Budget: ₹100 – ₹400 INR
Earlier:
Dataverse only → Power BI semantic model → Paginated report
This worked because all required columns were coming from one supported model/source.
Now:
Dataverse + Azure Databricks columns → same Power BI semantic model → Paginated report
Paginated report is failing/blank because the semantic model now has a mixed source model, and the Databricks master columns may not be resolving properly through the semantic model when paginated report queries it.
Most likely causes:
The Databricks columns are not imported/refreshed properly in the semantic model
Power BI visual may show them due to local/desktop cache or DirectQuery behavior.
Paginated report reads the published semantic model, not your desktop file.
Relationship issue between Dataverse table and Databricks master table
If relationship is inactive, many-to-many, wrong key, or filter direction issue, paginated report DAX may return blank.
Paginated report query is still based on old Dataverse-only fields
After adding Databricks columns, the dataset query in Report Builder may need to be refreshed/rebuilt.
Composite model / DirectQuery issue
If Dataverse is Import and Databricks is DirectQuery, paginated report may behave differently while querying the semantic model.
Credentials/gateway issue for Databricks in Power BI Service
Dataset may publish, but service-side refresh/query may fail for Databricks credentials.
Dataverse only → Power BI semantic model → Paginated report
This worked because all required columns were coming from one supported model/source.
Now:
Dataverse + Azure Databricks columns → same Power BI semantic model → Paginated report
Paginated report is failing/blank because the semantic model now has a mixed source model, and the Databricks master columns may not be resolving properly through the semantic model when paginated report queries it.
Most likely causes:
The Databricks columns are not imported/refreshed properly in the semantic model
Power BI visual may show them due to local/desktop cache or DirectQuery behavior.
Paginated report reads the published semantic model, not your desktop file.
Relationship issue between Dataverse table and Databricks master table
If relationship is inactive, many-to-many, wrong key, or filter direction issue, paginated report DAX may return blank.
Paginated report query is still based on old Dataverse-only fields
After adding Databricks columns, the dataset query in Report Builder may need to be refreshed/rebuilt.
Composite model / DirectQuery issue
If Dataverse is Import and Databricks is DirectQuery, paginated report may behave differently while querying the semantic model.
Credentials/gateway issue for Databricks in Power BI Service
Dataset may publish, but service-side refresh/query may fail for Databricks credentials.