Omar Hassan

Test your semantic model queries from the Fabric Plan connection before you build Planning sheets. Send a simple SUMMARIZECOLUMNS() against your planning dimensions and verify the output matches your expectations.

Also worth checking whether your semantic models and writeback destinations are in the same region. Cross-region data movement can become a compliance issue even if the compute stays local.

Attachment columns in PowerTable are something I've wanted for months. We use approval workflows for capital expenditure requests and attachments to the approval row were a blocker for us to retire our SharePoint workaround.

Alternatively for date-based triggers: set up a Fabric pipeline that runs daily, queries the PowerTable's underlying SQL table for rows where DueDate = today+7, and sends a Teams notification via the webhook action.

One limitation: the app definition (structure, configuration) is version-controlled, but the actual plan data (writeback values) is NOT in Git — that's in the SQL database. Git covers the 'how the app is built', not 'what planners entered'.