Skip to main content
Skip table of contents

Spring '23 Maintenance Release

This is a list of every change made in the Spring '23 release of Nimble AMS.

Nimble AMS Staff View

What's new?

Defects Fixed

One Payment Wizard now respects the Date of actual payment for credit/stored payment.

One Payment Enters Transactions in Wrong Batch / Date. (Known Issue ID-126054)


Your association may be affected if you: 

    • Use One Payment
    • Create manual batches


Original System Design: If user is using One Payment with Cash or Check (non credit) and choosing a manual batch, then the date from the selected batch should be carried over as date of the payment transaction.

    • If user is using One Payment with Credit Card and choosing a manual batch with a batch date of today, then the date from the selected batch should be carried over as the date of the payment transaction.
    • If user is using One Payment with Credit Card and choosing a manual batch and a batch date is not today, then the payment transaction should have todays’ date.


Solution: Added a logic to check one payment with Credit Card & stored payment method.

    •  If payment is using Credit/Stored payment with manual batch and the batch is for Today, then use the date from the selected batch for the payment transaction.
    • If payment is using Credit/Stored payment with manual batch and the batch is Not for Today, then use the batch of the current day and todays’ date will reflect on transaction record.


Module(s) impacted: One Payment, Manual Batch, Batches


Auto-renewal no longer creates duplicate schedules when clicking the Save button multiple times while setting up Recurring payments.

Duplicate renewal schedules occurs when a member selects the Auto-Renew Frequency for setting up Recurring Payment and clicks ‘Save’ multiple times. (Known Issue ID-125761)


Your association may be affected if you:

    • Have members who configure Auto-Renew Frequency in Community Hub (CH)


Original System Design: The configuration of the Auto-Renew Frequency field should create 1 schedule each time when a member selects the Auto-Renew option in CH.


Solution: Configured the ‘Save’ button to disable after the first click. When members click ‘Save’ the first time, members will not get the option to click ‘Save’ again till the schedule creation/update process runs fully.


Module(s) impacted:  Community Hub, Auto-Renew Membership


Coupon discount now recalculates based on the latest cart product when an order is edited.

Coupons applied on Event registration do not recalculate, if the registration order and the product is changed to a different product. (Known Issue ID-129045)


Your association may be affected if you: 

    • Have Community Hub users who modify an Event registration order
    • Use coupons


Original System Design: When a coupon gets applied on an Event registration product, while in a cart and the cart item is changed, the coupon should recalculate based on the new cart item and new total.


Solution: Added a logic to recalculate coupons on adjusted orders for Event Registration.


Module(s) impacted: Community Hub, Coupons


Resubmitting or canceling an adjusted membership order will no longer cause an error.

Error: "Problem when making a REST API call to Avalara through the SDK...uncommitted work...commit or roll back", occurs when resubmitting a membership order that was previously canceled or when canceling an adjusted cart order. (Known Issue ID-131045)


Your association may be affected if you: 

    • Cancel a membership order
    • Have external taxation (Avalara) enabled


Original System Design: Enabling external taxation should allow for membership orders to be canceled, adjusted, or resubmitted if the membership period has not begun.


Solution: Ensure external taxation is enabled and taxes are calculated before performing payment transfer.


Module(s) impacted: Memberships, Avalara


When using One Payment, an Account's Stored Payments will not show up for a different Entity's Order.

The wrong entity’s payment method pops up on One Payment when a staff user attempts to make payment for orders. (Known Issue ID-129991)


Your association may be affected if you: 

    • Use One Payment
    • Use Entity Crossover
    • Use Stored Payment Method


Original System Design: One Payment should only show payment methods for the entity in which the order was generated.


Solution: Updated One Payment logic to only show the Stored Payment Method connected to the original order entity.


Module(s) impacted: One Payment, Entity Crossover


Guest users can now submit payments for chapter membership via Express Payment.

Guest users were getting error “FIELD_INTEGRITY_EXCEPTION, field integrity exception…”  when they attempt to use Express Pay (Payment url) to pay for Chapter Membership. (Known Issue ID-130334)


