RTC XMLPort.BREAK
Roelof
Member Posts: 377
I noticed that a CurrXMLPort.BREAK does not behave the same way as in classic. The Break actually stops the XMLport immediately instead of stepping out of a DataItem loop. Is there any work-around?
Roelof de Jonghttp://www.wye.com
0
Answers
-
It should work the same way, it probably depends on where you put the break statement, normally this would we done in these triggers: Export::OnPreXMLItem() or Export::OnAfterGetRecord()
TableName - Export::OnPreXMLItem() if Something then CurrXMLPort.BREAK TableName - Export::OnAfterGetRecord() if SomethingElse then CurrXMLPort.BREAK
I would not advise to use the BREAK function during import. Skipping data imported should be handled differently0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions