Bring our quality data into an operational report.
Neil
- Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
- Reads
Selected Seal records
- Returns
- Defined measures and the records behind them
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Make selected Seal records available to Microsoft Power BI for quality and operational reporting through a connection set up with Seal’s API. Define each measure and the records behind it, and agree the refresh schedule and access.
Connection setup and permissions
Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.
2Refresh or push Seal records into Power BI.
Route
A scheduled refresh pulls data at the frequency and time slots you set; some sources need a gateway and others do not.¹ The Power Query Web connector fetches a URL and parses the response by type, such as JSON, but its Web API authentication type does not work in the Power BI service.² A push semantic model receives rows through the REST API, up to 10,000 rows a request. Microsoft is retiring the creation of new push and streaming semantic models after 31 October 2027; existing ones keep working.³⁴
Record identity
The push API’s delete operation removes every row from a table, so keep the Seal record identifier in each row to check a reloaded table against the records in scope.⁵ A push table holds up to 5,000,000 rows without a retention policy, or 200,000 in a first-in, first-out model.³
Refresh
Power BI Pro allows up to 8 scheduled refreshes a day; Premium Per User and Premium or Fabric capacity allow 48.¹ A refresh aims to start within 15 minutes of its slot and can start up to an hour late. A refresh can also be started through the REST API.¹⁶
When it fails
- The schedule has turned itself off
- Power BI deactivates a refresh schedule after four consecutive failures, or after an error that needs a configuration change, such as expired credentials.¹ Refresh history shows whether each past refresh succeeded, and the REST API returns the same history.⁷⁸ Read the refresh history, renew the credentials and turn the schedule back on. The report shows the old figures until then.
- Nobody heard about a failure
- Failure emails go to the semantic model owner by default, but on-demand and programmatic refreshes send none.⁷ Where a refresh is started through the API, read the refresh history after each call instead of waiting for an email.
- A quiet report stopped refreshing
- Scheduled refresh pauses after two months without views of the semantic model’s reports or dashboards.¹ Refresh a report that has not been opened for a while before using it in a review.
Check one record
Pick one month’s deviation count in Seal and the Power BI visual that shows it. Refresh, then compare the count and the record identifiers behind it. A difference means a filter, a failed refresh or a record outside the agreed scope.
3Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
4Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.
References
- 1Microsoft: configure scheduled refresh.
- 2Microsoft: Power Query Web connector.
- 3Microsoft: push semantic model limitations.
- 4Microsoft: real-time streaming in Power BI.
- 5Power BI REST API: Delete Rows In Group.
- 6Power BI REST API: Refresh Dataset In Group.
- 7Microsoft: data refresh in Power BI.
- 8Power BI REST API: Get Refresh History In Group.
