In Cobalt 4.0 we update the Cart Checkout Process to write data to a transitory database (referred to as the supplemental SQL database) and sync back to D365 using Azure functions, rather than directly writing it to D365.
Use Case
Mitigate the impact of service protection limits:
Safeguard against service protection limits and prevent against missing or duplicated payment information.
If a payment was rejected by Dynamics after charging a card with the payment processor, a manual reconciliation process would need to take place to get that payment into Dynamics. Depending on the processor, there's also the possibility of the portal subsequently allowing the user to charge their card again due to the fact that our system does not have a record of their charge occurring.
Benefits
Checkout processes in the Cobalt Portal and ISV applications can take a user from payment entry all the way to the receipt page without needing to talk to Dynamics. This results in no process queued payments cron job and overall faster processing time.
Checking error logs
If a transaction fails, a configurable number of re-attempts will occur until the message gets pushed into a Dead Letter queue. Below are the steps to take to look at the error logs.
1. In Dynamics 365 click on the funnel icon on the top left of the page
2. Within the Advanced Find set the look for to Integration Logs
3. Add a criteria for Subject name containing "Deadletter"
4. Click the Date Created column header to filter and find the most recent Integration logs
5. Open the desired Integration log
