Power BI/We build and run it for you.
Your ERP data in Power BI, without the refresh button.
We take the records and saved searches you actually report on, land them in storage you own, and model them so Power BI can read them. Pipelines run on a schedule you set, with the run history sitting next to them.
The reason to do it this way is that the person who built the dashboard doesn't need an ERP licence to keep it working, and nobody is exporting anything on a Monday morning.
Data can land in your own AWS account. There's a CloudFormation template for setting it up.
Power BI Sync Overview
Sync Status
Data synchronization is active
Recent Pipeline Activity
Sales orders
Sales Order Search → sales_orders.parquet
Inventory balances
Item Inventory Balance → inventory_balances.parquet
Customer invoices
Invoice Search → invoices.parquet
The Overview tab, as it looks once pipelines are running.
What's in it
Sources and sinks
A source is a record type or saved search in your ERP. A sink is where it lands. A pipeline joins the two and runs on a schedule. The app counts them separately because they fail separately, and knowing which of the three broke is most of the diagnosis.
Your storage
Data can land in an AWS account you own, set up from a CloudFormation template so you can read it before you agree to it. Your data stays somewhere you control.
Access requests
People ask for a dataset, someone who's allowed to approves it, and the app keeps the pending and approved counts. Duller than it sounds, and it's the reason finance stops emailing spreadsheets around.
Monitoring and control
Pipeline health, error rates and execution history, with manual runs and a full sync for when someone has backdated three months of transactions. We watch the failures whether or not you do.
Pricing
Scoped to the reports you rely on.
The number depends on how many pipelines your Monday spreadsheet turns into.
Power BI
Scoped to you
Quoted in writing before any work starts.
- We build and run the pipelines
- Data lands in storage you own
- Your BI person takes it from there
No standard price list, because no two businesses look alike. You get one clear number, and you can walk away from it.
How a build goes
- 01
Show us the report someone runs manually. Not the wishlist. The spreadsheet that gets rebuilt every Monday, because that tells us which records matter.
- 02
We build the pipelines for those. Usually three or four. It runs alongside the manual report until the numbers agree.
- 03
Your BI person takes it from there. They've got modelled tables and don't have to learn your ERP's schema. We keep the plumbing working.
docs.datashift.com.au
Read what we run before you agree to it.
The integration documentation is public, including how data lands in your storage, so your IT team can review it without a call.
Bring us the Monday spreadsheet.
Twenty minutes on what's in it and where it comes from, and we can tell you how many pipelines that is and roughly what it costs to run.
The rest of the range
Labels
Carton and product labels off the sales order. Free to 250 a month.
Freight
Live rates from every carrier account you hold, then book and print.
EDI
Partner purchase orders arriving as records in your ERP, and going back out.
3CX
The customer's record and their open orders while the phone is ringing.
Direct Print
Push print jobs directly to your registered DataShift print devices.