NAV working with .NET

hiddentexthiddentext Member Posts: 45
Hi All,

I need to find a way so that .net web application can pass information through to Nav to create Sales order real time.

Is NAS a good way to go? Can this be done in real time?

Thanks,

Comments

  • SavatageSavatage Member Posts: 7,142
    have you looked at these code samples?
    http://www.mibuso.com/dlinfo.asp?FileID=775
    The Dynamics™ NAV Web Store site demonstrates how simple it is to create applications and services for Dynamics™ NAV and the .NET platform.

    After installing the sample site, start browsing and add items to your shopping cart and submit it to the Dynamics™ NAV back end system for ordering. You can create reviews for any items; you can review your existing orders… Take the quick tour to know more about it.

    there might be other .NET stuff in the downloads section, this is the one I remember.
  • nunomaianunomaia Member Posts: 1,153
    Also check this document in MSDN

    Talking with Navision: Accessing Navision Business Layer through a Web Service

    http://msdn2.microsoft.com/en-us/library/ms952079.aspx
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • jlandeenjlandeen Member Posts: 524
    As this example illustrates this can definately be done in real time and I have worked on many projects that work in a similar fashion to what Patrice (he's the Microsoft Guy that put together that download) has done. They're stable and allow Navision to stay focused on it's job and the external application to send/request data as it needs it. It also allows for better licensing as not every user who needs to simply check something or create a sales document has to use up a Navision license.

    One key aspect I have found when doing anything with .Net/Navision & Webservices is to decide how generic and extensibile you want things to be. I have built a few frameworks with clients that try and minimize the amount of business logic that occurs in the Web Service layer. Business logic should be restricted to either your calling .Net application or Navision with nothing in between. The goals of this approach is to minimize support and maintenance problems going forward. It is enough to maintain a web application and Navision and the communicating web service should be as minimal as possible.

    If the componets are built well the first time around they can be easily leveraged to expose additional functionality by adding another XML port and with a minimum of fuss. Please feel free to email me if you require more details (as they can get a little specific and may not want to spam everyone here).
    Jeff Landeen - Sr. Consultant
    Epimatic Corp.

    http://www.epimatic.com
Sign In or Register to comment.