Understand Custom Field Snapshots and Historical Values

Understand how QCMM stores Custom Field values and policy with each subscription so historical purchases remain independent of later field and Plan changes.

The Subscription Is the Value Context

QCMM stores Custom Field values against the exact subscription, not as one global Joomla user profile. Two memberships owned by the same user can therefore hold different values for the same field key.

What Is Snapshotted

Each saved value records the field key, label, type, normalized value/display value, whether the customer entered it, customer visibility, Member Area editability, maximum Repeating Text entries, and ordering. Admin Only fields can be snapshotted blank at purchase for later fulfillment.

Later Definition Changes

Historical values are preservation-first. Removing a field assignment from a Plan does not erase the subscription value. A field added later is not silently injected into an old subscription’s fulfillment layout. Retired/unpublished definitions and old option keys can remain meaningful to history rather than being repurposed.

Plan Reassignment Is Explicit

When an administrator legitimately moves an eligible subscription to another Plan, QCMM uses a reconciliation workflow: matching field keys can be rebound to the target Plan policy, new target fields can receive blank snapshots, and old-Plan-only values are preserved as historical data instead of being discarded.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.