# Microsoft Dynamics NAV - Ignition

**URL:** <https://forum.inductiveautomation.com/t/microsoft-dynamics-nav-ignition/93261>\
**Category:** Ignition\
**Created:** [July 15, 2024, 10:24pm UTC](https://forum.inductiveautomation.com/t/microsoft-dynamics-nav-ignition/93261 "2024-07-15T22:24:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DAC2](https://avatars.discourse-cdn.com/v4/letter/d/f6c823/32.png) [@DAC2](https://forum.inductiveautomation.com/u/DAC2)\
**Post date:** [July 15, 2024, 10:24pm UTC](https://forum.inductiveautomation.com/t/microsoft-dynamics-nav-ignition/93261/1 "2024-07-15T22:24:56Z")

</div>

Has anyone here moved data back and forth between Ignition and Microsoft Dynamics NAV and Ignition. If so what modules did you use?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 15, 2024, 10:30pm UTC](https://forum.inductiveautomation.com/t/microsoft-dynamics-nav-ignition/93261/2 "2024-07-15T22:30:27Z")

</div>

The only module I can imagine would be relevant is the WebDev module, which would allow you to create HTTP/REST endpoints that Dynamics can call to initiate some action or get data.

In the other direction, Ignition can already make HTTP calls out of the box via `system.net.httpClient`, no extra modules required.