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?
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 differently
Answers
I would not advise to use the BREAK function during import. Skipping data imported should be handled differently