CData Arc

OverviewBearer token authentication can be one of the more finicky authentication mechanisms to implement within Arc. The reason is because the token lifetime is very short and automatic token refresh isn’t something that is built into that mechanism, like it is with OAuth 2.0. Thus, a new token needs to be generated and manually re-entered every time the old one expires. This isn’t really practical in Arc since many flows rely on automation to continually process files or make requests to APIs. Luckily, in Arc t is possible to create a custom script that gets a new token for each request that you send and then the token is dynamically evaluated within the REST connector.The ScriptThe script that should be used here is going to need to be responsible for two things:1) Obtaining a refresh token from the token endpoint of your API2) Adding the token as a header onto the message within ArcThis will fire every time your input file passes through the script and will get a new token for each

CData Arc’s enterprise edition includes a built-in tool to generate custom reports tracking EDI messages, file exchanges with partners, and much much more. To learn how you can start building multi-dimensional reports out of CData Arc’s transactions in mere minutes, simply watch our 4-minute video tutorial:  As always, feel free to ask any questions or provide any feedback as you generate your own reports! -- Matt S

Hello,Thought I’d post this question here to help build content for the community.I have a situation where I have a workspace dedicated to  complete document flows for all EDI trading partners (832, 850, 855, 810, 856).  I have a single X12 connector where all documents either send or receive files.I have another workspace where I have specific  1-off flows created where my application interacts with Arc via API.An ongoing issue (in my industry) has always been customers asking us to re-send 810 Invoices. My main workspace is setup to send 810 files in a batch at the end of the day.  So I have a flow I created in my “API” workspace where my application allows the user to generate a single 810 file and makes an HTTP POST to the workspaceid and connectorid using /api.rsc/receiveFile through the Admin API.My question is this:  Since I already have these trading partners X12 connectors (and corresponding AS2 or SFTP connectors) setup in another workspace, is it possible to use the Branch c

I need to be able to ingest the following string and remove everything but the financial values in an xml map connectorCIGNA;QPA=242.06any direction is appreciated. This is for an x12 837 file

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 is enabled, only the subtree for a particular element is available while the XML document is processed, allowing the connector to only load the relevant chunk of XML at a time.  When doing this, relative XPaths as in our previous example are not available, so how can we access elements that are available at

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> <Items> <Name>Number Puzzle</Name> <C

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:   Still, it is possible to replace the source XML in the XML Map without starting your mapping over by uploading the new XML file and then overriding the source in the XML Map with the new file without using the designer by doing the following: Create a copy of the updated source temp

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 the EDI connectors, you will find an option in the Advanced tab to relax the valida

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 unlimited use of the EDI connectors, you will find an option in the Advanced tab to rela

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 the EDI connectors, you will find an option in the Advanced tab to relax the vali