Until a few weeks ago, we had some triggers available from Dynamics NAV in Flow:
It seems that these triggers are not available anymore?
Anyone else noticed this, any suggestions?
There were a couple issues regarding how the triggers were working so they were hidden until a solution is available in a few months. If you have an existing Flow created, the triggers will continue to work.
Targeting to have an upated connector as part of our work in the next semester. We plan on doing a blog post on this shortly.
Found a work around to expose the triggers. The triggers are hidden but still seems to work. I fudged it by manuapalting the URL.
In my example, I needed to trigger the flow when a record was created in NAV. I create a sample flow using another trigger and then manuapulated the URL (as below).
You might have to adjust the URL to suit your region. You can swap out the operation ID if you want to expose other triggers (modify / delete). They are documented on the Flow connector website.
This only gives you the trigger to start the flow but was good enough for my scenario. If you want to expose triggers in the other places in the flow you can download the flow in JSON format and edit the JSON. Get's pretty messy through.
Hope this helps somewhat.
The official response from Microsoft can be read here https://blogs.msdn.microsoft.com/nav/2018/04/16/use-microsoft-flow-to-build-automated-workflows-base...
It was promised to deliver some news about it this Fall but until now there is no news.
I was able to create a flow connecting to a NAV. It was exported a package file before it was hidden and after imported. This flow is working on a Test scenario with few lines and it is stable!
Triggers will be available for Business Central (SaaS) within the next couple weeks. The connector, in preview, was reconfigured to utilize the Business Central API layer and a new Delta Service was created to better monitor changes in the data set.
Unfortunately, this functionality will not be made available for Business Central (on-premises) and NAV users. The Intelligent Cloud functionality released in October could be used as a work around. This functionality enables customers to replicate data from their Business Central (on-premises) solution to their Business Central (SaaS) tenant to enable usage of cloud services, such as Machine Learning, Power BI, Power Apps, and Microsoft Flow.
Support for NAV 2018 and the Intelligent Cloud is currently planned for the Spring '19 release.
hi @arootman , what do you mean with i create a sample flow using another trigger and then manuapulated the url? Which trigger is "Another"
To “work around” the issue follow these steps:
When a record is created
When a record is deleted
When a record is Modified
Note these triggers have since been deprecated so not sure about the reliability. Since the BC connectors don’t work with NAV I have resorted to use the HTTP request trigger (in flow instead and have added code and event subscribers in NAV to call the HTTP end point in flow.
hi @arootman one step closer, i have the trigger visible but where do i need to enter the odata urls? I try to connect to a NAV On Premise...
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks