Microsoft Dynamics NAV 2018
How Dynamics NAV 2018 can supply serial numbers until an upgrade, and why new integrations target Business Central.
This page describes an integration pattern. BatteryPass ships no connector for Dynamics NAV and has no partnership with Microsoft; nothing here is a vendor approval.
According to Microsoft's lifecycle page, extended support for Dynamics NAV 2018 ends on 11 January 2028. Build new integrations against the Business Central API (see Business Central) and keep what you build for NAV small.
NAV 2018 publishes pages, codeunits and queries as SOAP and OData web services. The middleware signs in with NavUserPassword or the user's web service access key; use a technical user with read rights only. NAV has no change events, so the middleware reads new serial numbers on a schedule.
Until the upgrade, a file export is often enough: the middleware (or a scheduled report) writes the serial numbers
with the column names of the generic-csv preset, and the file is staged as in
units from production.
Interfaces and how they were checked
- Vendor
- Microsoft
- Deployments
- On-premise: Dynamics NAV 2018
According to Microsoft, extended support ends on 11 January 2028. New integrations should target the Business Central API; until the upgrade, a file export with the generic preset is enough.
An integration pattern, not a connector: BatteryPass ships no ERP connector and holds no vendor certification.
| Interface | Protocol | Sign-in | Events | Objects | Checked |
|---|---|---|---|---|---|
SOAP web servicesPublished pages and codeunits | SOAP | Basic auth, API key | none | Product/material master, Batch/serial number, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
OData web servicesPublished pages and queries | OData V4 | Basic auth, API key | none | Product/material master, Batch/serial number, Delivery/goods issue | checked in the vendor documentation, 24/10/2026 |
Notes
SOAP web services: Sign-in with NavUserPassword or the user's web service access key.
Import presets
Generic CSV file (generic-csv): For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.
| Column in the export | Field in BatteryPass |
|---|---|
GTIN (also EAN, GTIN-13, GTIN-14) | GTIN (GS1) identification.gtin |
Serial number (also Seriennummer, serial_number) | Serial number identification.serial_number |
Manufacturing date (also Herstelldatum, manufacturing_date) | Manufacturing date identification.manufacturing_date |
Facility (also Produktionsstätte, Facility GLN, Werk-GLN) | Place of manufacture identification.manufacturing_place |
Model version (also Modellversion, model_version) | Model version model_version |
Battery status (also Batteriestatus, battery_status) | Battery status identification.battery_status |
Workflows
- Units from production: Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears. Key scopes: import
- Passport links back into the ERP: The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it. Key scopes: read
- Returns and repairs as lifecycle events: Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history. Key scopes: readcondition