Best performance between Webshop and NAV 2013?

BoBrinkmann
Member Posts: 2
What is the fastest way to communicate data between the shop and Nav 2013
Is it via:
web services?
ODBC?
Files?
Direct entries in the database?
There should be no safety issues, about the solution and perfomance should be as high as possible.
Online users on average approx. 100
Is it via:
web services?
ODBC?
Files?
Direct entries in the database?
There should be no safety issues, about the solution and perfomance should be as high as possible.
Online users on average approx. 100
0
Comments
-
Direct to SQL is the fasted but you still need to run the business logic.
You could insert it into staging table and process them from NAV.
But I suggest implement it with web services. The two system are separate db.
Have a separate task send the data asynchronously.0 -
I'm curious, why write directly to SQL table? You can directly write to the SQL table, but you're still subject to the delay of actually processing the data when the data gets to the staging table.
Web service is a direct link and it validates business logic.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
First of all because web services are a three-tier, RTC thing.
I see the delay as a feature, not a bug. I don't believe in "silently" importing data automatically. Rather, the Order Processor should go to a button twice a day that says "Import Web Orders", and if there is an error message he can call me immediately. That is a proper solution, that means any problem will be promptly dealt with because the process is overseen by a human.
"Silent" imports such as scheduled with NAS are very dangerous. There is some error, nobody notices that it stopped, people wonder how comes we have no orders for the last week, then angry customers call in the hundreds...
This should be a principle really. If ever data is loaded into Navison, it should be initiated by a person pressing a button. So if it does not works they know it.
If a webshop "pushes" data into Navision through web services, and something fails, how does the Order Processor know about it?0 -
BoBrinkmann wrote:What is the fastest way to communicate data between the shop and Nav 2013
web services?
ODBC?
Files?
Direct entries in the database?
There should be no safety issues, about the solution and perfomance should be as high as possible.
Online users on average approx. 100
Probably using SQL to reading data and web-services with Nav to provide business logic better choice.Looking for part-time work.
Nav, T-SQL.0 -
using web-service is best practice to integrate NAV system with an e-com system. To retrieve data from NAV on behalf of any calculation you can use Sql services.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions