Opinion on Api strategy
We are moving from nav to bc. Our solution is heavily integrated to other solutions. One of the challenges is that all our integration is build on soap. But this will be deprecated in bc. After looking at standard ui pages, custom ui pages and odatav4, I found that these 3 technologies have limitations and issues.
Odatav4 in bc does not support deep inserts. Therefore, multiple operations have to be done using $batch calls. And there is a limit of 100 operations per batch.
As for custom ui pages, it does support deep inserts, but it has a bug where duplicate inserts can happen.
As for standard ui pages, it did not have the duplicate insert issue in custom ui pages, but standard ui pages cannot be extended.
In all these respect, cannot help but feel that soap is better.
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
- 321 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