Change in Quantity for PreAuthorization transactions from C&P Connect?

[Frank]

Dear C&P,

In June 2016 and prior, we were able to manage and edit Recurring transactions from C&P Connect. When setting a new credit card number, it would create a C&P Data with the following XML...

<ItemName>PreAuthorization</ItemName>
<Quantity>1</Quantity>

and a C&P Transaction and Opportunity with the PreAuthorization Opportunity Product.

Starting sometime around July 2016, using the same C&P Connect web interface, they now come in as follows in the C&P Data:

<ItemName>PreAuthorization</ItemName>
<Quantity>0</Quantity>

The problem is this creates an exception because the Quantity in Salesforce Opportunity Products(Opportunity Line Items) can't be zero. I am pretty sure this is core Salesforce, not special to us:

Upsert failed. First exception on row 0; first error: FIELD_INTEGRITY_EXCEPTION, field integrity exception: Quantity (quantity must be nonzero): [Quantity]

Can you reinstate the Quantity of 1 for PreAuthorization transactions? I believe this is a basic data integrity issue for anyone who preauthorizes.

Thanks for considering,
Frank

[CnP.Support]

Good day Frank

Our team is reviewing this case. I will update you once our team has reviewed it.

[CnP.Support]

Good day Frank

Would you please post an order number for a transaction that you are seeing this. This way we can review the posted XML

[CnP.Support]

Frank

May we also have access to the account to review the order number.

[Frank]

We had already granted to C&P Support case #45660, but I've granted login access for another week.

Once logged in, you can see these three newer C&P Data with bad PreAuthorization Quantity of 0:

1607111818419310200
1607121403137616021
1607181924361612617

At the time, an Opportunity Product wasn't created because of the field integrity exception, but I manually added the PreAuthorization back to the Opportunity.

These two older C&P Data with good PreAuthorization Quantity of 1:

166211045019517858526
1662810432135371554147

Thanks in advance for any insight.

Frank

[CnP.Support]

Good day Frank

Please provide us with your Salesforce Organization ID. In the future it will help us a great deal if you provide the Salesforce Org ID with the initial post so we can make sure we know what instance we have to review.

Once we have the Salesforce Organization ID we will proceed.

[Frank]

Fair enough -- we are 00D80000000aMTi.

[CnP.Support]

Good day Frank

I have submitted this to the team to review. In reviewing your account I noticed you are a release behind. Do you want us to upgrade you while we review your instance?

[Frank]

Thanks in advance for reviewing.

In terms of being behind, yes, we were on June's 9.4, but July's 9.5 just got released after this thread was started (July 27 according to https://forums.clickandpledge.com/fo...release-9-5011 ).

I'll admit I prefer to let the dust settle on these releases. However, it it is determined that PreAuthorization behavior changed in 9.5, I'm happy to do the upgrade in the evening or weekend to minimize any disruption.

Frank

[CnP.Support]

Good day Frank

The pre-authorization is a matter of Connect and how it posts the data to Salesforce.

A bit of history on this behavior.

The post was changed since in Salesforce we had to have a line item for processing. Connect was not posting any line items to start with but it was changed to make sure Salesforce does not run into issues. A preauthorization does not have any line items that is being purchased. It is just to tokenize the card.

We have requested this to be changed in Connect and it will be changed in an update soon.

The Salesforce update has nothing to do with this issue.

Just wanted to clarify this.

[CnP.Support]

Good day Frank

We just updated the core API to address your request.

Please see: https://forums.clickandpledge.com/fo...96-enhancement

Hope it helps.

[Frank]

Dear C&P,

Many thanks for making this update. I had been hoping to explicitly try it out, but we'll just wait until our next pre-authorization case to see the change.

We also did the Salesforce update anyway, figuring it was good to be on the latest.

Yes, we have seen a bit of the history of pre-authorizations. One other peculiarity that is because the PreAuthorization doesn't haven't a SKU, it doesn't match any existing Product. Thus, every pre-authorization ends up creating a new Product (not to be confused with Opportunity Product / Opportunity Line Item).

<OrderItem>
<ItemID>1</ItemID>
<ItemName>PreAuthorization</ItemName>
<Quantity>0</Quantity>
<UnitPriceCharge>0</UnitPriceCharge>
<UnitPriceDue>0</UnitPriceDue>
<UnitDeductibleCharge>0</UnitDeductibleCharge>
<UnitDeductibleDue>0</UnitDeductibleDue>
<TaxAmountCharge>0</TaxAmountCharge>
<TaxAmountDue>0</TaxAmountDue>
<DiscountCharge>0</DiscountCharge>
<DiscountDue>0</DiscountDue>
<SKU></SKU>
</OrderItem>

It doesn't cause an exception like what started this topic but causes a bit of sprawl in our Price Book. If there's any way to add a SKU of "PreAuthorization" without disrupting anything else, that might benefit others too.