LogoLogo
Connectors
Salesforce B2B Commerce App 2.1.1
Salesforce B2B Commerce App 2.1.1
  • Salesforce B2B Commerce App 2.1.1
  • Introduction
    • How it works
    • What's new in version 2.1.1
    • Requirements
  • Integrating the Digital River Salesforce B2B Commerce App
    • Step 1: Install the Digital River App for Salesforce B2B
    • Step 2: Create page labels
    • Step 3: Configure the Salesforce B2B Commerce App
    • Step 4: Add custom Salesforce B2B Commerce App fields to page layouts
    • Step 5: Enable email deliverability
    • Step 6: Import ECCN codes, tax groups, and tax types
    • Step 7. Update the Product Sync settings
    • Step 8: Set up Digital River fulfillments
    • Step 9: Set up webhooks
    • Step 10: Configure CC Admin settings
    • Step 11: Configure landed cost
    • Step 12: Schedule backend jobs
    • Step 13: Manage permission sets
    • Step 14: Configure the Salesforce B2B Commerce app logs
    • Step 15: Test the Digital River Salesforce B2B Commerce app integration
  • Extending the Digital River Salesforce B2B Commerce App
    • Extend the Ship from address
    • Extend the App Webhook Framework
  • Support
  • Version number
  • Appendix
    • Fulfillment and cancellation flow
    • Issuing refunds
    • Managing regulatory fees
    • Managing subscriptions
    • Salesforce B2B Commerce App logs
    • Uploading tax certificates (US TEMS)
    • Global tax identifiers
    • VAT invoices
Powered by GitBook
On this page
  1. Appendix

Salesforce B2B Commerce App logs

Learn how to work with the Salesforce B2B Commerce App logs.

PreviousManaging subscriptionsNextUploading tax certificates (US TEMS)

Last updated 4 years ago

All Salesforce B2B Commerce App application logs are logged to a custom object called DCM Application Logs “digitalriverv2__DCM_Applications_Log__c”. The default logging level of the app is always set to ERROR. That is, it only logs errors. You can modify the default logging level in .

The app displays generic user-friendly error messages on the storefront user interface (UI), and the actual Error/Exception details will be logged to the DCM application log object. The Logging Level field on this object indicates the severity level of the log created by the application.

As you can see in the image above, there was an error while making a callout to Digital River API (Logging Level field is set to ERROR), and the request/response information is logged for debugging purposes. There are fields in this Log object that capture run-time exception information, as shown in the following image:

The Record Id field has information about the Salesforce or Digital River record that generated this log. In the following example, the Salesforce Record ID, a1U4C000000MnppUAC, generated the log. Note that the Logging Level for this record is DEBUG. That is, the severity level of this log is DEBUG, and this is only for debugging purposes. You can click the link next to the Link to Record field to go to the Salesforce record for the ID captured in the Record Id field.

Similarly, we have other fields for capturing User information (User Information section), Salesforce Governor Limits, and other support data. In case of any errors/exceptions encountered in the app, DCM Application logs would be the first place to go for debugging purposes.

Step 14