ERP integration

The project starts in Dynamics 365. It is planned in Linetrack.

If you work in Business Central or Supply Chain Management, Power Automate is usually already part of your Microsoft 365 tenant. A flow reacts to a new project in the ERP and creates it in Linetrack from your template, with project number, customer and project manager. Planned hours per task and resource and the KPIs per project flow back.

Via the REST APIBusiness Central & SCMPower Automate in betweenSign-in with Microsoft

Microsoft Dynamics 365 website ↗

In short

Microsoft Dynamics 365 is connected through the Linetrack REST API, usually with a Power Automate flow in the same Microsoft 365 tenant. The flow turns new projects from Business Central or orders from Supply Chain Management into Linetrack projects built from a template, and sends customers and vendors with their numbers as project partners. Planned hours per task and resource and KPIs per project go back to Dynamics 365. There is no dedicated Dynamics connector for this; the flow calls the API with an API key.

What the flow transfers

Two Dynamics worlds, one interface in Linetrack

Business Central and Supply Chain Management name many things differently, but in Linetrack they land in the same places. The cards show what a flow typically writes and what it brings back. Which tables and fields your flow reads is agreed with your Dynamics partner.

Business Central

The project card becomes a Linetrack project

When someone creates a new project in Business Central, the flow starts from the trigger of the Business Central connector in Power Automate. Linetrack builds a project from the matching template and calculates the dates from the start date on the project calendar. The Business Central project number stays on the project as its external ID.

  • Project number
  • Description
  • Customer
  • Project manager
  • Portfolio
  • Template
  • Start date
  • External ID

Where in Linetrack: project overview and the project's Gantt chart

Supply Chain

Plant orders with a ready-made structure

If a plant order in Supply Chain Management already has a breakdown, the flow sends it as a complete plan: up to 2000 tasks on up to 20 levels, with milestones and dependencies. Production orders and material stay in Dynamics 365, and Linetrack plans the teams' hours.

  • Tasks
  • Milestones
  • Dependencies
  • Lag
  • Order number
  • Line number
Master data

Customers and vendors as project partners

Customers and vendors come from Dynamics 365 with their numbers and contacts. On the project, the project manager then sees who signs off the acceptance at the customer and which supplier builds the control cabinet.

  • Customer number
  • Vendor number
  • Contacts
  • Project assignment

Where in Linetrack: project partners

Resources

Planned hours on the right person

Hours from project planning lines or routing land in Linetrack on the task, with the resource. The flow maps the resource number from Dynamics 365 to the personnel number or short code in Linetrack.

  • Task
  • Resource
  • Hours
  • Personnel number
  • Short code

Where in Linetrack: resource view

Return path

KPIs for Dynamics and Power BI

Per project, Linetrack delivers completion, status light, open and overdue tasks and schedule adherence, together with order and line number. A scheduled flow writes the values back to Dynamics 365, and Power BI can fetch the same KPIs directly when needed.

  • Completion
  • Status light
  • Schedule adherence
  • Time progress
  • Phase
  • Overdue tasks
Microsoft account

Sign-in with the same account

Your project managers sign in to Linetrack with “Continue with Microsoft”, using the same Entra ID account as in Dynamics 365. Linetrack only asks for profile and email address and has no access to mailboxes or files.

  • Microsoft Entra ID
  • Web
  • Mobile
  • Profile
  • Email

Day to day

What changes for sales, project management and controlling

Order on Friday, project on Monday

Sales enters the order for an assembly line in Business Central on Friday afternoon. On Monday the project manager finds the project in Linetrack, built from the assembly line template, with delivery date and customer. All that is left is to adjust the phases that run differently for this customer.

Room in controls engineering

Before a large quotation, management wants to know whether controls engineering still has capacity in the second quarter. The figures per resource group and month from Linetrack sit in the Power BI report next to the order data from Dynamics 365. Net capacity and planned hours show the gap before anyone commits to a delivery date.

Month-end close with the current plan

At month end, controlling compares budget and project status in Dynamics 365. The hours report from Linetrack supplies planned, actual and remaining hours per order, and the KPIs show whether commissioning is still on plan. Nobody copies Gantt screenshots into a spreadsheet any more.

Setup

From API key to a running flow

  1. 1

    A key with the right scopes

    An administrator creates an API key for Dynamics 365 in Linetrack, for example with projects:write for projects and kpis:read for the return path. Every call made with this key is logged.

  2. 2

    Map the fields

    Together with your Dynamics partner we decide which project or order type gets which Linetrack template and which fields come along as custom fields, such as cost centre or budget.

  3. 3

    Build the flow

    In Power Automate a flow reacts to new or changed records in Dynamics 365 and calls the Linetrack API with the HTTP action, with the key in the X-API-KEY header. A second flow runs on a schedule for the KPIs.

  4. 4

    Test with a real project

    We run one real order through together and check structure, dates and partners in Linetrack. After that the flow takes over all new projects.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is there a ready-made Dynamics 365 connector for Linetrack?

No. The connection runs through the Linetrack REST API. Power Automate brings its connectors for Dynamics 365, and for the Linetrack side the flow uses the HTTP action. Alternatively, your Dynamics partner calls the API from an extension of their own or through Make or n8n.

Does it work the same way with Business Central and Supply Chain Management?

On the Linetrack side, yes: the API is the same. What differs is where the flow reads the data. In Business Central it is usually projects with project tasks and planning lines, in Finance and Supply Chain Management more often projects and sales orders. We are happy to check with you and your Dynamics partner which tables are the right ones.

Do our project managers need another password?

Not if you use sign-in with Microsoft. On the first login Linetrack matches the account by email address, after that by the stable Entra ID identity. Personal Microsoft accounts such as outlook.com are switched off by default.

Can absences come from Dynamics 365 as well?

Yes, if you keep absences there. The flow sends them to Linetrack with a type such as holiday, sickness or on-site assembly, or, if you prefer, with the period only and no reason. If they live in a time-tracking or HR system, it is better to connect that one.

The platforms and brands mentioned belong to their respective owners. Mentioning them describes the technical connection and does not imply a partnership or certification.