[NO, some field types are compatible] Will changing field type corrupt values?

More
9 years 1 month ago - 9 years 1 month ago #58421 by kath
hi there,

[i have a question]
If I change the type of a field, will I loose or corrupt values that were already input?

[in more detail]
My live-site has a field of type 'checkbox'. current config is: 1::yes%% .
Problem: Client needs category-page with filtering; filtering needs to offer 'any', 'yes', 'no'.
But current filter on category-page is set to 'dropdown-selector' and of course only offers 'any' and 'yes'.

Although I assume, that changing my checkbox into a radiobuttons-group with a config like: 1::yes%%0::no%% would work, but now above question arises: "Will that do something bad to my data?"

Thank you a lot and sorry for this lengthy question :)
Kath
Last edit: 9 years 1 month ago by ggppdk.

Please Log in or Create an account to join the conversation.

More
9 years 1 month ago #58422 by ggppdk
Hello

changing field type will
- maintain all common paramaters (e.g. "Required")
- also the fields have compatible values:
select, selectmultiple
radio, radioimage
checkbox, checkboximage

* but note that adding / removing into a fieldgroup: selectmultiple, checkbox, checkboximage into a fieldgroup, will distribute their values across the fieldgroups

so you can change the fieldtype without problem,
just in your case you may not need to change the field type ??
- the way that the field's filter is displayed is another parameter inside the "Filtering" TAB


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

More
9 years 1 month ago #58425 by kath
first, thanks for your lightning-fast reply! :)

>> the way that the field's filter is displayed is another parameter inside the "Filtering" TAB
yes, but in my case I seem to have a discrepancy between field editing and filtering:
- editing currently allows 'yes' or ~no checkbox checked.
- filtering currently allows 'any' or 'yes'.
In other words: I can't filter what my field doesn't know about, right?

- filtering should allow 'any', 'yes' and 'no'.
My approach would be to add 'no' to the field's editing config, making it necessary to change it's type to radiobuttons (client doesn't like dropdown).
Or are you saying there is a way to interpret '~no checkbox checked' (in editing) as 'no' in the filters, while still telling the difference from 'any'?

Please Log in or Create an account to join the conversation.

Moderators: vistamediajoomlacornerggppdk
Time to create page: 0.671 seconds
Save
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Essential
These cookies are needed to make the website work correctly. You can not disable them.
Display
Accept
Analytics
Tools used to analyze the data to measure the effectiveness of a website and to understand how it works.
Google Analytics
Accept
Decline