Chargebee Release Notes

When you changed the billing cycle while creating or editing a quote, the system needed a moment to retrieve the updated billing configuration in the background. If you clicked Create or Update before that fetch completed, the quote could be built using outdated billing cycle information. Chargebee for Salesforce now waits for the latest billing configuration before submitting your change, so quotes always reflect the billing cycle you selected.

If your Salesforce user time zone was set behind Chargebee's time zone, editing a quote could incorrectly increase the billing cycle due to a date conversion issue. This affected the billing cycle calculation during the edit quote flow. Billing cycles on edited quotes now calculate correctly regardless of the time zone configured for your Salesforce user.

When attempting to change a subscription in Salesforce to a plan configured for a different billing period than the current one—such as switching from a monthly plan to one set up only for yearly billing—the target plan was not appearing as an available option on the Change Subscription page. This occurred even when the plan existed in both Chargebee and Salesforce. This fix ensures that all eligible plans, regardless of their configured billing frequency, now appear correctly when you initiate a subscription change.

If your Salesforce workflow includes ramp pricing on opportunities, you may have noticed the Chargebee-Salesforce sync becoming unresponsive, with sync logs showing large gaps or no activity for extended periods. This occurred when subscriptions were created through a checkout link tied to a ramp-based opportunity, causing the sync process to become overloaded and stall. This fix ensures the sync runs reliably so your Chargebee data stays up to date in Salesforce without manual intervention.

If you tried to use Manage CB Products on an opportunity that didn't have an account associated with it, you previously saw a generic list index error with no clear next step. Now, Chargebee shows a clear message letting you know that the opportunity needs an account before you can proceed, so you can associate one and continue without confusion.

If you tried to modify an existing product or add-on directly on an opportunity using Manage CB Products, the page may have frozen and become unresponsive, even though removing the item and adding a new one worked without issue. This happened when replacing an add-on on an opportunity that already had a product and add-on added through Manage CB Products. You can now modify existing products and add-ons directly without the page freezing, so you don't need to remove and re-add items as a workaround.

If you updated a checkbox-type custom field from Salesforce, the value may have synced to Chargebee in lowercase, such as "true" or "false," while updates made directly in Chargebee used "True" or "False." This created inconsistent values across customer records depending on where the update originated. Checkbox custom field updates from Salesforce now sync with consistent casing, so your customer records stay uniform regardless of where the change was made.

If you ran Apex test classes that inserted test accounts, you may have run into an unexpected error, even though Chargebee sync wasn't enabled for those test records. This affected merchants updating or testing their Salesforce package version. Your test classes now run without this error when Chargebee sync isn't enabled for the account being tested.

If you created a second amendment quote on the same opportunity, you may have noticed the contract start date defaulting to today's date instead of the correct date, along with existing ramps missing from the items and pricing section. This occurred specifically when a subsequent amendment quote was created on the same opportunity as an earlier quote. Amendment quotes now reflect the correct contract start date and carry over any existing ramps on the subscription, so the quote details match what's actually on the account.

If a ramp created in Salesforce didn't sync to Chargebee, for example when an opportunity was marked Closed Lost before the ramp was needed, it could be difficult to tell whether the ramp was actually synced. You can now more easily identify ramps that haven't synced to Chargebee, helping you spot and address sync issues before they affect a subscription.

If you used Create Quote for Amendment on a subscription that had ramps, those ramps may not have appeared on the quote. Amendment quotes now correctly load and display any ramps on the subscription, so your quote reflects the actual terms of the account.

If you generated a detailed Quote PDF, you may have noticed the item description appearing twice. The detailed Quote PDF view now shows the description only once, keeping your quotes easier to read for prospects and customers.

When you tried to create an amendment quote for an amendment opportunity in Salesforce, the quote screen loaded indefinitely and never displayed the quote. This affected all opportunities rather than a specific one, making it impossible to complete amendment quoting in the affected environments. This is now fixed, so amendment quotes load as expected every time you open them.

If your subscription ID included special characters such as + or &, ramps created or updated for that subscription in Salesforce did not sync over to Chargebee. The subscription itself would sync correctly, but the associated ramps failed to appear on the Chargebee side, creating a gap between what you set up in Salesforce and what took effect in Chargebee. This is now fixed, so ramps sync correctly regardless of the characters used in your subscription IDs.

If you applied manual discounts to both a plan and an addon on a quote and then created a new quote from the same opportunity to take them off, only one of the two discounts was actually cleared. The other stayed on the quote, so the customer saw a lower price than the one you meant to send. This happened on new subscription, upgrade, and change subscription quotes, including quotes that also had coupons applied to the plan and addon. Clearing a manual discount now removes it from each line you cleared it from.

The default value you set for Billing cycles in access control was ignored on the create subscription screen, so your reps had to type it in themselves and could enter something other than the default you intended. This affected users in the Salesforce public group that the access control setting was assigned to. The default now applies when the subscription is created.