Static Conditions on already existing subscriptions and CB Fields and Dates to allow upgrades

I have dynamic conditions to show or hide child subscriptions on registration based on two cb fields that work great.

I would like the same child subscriptions to show as available upgrades for registered users when one or both of the cb fields are changed in a profile edit.

For example:

On registration, if a user selects "United States" from a drop down menu AND checks the box in response to the question, "Do you like the color Red?" the user is given the opportunity to purchase Child Subscription A.

On the other hand, if the user chooses "Canada" from the drop down menu and checks the box in response to the question, "Do you like the color Red?" they have the option of purchasing Child Subscription B.

If any user doesn't check that they like the color red when registering, then the only option they are given is to purchase the Parent Subscription.

If someone selected "United States" but does not check that they like the color red during registration, but checks the box on a profile edit, they are currently not given the option to purchase Child Subscription A. How can I give the user that option? Likewise with Canada and Child Subscription B.

I think I have tried every option given on the "Subscriptions upgrades workflows" and either everyone is given the option or nobody is given the option.

Currently the only way I can get this to work is to send an email with a link to the child plan's URL and very specific instruction to log in first, then click on the link. Any help would be appreciated.

You'll need to edit your child plans and ensure they're set to allow upgrades. Next on the Workflows tab you'll need to add your conditionals to "Static Conditions on already existing subscriptions and CB Fields and Dates to allow upgrades" parameter group to match your registration usage. That should allow it to work fine. The upgrade settings should be as follows.

Allow upgrade to this: Yes
Propose plan for upgrades only if it is more expensive: No (you'll condition it below)
Propose spontaneously plan for upgrades: Yes

First static condition: This condition must be met to allow upgrades

Next configure the conditional as needed based off your registration conditional.

Thank you for the quick response. I missed the conditional comparison, "Condition 1 (> for Dates):." Now that I am looking at it again, it seems like it should have been obvious.