Duaer

Guides

Dynamics NAV purchase to pay and order to cash: see where each order waits

Connect Dynamics NAV to Duaer. A read-only database user reads the steps of each purchase or sales order of one company.

What does Duaer read from Dynamics NAV?

Each purchase or sales order is a case, with the supplier or customer, the company, currency and amount. The steps are:

  • Purchase to pay: Order created (Purchase Header, or the posted invoice once NAV deleted the fully invoiced order), Goods received (Purch. Rcpt. Header), Invoice posted (Purch. Inv. Header), Paid (the closing date in Vendor Ledger Entry).
  • Order to cash: Order created (Sales Header), Goods issued (Sales Shipment Header), Invoice created (Sales Invoice Header), Paid (the closing date in Cust. Ledger Entry).
  • One source reads one company.

How do you connect Dynamics NAV to Duaer?

  1. In Dynamics NAV's SQL Server database, create a read-only user with SELECT on the tables above.
  2. If the database is only inside your network, start the Duaer on-premises data gateway (0.2.0 or later) there with tcp://database-host:port in ALLOWED_TARGETS; the credential's host and port must match it.
  3. In Duaer, create a Microsoft SQL credential for this user.
  4. As an owner or admin, open Data sources, select Add source, choose Dynamics NAV under Purchase to pay or Order to cash, choose the credential, enter the company name (such as CRONUS International Ltd.), select Check connection and confirm.

How often does it read, and how much?

Each run reads the streams by posting date. NAV documents carry dates only, so each read starts two weeks back to catch documents posted with a past date; a step is never written twice. Queries only.

What are the limits?

  • The tables, entities and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
  • Nothing is read until the company name is given.

Questions

Is this for Business Central too?

No. Business Central has its own source, which reads its API.

In this section

Process

Add a process source in Duaer

A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.

Process

See the process in your data and generate workflows in Duaer

Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.

Process

Process findings and SOP conformance in Duaer

Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.

Follow-through

Dynamics AX 2012 purchase to pay and order to cash: see where each order waits

Connect Dynamics AX 2012 to Duaer. A read-only database user reads the steps of each purchase or sales order.