- 2 minutes to read

Can I export BPM data for reporting?

Quick Answer

Yes. A BPM doesn't store data of its own: it draws the Log Events that a Log View finds. So you export BPM data the same way you export any Log View result:

For Power BI, connect to the same Web API URL; the former Power BI template and content pack are obsolete, see Reports and Power BI. Your Role decides what you see in the export, just as on screen.

Where the Data Comes From

flowchart LR LE[fa:fa-bolt Log Events
Portal, ERP, WMS] --> LV[fa:fa-hard-drive Log View
group by interchange id] LV --> BPM[fa:fa-project-diagram BPM
Order-to-Cash] LV --> CSV[fa:fa-file-csv Export to CSV] LV --> API[fa:fa-code Web API JSON
Copy API URL] API --> BI[fa:fa-chart-column Excel, Power BI,
custom code] style LV fill:#2678BD style BPM fill:#93d16d style CSV fill:#E47528 style API fill:#E47528

The BPM and the exports (orange) read the same Log View (blue).

Example: Order-to-Cash

In the Order-to-Cash demo, the Order 2 Cash Log View groups events by Application interchange id, and the Order Number Search Field holds the business key.

  1. Open the Log View and set the time interval, for example last month.
  2. Search on Log Status Code -1337, if the Log View offers it as a search field, to list the orders that stopped at a step.
  3. Click Export to CSV for a one-off list, or Copy API URL to build a Power BI report over the same search.

Business values such as Order Number come from Search Fields; add one later and re-index to cover older events.

Things to Know

  • No BPM-specific export: export from the Log View associated with the BPM.
  • Retention: you can only export what the Log Databases still hold; load long-term data into your own store.
  • Aggregates: Nodinite returns events; calculate counts and durations in your report tool.
  • Payloads: follow View Body and View Context; see Permission Set for Log Views.

Next Steps