Hello,
We just upgraded our Production instance to the most recent version of C&P (there was a long gap), and part of our post-deploy is 'Posting' Recurrings so that all of the fields update on the pre-existing Recurring objects in SF. The *vital* fields are working (like Status), but a handful of fields are not updating (C&P Account Number, Currency, Payment Type, Credit Card Name, and Credit Card Expiration). Those fields update fine if either a start a new Recurring from scratch, or, in the case on one Recurring that had a payment that was missing in SF (and thus causing the Recurring to be out-of-sync), if I post the missing payment.
Is this expected behavior? My best guess is that integration needs a certain threshold of changedness (like if the Status changes) before it even bothers updating those.
Thank you,
Nick
We just upgraded our Production instance to the most recent version of C&P (there was a long gap), and part of our post-deploy is 'Posting' Recurrings so that all of the fields update on the pre-existing Recurring objects in SF. The *vital* fields are working (like Status), but a handful of fields are not updating (C&P Account Number, Currency, Payment Type, Credit Card Name, and Credit Card Expiration). Those fields update fine if either a start a new Recurring from scratch, or, in the case on one Recurring that had a payment that was missing in SF (and thus causing the Recurring to be out-of-sync), if I post the missing payment.
Is this expected behavior? My best guess is that integration needs a certain threshold of changedness (like if the Status changes) before it even bothers updating those.
Thank you,
Nick
Comment