Reply
Member
Posts: 3
Registered: ‎06-18-2012

ARB Upload?

Our IT department is working with us to try to upload ARB files, we currently have a "text delimited" string in the DESCRIPTION field that we use to identify and automatically post the transactions to our files when they are charged.  The upload also uses a text delimited file.  Is there any way to tell the upload system to ignore the DESCRIPTION information?  Currently it is reading it as part of the upload and nothing will upload properly.  If we do not have the breakdown in the description when it charges then we will not be able to update our records here.  Any suggestions, help?

Member
Posts: 3
Registered: ‎06-18-2012

Re: ARB Upload?

Found the section on the FAQ's regarding encapsulation, we are trying this now.

 

An encapsulation character is really only needed when the possibility exists that the delimiting character may be included in an actual field value, which could cause an error when the data is parsed. For example, if you submit an address that you would like to include on the receipt page, and the address text includes a comma, the encapsulation character will ensure that data in the transaction response is parsed correctly by the merchant's Web server. This is also a good example of why common characters, such as a comma, are not the best delimiting characters. If you use an uncommon delimiter, (i.e., |), you do not necessarily need to configure or use an encapsulation character.

Member
Posts: 3
Registered: ‎06-18-2012

Re: ARB Upload?

We are using both delimiting character (,) and encapsulation character (") in our string.  This is the problem.  We need a way to make the Authorize keep it as one field.

 

Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: ARB Upload?

[ Edited ]

You can change the delimiting char and/or encapsulation char on the merchant account. Then have the IT create the upload using the new delimiting/encapsulation char.

Or change what to fields to upload in the merchant account.