Error importing data directly from one instance to another via XML data source.Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } --> Error importing data directly from one instance to another through XML data source ProblemWhen importing data directly from one instance to another instance via XML data source sometimes an error occurs: The current node has been removed using a method other than Iterator#remove() in the progress page. SymptomsAfter executing the data source, in the progress page you can see the following: The state is complete and completion code is Error with the message: The current node has been removed using a method other than Iterator#remove()In the local host logs the following stack trace appears:ImportProcessor SYSTEM SEVERE *** ERROR *** com.glide.db.impex.XMLLoader java.util.ConcurrentModificationException: The current node has been removed using a method other than Iterator#remove() at org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:67) at org.jaxen.util.DescendantAxisIterator.hasNext(DescendantAxisIterator.java:101) at com.glide.xpath.GlideStep$GlideStepImpl.nextFromIterator(GlideStep.java:80) at com.glide.xpath.GlideAllNodeStep.nextFromIterator(GlideAllNodeStep.java:49) at com.glide.xpath.GlideXPath.selectNextNode(GlideXPath.java:118) at com.glide.util.XMLStreamDocument.selectNextNode(XMLStreamDocument.java:284) at com.glide.db.impex.XMLLoader.next(XMLLoader.java:175) at com.glide.db.impex.XMLLoader.getColumnAttributes(XMLLoader.java:291) at com.glide.db.impex.AbstractLoader.createTableFromImportData(AbstractLoader.java:375) CauseThe problem seems to be triggered when both element and its attribute are named similar. In other words, whenever a table and its field has the same name, this issue happens when import is performed through the xml datasource from one instance to another. For example, https://xxxx.service-now.com/u_sar_item.do?XML <xml> <u_sar_item> -----------------------------------------------------------------------------> Element name <sys_created_by>NORMOYS</sys_created_by> <sys_created_on>2015-05-07 15:31:54</sys_created_on> <sys_id>0f5844cf9973310001ccc5dc7b0dd344</sys_id> <sys_mod_count>0</sys_mod_count> <sys_updated_by>NORMOYS</sys_updated_by> <sys_updated_on>2015-05-07 15:31:54</sys_updated_on> <u_association/> <u_item_display>Business Central OLB</u_item_display> <u_sar_item>ce88fdfaa467b5009a24c1eea0d7430c</u_sar_item> ------>Attribute with the same name as element. <u_task_approvers/> <u_task_instructions/> </u_sar_item> u_sar_item is the table name, and it also has a field named u_sar_item. ResolutionRename either the element/table or the attribute/field so that the names do not match.