Issues with fee fields which also depend on

Hi,
I'm running into issues with setting up "fee fields" which also "depend on" a selected list value.

I have a custom field list item.
If selection 'A' is chosen - a custom list item field should display - which is a fee field.
If selection 'B' is chosen - a different custom list item field should display - (or I could use a text field here) - which also is a fee field.

The depend on behavior works fine until I add the fee field settings.
As soon as I activate the fee field settings in the admin - the front-end depend on behavior no longer works as expected,
and in the back-end - my settings for the "Depend On Options" are no longer checked -
so I recheck the boxes - save - and again - the options are unchecked and the front end still not working.

Is it not possible to have a fee field depend on a list selection?
Are there known issues that would cause this behavior?
Any help would be appreciated.

Thanks,
Diane

Hi Diane

The problem is not with fee field. The problem is that at the moment, we only support one level of dependency. That mean we can only have field B depends on field A, not then field C depends on field B

In your case, seems you have two levels of dependency and that's the reason it doesn't work

This is something I will try to add support for in version 2.4.0 or 2.5.0 of Membership Pro

Regards,

Tuan

Hi Tuan,
Thanks for your reply.
Just to be clear - please confirm - whether or not the following is a second level of dependency :
There is a FIELD_A which has 2 options - OPTION_1 and OPTION_2.
If OPTION_1 is selected then FIELD_B is displayed.
If OPTION_2 is selected then FIELD_C is displayed.

Thanks,
Diane

Hi Diane

That's just still one level of dependency and should still work. Maybe you can submit a support ticket sending us super admin account of your site so that I can check it directly on your site?

Tuan

Hi Tuan,
The support ticket is now submitted.
Thanks,
Diane

Hi Diane

Replied you via support ticket. Could you please check and let me know if that's the reason of the error?

Tuan

Just relaying the what was determined to be the cause of the issue - for the benefit of the forum.
Commas were included in the list option values of the custom field which was the depend on field.
After removing the commas and also periods from the US currency values - the issue vanished - and all worked as expected.

Thanks to Tuan for the quick response and solution!

As mentioned via support ticket, I will try to add support for comma in the value in the near future. I will update you when it is implemented. For now, please remove the comma character as we discussed in the support ticket

Regards,

Tuan