Skip to main content
Vindicia Knowledge Center

CashBox Reporting for Salesforce Release Notes 2.7

CashBox Reporting for Salesforce Release Notes 2.7

Disclaimer

As of version 14.11, CashBox Reporting for Salesforce is now known as CashBox (Basic).

Features and Enhancements

This release includes the following new features and enhancements.

Two-Way Sync for CashBox Custom Data Fields (Except for Transactions) 

CashBox for Salesforce now supports two-way synchronization for Custom Fields.

Except for Transactions, all objects which allow you to map custom Salesforce text fields to CashBox Custom Data fields (Merchant Data) now support 2-way sync. Changes made to the Salesforce values will export in near-real-time to their CashBox equivalent based on your existing mapping options.

Custom fields defined in Salesforce for mapping to CashBox must be defined as TEXT fields (of any length) on the Salesforce Object (e.g. Account) that corresponds to the matching object in CashBox. 

Sync CashBox for Salesforce with Custom Data Fields for Cashbox Payment Methods

Payment Methods have been added to the list of objects for which custom fields may be mapped. CashBox for Salesforce will support two-way sync of these fields. 

Protect Account-Level Addresses (Billing Address and Shipping Address) From Changes Due to Sync with CashBox

You may now edit Account-level addresses in Salesforce, without synchronization of changes to (or from) your CashBox system. A new checkbox is available on the Account object in Salesforce:

  • Label: Protect Account Addresses
  • Field name: cashbox.suppress_address_change

When set to true(checked), any changes to the Account-level Billing Address or Shipping Address will notexport or sync to CashBox, and changes to the CashBox Shipping Address will notupdate the Salesforce equivalent.

Changes made to the Billing Address for the default Payment Method will export to CashBox as before, but will notupdate the Account-level Billing Address in Salesforce (nor will changes to the Account-level address update the local Billing Address for the Payment Method.)

By default, this checkbox is deselected, which will maintain sync between Account-level Addresses. 

API Endpoint No Longer Fixed in Production Mode 

The API endpoint in the CashBox Admin configuration page will now be editable when the app has been installed in Production Mode. 

Revenue by Product Report Now Uses Product SKU from Completed Transactions

The included Revenue by Product Report has been updated to use the Product SKU on Transactions (from Transaction Items) rather than Purchased Products, to produce a more accurate report for revenue by individual product.

In the previous version of the report, duplication in the totals would occur when multiple products were sold on the same transaction. The new report avoids this issue. 

Revenue by Product Report Updated 

The included basic Dashboard has been updated to use the newer Revenue by Product Report in the widget of the same name. 

Most Fields for the Payment Method Layout No Longer Required by Default 

The Payment Method default layout has been adjusted so that most fields are no longer required. (These default settings may be changed by your local administrators to suit your business policy.) 

Clarifcation to CashBox for Salesforce Import Setting, 'Timestamp Adjustment for PST'

Prior Change Clarification: The CashBox Import Settings named 'Timestamp adjustment for PST' (an added configuration on the CashBox Admin tab) was not explained in previous release notes. The 'Timestamp adjustment for PST'setting allows you to define how date and date-time fields are used in outbound calls from Salesforce to CashBox.

The 'Timestamp adjustment for PST' settingmust be set to the opposite of your USE_TIMEZONE_IN_SOAP CashBox merchant setting. For example, if your USE_TIMEZONE_IN_SOAP field is set to true, the Salesforce 'Timestamp adjustment for PST' checkbox must be set to false(unchecked) to ensure that the time zone setting in outbound calls from Salesforce will match what you expect in CashBox. 

Bug Fixes

The following Bugs were fixed in 2.7:

Summary Description

Several minor bugs have been fixed in the import process. 

Several minor Bug Fixes on routine import log error messaging rules were performed to avoid unnecessary duplication of error messages. 

Multiple Product merchant data fields were not syncing properly. 

When more than one custom data (merchant data) field was defined for a Product in CashBox, only the most recent field was syncing on import (Custom Field Mapping.) All mapped fields will now import as expected. 

Some Payment Methods were not syncing correctly. 

In rare cases, some Payment Methods that were not used on any present or historical transaction were not syncing correctly. All on-file Payment Methods will now sync. 

A conflict affecting Account field export (SFDC to CashBox) when CashBox Contact is not present was preventing export. 

A Contact (CashBox-created or otherwise) is no longer required for the real-time export.

Reminder: Account field changes that can initiate exports are:

  • Account Name => [Vindicia Account] Company

  • Primary Contact => [Vindicia Account] Name

  • Account Email => [Vindicia Account] Email Address

  • All Shipping Address Fields => [Vindicia Account] Shipping Address

    If a CashBox-created Contact exists, the Phone/Fax information will also be exported to CashBox (unless this address is protected.)

  • All Billing Address Fields

    Initiates Payment Method export to the local Billing Address of the associated Payment Method’s (unless protected.) 

StoreFront

Learn More
StoreFront

CashBox for
Salesforce (Premium)

Learn More
CashBox for Salesforce (Premium)

CashBox

Learn More
CashBox
Back to Top