06-01-2017 01:01 PM
After the https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Enhanced-Customer-Prof... announcement that added the CIM profile id's to the getTransactionList, we're now noticing transaction nodes getting duplicated. One of the transaction nodes will include the "profile" node with the CIM data and the other transaction will be missing that node.. Othere than that, they are duplicates, and I'm assuming that's not an intentional change.. Is it?
06-02-2017 01:56 PM
Great. I don't have settled profile transactions in my sandbox account to look at right now, but I'll try some testing on my end and wait for the transactions to settle.
In the meantime, is every transaction node that's associated with a profile duplicated (without profile info in the duplicate), or just some of them?
06-05-2017 07:25 AM
Not all are duplicated... out of 151 from yesterday, 103 had duplicate transaction nodes (one with a profile node, one without). All 48 of the transactions that showed up only once had a profile node.
I'm looking to see if I can find something about the rows that signifies them as different, but haven't seen a pattern yet.
06-05-2017 07:51 AM
Just found a couple of patterns... It appears to be tied around if the transaction flowed through an Authorize then Capture or AuthorizeCapture in one step flow. Here's how I got there..
Hope that helps narrow it down
06-05-2017 01:59 PM
That's very useful information, thanks! There's two things going on here:
I'll run this around the company to see if I can get a handle on whether or not this is working as designed. If not, we'll look to fix it. If so, we can talk about changes to make it less confusing, or at least better explanations in the documentation.
Thanks for following up on this!
06-05-2017 02:25 PM
You *might* be able to convince me that it was intended to have tow listed, but then I would additionally expect to see a different state or something else aside from just the appearance or lack of appearance of the profileID.
In addition, duplication of any form before the addition of the profileID did not happen, so I would certainly call it a braking change either way as the current behavior was only ever returnig one node per transaction.
Love to hear what you find
06-08-2017 07:36 AM
Is there any update on this? My accounting department is asking why the reconciliations aren't lining up and I'd like to know if there is a way forward on this one.