Howdy, Stranger!
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
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
how to prevent a create from triggering an insert and modify
happyllama
Member Posts: 2
Hello,
I have a high-performance integration use-case with NAV, where customers can add lines to their order from our ecommerce website. This is the SOAP created for the creation of a new sales line:
SOAP Message: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:salesorderline="urn:microsoft-dynamics-schemas/page/salesorderline"><SOAP-ENV:Header/><SOAP-ENV:Body><salesorderline:Create><salesorderline:SalesOrderLine><salesorderline:Description>Artichoke</salesorderline:Description><salesorderline:Quantity>1</salesorderline:Quantity><salesorderline:Document_Type>Order</salesorderline:Document_Type><salesorderline:Type>Item</salesorderline:Type><salesorderline:Line_No>33000</salesorderline:Line_No><salesorderline:Unit_of_Measure_Code>EA</salesorderline:Unit_of_Measure_Code><salesorderline:No>4552</salesorderline:No><salesorderline:Document_No>SO0000000000000025</salesorderline:Document_No></salesorderline:SalesOrderLine></salesorderline:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
The performance isn't bad, but it isn't ideal either (about 300ms). I noticed that both the onInsert and onModify were being triggered. My question is, is there a way I can force this create to be a single Insert, thus calling only the onInsert biz logic and hitting the database only 1 time?
I tried the DelayedInsert property on the Page, but unfortunately that did not have any noticeable impact.
I have a high-performance integration use-case with NAV, where customers can add lines to their order from our ecommerce website. This is the SOAP created for the creation of a new sales line:
SOAP Message: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:salesorderline="urn:microsoft-dynamics-schemas/page/salesorderline"><SOAP-ENV:Header/><SOAP-ENV:Body><salesorderline:Create><salesorderline:SalesOrderLine><salesorderline:Description>Artichoke</salesorderline:Description><salesorderline:Quantity>1</salesorderline:Quantity><salesorderline:Document_Type>Order</salesorderline:Document_Type><salesorderline:Type>Item</salesorderline:Type><salesorderline:Line_No>33000</salesorderline:Line_No><salesorderline:Unit_of_Measure_Code>EA</salesorderline:Unit_of_Measure_Code><salesorderline:No>4552</salesorderline:No><salesorderline:Document_No>SO0000000000000025</salesorderline:Document_No></salesorderline:SalesOrderLine></salesorderline:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
The performance isn't bad, but it isn't ideal either (about 300ms). I noticed that both the onInsert and onModify were being triggered. My question is, is there a way I can force this create to be a single Insert, thus calling only the onInsert biz logic and hitting the database only 1 time?
I tried the DelayedInsert property on the Page, but unfortunately that did not have any noticeable impact.
0