1. Push Dataset → No Relationships
Yes, that’s correct. A Push Dataset in Power BI (via REST API or Power BI API) works as a stand‑alone dataset and does not support relationships with other tables in your existing model. Because of this, it’s not suitable when you need relational modeling or DirectQuery scenarios.
2. Writing to SQL Using Premium Connector → Relationships Work
If you write data from Power Apps/Power Automate into SQL Server using the Premium connector, then load that SQL table into Power BI:
You can create relationships
You can use Import, DirectQuery, or Composite mode
Fully supports advanced modeling, DAX, visuals, etc.
This is the recommended architecture for enterprise scenarios.
3. DirectQuery for Real‑Time Updates
For real‑time or near real‑time:
Dataverse (Best Option)
Native integration with Power Apps
Power BI supports DirectQuery
No separate SQL licensing (depends on tenant)
SQL Server
Fully supports DirectQuery
Power Apps can write using Premium connector
Great for relational models
4. Notifications + Highlighting Rows in Power BI
Power BI cannot send row‑level notifications by itself.
However, you can achieve the full requirement using SQL/Dataverse + Power Apps + Power Automate:
Power Apps writes comments to SQL/Dataverse
It also updates a field like IsNewComment = true (or updates a timestamp)
Power Automate triggers → sends email/Teams notification to the user
Power BI (DirectQuery or fast refresh) uses conditional formatting to highlight any rows where IsNewComment = true
Flow Summary
Power Apps → writes “new comment” flag
Power Automate → notifies the concerned user
Power BI → highlights the flagged row in the matrix
This gives both real‑time visibility and user notifications.
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.