Order lines from D365 become JIRA tickets, and the ticket status finds its own way back.
Lasernet carries orders into JIRA and ticket states back into D365, down to the order line.
Industry: Industrial company, D365 FO
The problem
The order confirmation went from D365 FO to the customer. Everything that happened internally after that lived in JIRA tickets. Neither system knew about the other, so somebody updated the status by hand. Nobody in the company wanted to buy a second middleware product just for this sync.
The solution
The order confirmation gets split: one document for the customer, the XML metadata goes into a SQL database as JSON.
An hourly scheduler pushes everything open to JIRA via REST. The response comes back as metadata.
A second scheduler writes the ticket states back into D365, down to the order line. Authentication runs through MS Graph against D365.
The final Solved flag pulls delivery note and invoice straight out of D365.
The reverse direction runs through a Lasernet REST input port.
What it delivered
Nobody types a ticket status twice. The licence bill looks the same as before.