DataShift Logo

We build and run it for you.

NetSuite 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 a NetSuite 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.

app.datashift.com.au/acme/services/powerbisync

PowerBI Sync Overview

2
Active Connections
3
Data Sources
3
Data Sinks
3
Enhanced Pipelines

Sync Status

Data synchronization is active

Active

Recent Pipeline Activity

Sales orders

Sales Order Searchsales_orders.parquet

Active

Inventory balances

Item Inventory Balanceinventory_balances.parquet

Active

Customer invoices

Invoice Searchinvoices.parquet

Active

Rebuilt from powerbisync/page.tsx and OverviewTab.tsx, including the five-tab structure the app calls frozen.

What's in it

Sources and sinks
A source is a NetSuite record type or saved search. 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.

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 NetSuite's schema. We keep the plumbing working.

What we don't do here

We don't build your dashboards. We've done it, and we're not the best people for it. That's someone who knows your business rather than your API.

We don't do real-time. This runs on a schedule, and if you need a stream you need something else.

If Power BI isn't your tool, say so early. The pipeline half works for anything that reads from storage, but Power BI is the only last mile we've proven.

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.