CData Arc

While our talented Arc support team is always happy to help resolve errors that you are seeing, it can certainly be nice to handle simpler issues on your own. To that end, we’ve compiled a list of common Arc errors and their solutions to arm you against those pesky red bars. If your error isn’t included in the list and you think it belongs, feel free to post it below! We’re always looking to expand our self-service resources and would love to hear your feedback. -- Matt S

Hi,I was wondering if it was possible to write and save custom code snippets which would be available for use with any script block.  I have a lot of custom scripts that I re-use often and was wondering it there was a way to build upon the default snippet list.  Either through the Arc interface or by adding my own code files within one of the Arc directories.  Thanks!

This is a continuation of the discussion in Mapping a document with parent-child relationships to CSV (small files)In the previous discussion, relative XPaths were used to map header elements to line values in the XML Map, but this can become impractical if the input XML is very large, as is often the case with large inventory reports and health care claim reports. Loading the XML document model for large files in memory can often require more memory than is available, or at least significantly degrade performance.  Fortunately, there is a feature of the XML Map that allows for efficient processing of XML files, available in the Advanced tab called XML Streaming:  When XML Streaming

In the destination map, we need to access elements from two different tiers in the source XML hierarchy - transaction level elements like the name and order number come from the Order level, and line level elements like the item name and cost come from the Order Line level. For smaller source documents, the simplest way to create such a mapping it to begin by creating your Foreach mapping to the destination at the line level that you are mapping, to, creating a Foreach from the Orders/Items element in this case to the OrderLines in the destination: A frequent case that come up in CData Arc is a need to map a more complex data structure (such as an order) into a flat structure, such as a CSV. For this example, we’re going to use a source XML with two orders:<Items> <Orders> <CustomerName>Teddy Blasingame</CustomerName> <PONumber>PO042619</PONumber>

Once you have begun a mapping using XML Map, you will find that is you attempt to update the source document, the XML Map connector will prompt you to restart your mapping: If you’ve already begun a really complicated XML Map, you don’t want to lose your progress, so how do you introduce a minor change, like a few additional elements?  First, it’s not required that the source of your XML Map exactly match all of the possible nodes for mapping, so if you just need to access a new field, in the same loop - for example, Name, you don’t need to use the designer to drag and drop the element onto the destination, you can just start a new expression and manually type in the XPath of the element you want to grab:  

A common challenge that can be encountered in mapping projects occurs when a data source contains element that can be grouped into multiple transactions, but the format of the data is in a flatten data model. A simple example of this can be seen in many CSV files: OrderNumber Customer Date Item Qty 12345 James Blasingame 3/17/23 Corned Beef 1 12345 James Blasingame 3/17/23 Colcannon 1 12346 Teddy Blasingame 3/17/23 Peanut Butter 1 12346 Teddy Blasingame 3/17/23 Apples 2   With the human eye, it is easy to tell that this table represents two separate transactions, each of which contains 2 line items (Or

There’s a question that arises in configuring Arc that comes up often:I have a transport connector (like AS2 or SFTP) that receives multiple EDI files that are addressed to different interchange relationships. How can I support this in my flow if each X12 connector expects one EDI relationship (Interchange Sender ID and Interchange Receiver ID)?By default, the X12 connector is meant to be used in a 1:1 relationship with the interchange relationship in the EDI document, so if you had a sender that was using different interchange IDs for different document types - 123A and 123P for instance, you would set up X12 connectors where the Sender Identifier is configured in each one, and EDI files would need to be routed to the correct connector accordingly. Support multiple EDI relationships in a single connector (only supported in unlimited EDI licenses)If you are using a license that supports unlimited u

There’s a question that arises in configuring Arc that comes up often:I have a transport connector (like AS2 or SFTP) that receives multiple EDI files that are addressed to different interchange relationships. How can I support this in my flow if each EDIFACT connector expects one EDI relationship (Interchange Sender ID and Interchange Receiver ID)?By default, the EDIFACT connector is meant to be used in a 1:1 relationship with the interchange relationship in the EDI document, so if you had a sender that was using different interchange IDs for different document types - 123A and 123P for instance, you would set up EDIFACT connectors where the Sender Identifier is configured in each one, and EDI files would need to be routed to the correct connector accordingly. Support multiple EDI relationships in a single connector (only supported in unlimited EDI licenses)If you are using a license that supports

There’s a question that arises in configuring Arc that comes up often:I have a transport connector (like AS2 or SFTP) that receives multiple EDI files that are addressed to different interchange relationships. How can I support this in my flow if each X12 connector expects one EDI relationship (Interchange Sender ID and Interchange Receiver ID)? By default, the X12 connector is meant to be used in a 1:1 relationship with the interchange relationship in the EDI document, so if you had a sender that was using different interchange IDs for different document types - 123A and 123P for instance, you would set up X12 connectors where the Sender Identifier is configured in each one, and EDI files would need to be routed to the correct connector accordingly.  Support multiple EDI relationships in a single connector (only supported in unlimited EDI licenses)If you are using a license that supports unlimited use of th