Epicor Kinetic and Microsoft Power BI integration

What moves between them

ml-connector polls Epicor Kinetic on your defined schedule, typically daily or after each business transaction cycle, filtering for changed records since the last sync using OData date fields. The connector retrieves vendors, AP invoices, purchase orders, customers, parts, and GL accounts. Each record is transformed into the Power BI table schema and rows are posted into your Power BI push datasets. The main data flow is one-way from Epicor into Power BI; Power BI does not write data back to Epicor.

How ml-connector handles it

ml-connector stores your Epicor credentials encrypted and selects the authentication method based on your deployment: Basic Auth for on-premises, API Key for on-premises or cloud, or OAuth2 for cloud. It refreshes Epicor bearer tokens as they expire (~1 hour) and uses OData $filter syntax to retrieve only records changed since the last run, reducing API load. For Power BI, ml-connector obtains a service principal token using your client ID and secret, then POSTs rows to your push datasets in batches. It handles pagination on the Epicor side and validates that the service principal has workspace access on the Power BI side. Every record includes a full audit trail and can be replayed if a downstream Power BI call fails. Epicor does not publish rate limits, so ml-connector includes exponential backoff for unexpected delays.

A real-world example

A mid-sized distributor runs Epicor Kinetic for procurement and GL management across three warehouses. The finance team needs visibility into AP aging, vendor invoice trends, and cost allocation by warehouse for month-end close and vendor scorecards. Before the integration, they exported AP invoice reports from Epicor monthly and rebuilt them in Excel or Tableau, creating a lag and manual rework each cycle. With Epicor and Power BI connected, new invoices from Epicor flow into Power BI daily, dashboards update automatically, and the team can drill into aging, dispute patterns, and cost by vendor and warehouse in real time. Month-end close starts with current data already in Power BI, shortening the close timeline.

What you can do

• •Poll Epicor Kinetic on a schedule you define to retrieve vendors, AP invoices, purchase orders, GL accounts, and other business objects.
• •Push the records into your Microsoft Power BI push datasets, transforming Epicor OData schema into your Power BI table structure.
• •Refresh Epicor bearer tokens automatically as they expire and handle OData pagination transparently.
• •Authenticate to Epicor with Basic Auth, API Key, or OAuth2 depending on your cloud or on-premises deployment.
• •Maintain a full audit trail on every record sent to Power BI with error replay and retry logic on transient failures.

Questions

Which direction does data move between Epicor Kinetic and Microsoft Power BI?

Data flows one way: from Epicor Kinetic into Power BI. ml-connector polls Epicor for vendors, invoices, GL accounts, and other entities, transforms them to match your Power BI dataset schema, and pushes rows into your Power BI push datasets. Power BI is a read-only analytics destination and does not write back to Epicor.

Does the integration support both cloud and on-premises Epicor deployments?

Yes. ml-connector detects whether your Epicor instance is cloud (SaaS) or on-premises and uses the appropriate authentication method: API Key and OAuth2 for cloud, or Basic Auth and Token Resource Service for on-premises. The OData endpoint URL format differs between the two, and ml-connector handles both.

What happens if my Epicor bearer token or Power BI service principal token expires?

ml-connector refreshes Epicor bearer tokens automatically before they expire (~1 hour). For Power BI, it re-authenticates on each sync cycle by requesting a fresh OAuth2 token from Microsoft using your client credentials. If either authentication fails, the sync is retried with backoff and logged in the audit trail.