Your association may be affected if you: 

    • Use Express Payment for chapter membership

    • Submit payment as Guest user


Original System Design: When a Guest user applies a coupon on an event registration product while in a cart and the cart item is changed, the coupon should recalculate based on the new cart item and new total.


Solution: Updated the Chapters cart submitter logic for to allow a Guest user to submit the payment using the express payment method


Module(s) impacted: Chapter Membership, Account Affiliation, Express Payment, Cart

Automatic Sales Tax rate calculation now applies to taxable Registration Products.

Previously, when Staff users created new Roders for non-Merchandise products (specifically Registration Products) the Sales Tax rate was not automatically selected on the Tax and Shipping page. (Known Issue ID-129169)


Your association may be affected if you: 

    • Use Orders

    • Use Sales Tax


Original System Design: The Sales Tax rate should have automatically been selected if the product was taxable.


Soultion: Added support for automatic Sales Tax rate selection for taxable Registration products. The Sales Tax will be calculated on the Tax and Shipping page.


Module(s) impacted: Orders, Sales Tax


One Payment no longer duplicates charges for Sales Tax and Shipping.

One Payment function charged Sales Tax and Shipping multiple times within a transaction but did not initiate payments for those duplicate charges, creating an accounting discrepancy. (Known Issue ID-129423)


Your association may be affected if you: 

    • Use One Payment

    • Collect Tax or Shipping on products


Original System Design: One Payment function should charge and collect Sales Tax and Shipping once per transaction. 


Solution: Assigned the existing order items to the transaction generator requests to avoid duplicate transaction entries.


Module(s) impacted: One Payment, Order Entry

Community Hub

What's new?

Defects Fixed

Resolved 38-character restriction on the customization setting fields to only apply to Field Mapping. 

Fields like google analytics and custom class names were blocked or cut off due to the 38-character limit. (Known Issue ID-131098)


Your association may be affected if you:

    • Use the Customization setting


Original System Design: All Customization fields had a 38-character limit.


Solution: Limited the 38-character enforcement to 'custom setting name’ field only.


Module(s) impacted: Customization settings, Community Hub Setup


An error when using an expired Stored Payment Method to set up Recurring payments is now rectified.

When an expired Stored Payment Method (SPM) is utilized to establish Recurring payments, an error will occur during cart submission, and the data field will be labeled with the SPM ID. If the Community Hub user removes, modifies, or generates a valid SPM, the error persists since the data field retains the old SPM ID. (Known Issue ID-129462)


Your association may be affected if you:

    • Use Flexible Payments
    • Use Stored Payment Method


Original System Design: The data field should be updated to the new SPM ID once the Stored Payment Method becomes valid.


Solution: Updated the logic to verify the expiration date of the external payment profile record before automatically assigning it to a recurring item. This will result in the data field being updated with the new SPM ID. 


Module(s) impacted: Stored Payment Method, Flexible Payments


Lightning Store now arranges the product grid by using the Display Sort Order field.

The Lightning Store product grid did not respect the Display Sort Order field when presenting the layout of merchandise/products. (Known Issue ID-120356)


Your association may be affected if you:

    • Use Lightning Store


Original System Design: The Query Datasource should have sorted the products based on the Display Sort Order field on the product.


Solution: Added a query plugin while retrieving products using the SOQL data source to sort them by the DisplaySortOrder__c field.


Module(s) impacted: Lightning Store


Community Hub $0 balance Carts can now be submitted.

Community Hub user were unable to process payments when the Cart has a $0 balance due to the user of a Coupon while Hosted Payment Forms is configured. (Known Issue ID-130546)


Your association may be affected if you:

    • Use Coupons
    • Use Hosted Payment Forms


Original System Design: Coupons should apply to cart items even when it is a 100% off coupon that leaves the car at $0 balance.


Solution: Added a check for the Cart balance amount, if the Cart balance is $0 the Submit button will render. The user should allow the Cart to process without entering payment information.


Module(s) impacted: Hosted Payment Forms, Coupons


Seasonal Permission Changes

See the Spring '23 Permission Changes in the Security section.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.