[SOLVED] CB Conditional delete values in fields

I'm using a button radio field to show/hide diferent fields. It works, but when I hide the fields all their values go to empty. For example, I've an cb_country field (query dropdown field from a select in db) with a default value "Spain". At first it loads properly, with "Spain" inside. When I click "No" in the button, cb_country fields hides ok, and when I click "Yes" in the button, It shows again, but doesn't keep the default value. With other more simple fields (text field) I've the same problem.

How can I fix this, for keeping values when hide/show fields with conditional?

Thanks in advanced

Solved. I've realised that, in "plugins", the CB Conditional has an option to enable/disable reset or not to blank if condition is met.

After that, and with little changes in AND to OR conditional in updating to 5.0.0 all works.

Thanks indeed.

Is the option "Reset" in the conditional field plugin a new feature? I searched now for hours why some fields are deleted after saving a profile. Now I see, that the Reset-Button for "Reset field to blank if condition is not meet" is enabled. I never made this setting and the profile savings worked for month perfect. I have this problem since the last CB plugin update.
I think it would be good to set the default setting for this field on "disable".

No, it's not new. That parameter has existed since CB Conditional implemented value resetting something like a year ago. No, default of disabled does not make sense. A user doesn't have access to the field so it's supposed to be reset. If you disable resetting and you've 3 fields conditioned 1 after another the chain won't work anymore for example.

Thank you for quick response!

Ok, it´s "relatively" new.
I was not aware of this new feature. So I have to check the conditionals in detail. Now it makes a difference how I set conditionals:

Show field X if group A meets condition Y
or
Hide field X if group B not meets condition Y

The result of publishing/unpublishing the field is the same, but in one case the field will be reset and in one not.

If a condition is not met then the value is reset. If you don't want value resetting just disable it. It only negatively impacts condition chaining and if you're not chaining multiple conditions you don't have to use value resetting.