Don’t get me wrong, I do not see anything wrong in building everything by yourself but it is also great to know that you can do something faster and don’t need to spend time on something which was already built by someone else. Example: you can get a response from Azure Function in just 3 lines of code (not counting variables).
Tag Archives: Response
Adding Response Options
One thing I didn’t cover in my previous tutorials, is how to add an option to your responses. This allows you to have even more flexibility in how creating your workflows. One base example is the Show Message response. It has a single option.
Remove Namespace – Web Service Response (DotNet Variable)
This Post is about How to Import directly an XML which is coming as Web-Service from different platform like .NET. Whenever we get a response from a .NET Service we usually get Namespaces coming as enclosed in it. Now being a NAV developer it’s something which becomes a barrier to us while getting it directly Imported from NAV XML Ports. So here we are to how get rid from this.
Remove Namespace – Web Service Response (Automation Variable)
This Post is about How to Import directly an XML which is coming as Web-Service from different platform like .NET. Whenever we get a response from a .NET Service we usually get Namespaces coming as enclosed in it. Now being a NAV developer it’s something which becomes a barrier to us while getting it directly Imported from NAV XML Ports. So here we are to how get rid from this.
NAV 2016 Workflow Response Timing
Last week I took a look at event subscribers to see if there was a order if multiple ones got fired at the same time. It seemed like if there are multiple subscribers to an event, they are fired in order of codeunit ID and then in order they appear in the codeunit.
Reading Webservice Response
While we are integrating our NAV with any other Frontend , we should read all the response from the webservice response file for our required information. For simple testing i am just storing the response file in ‘C:\TEMP\testing.xml’ location