Hello.
We already have correspondence about this issue. What is the reason to create a topic again. I have mentioned that this will be improved in new versions of our products.
Regards.
I was giving you more info about the TRUE/FALSE, Yes/No, and 1/0 after more testing on my end.
Also, I wanted wordpress community members to know about the issue in case anyone else is struggling with it.
I have tested single check box with true/false and didn’t faced that issue. I will check again.
Regards.
Adam,
Thank you for pointing us to the issue. We will take a look to it as soon as possible.
There is an issue with using multiple attributes on import. You could use Terms ( taxonomy ) instead of multiple checkbox attribute. I believe, it would do the trick on import.
Also, try to use true/false instead of uppercased values TRUE/FALSE.
Regards.
@maxim I thought to use terms, but there is no way to do a multi-select search on terms on the front end. There is only the dropdown single select option with terms.
**I noticed on the All Apartments page in backend there is a way to choose multiple terms, but there is no equivalent for front end on website.
I’m using the field for bedrooms: Studio,1,2,3,4. I will need to allow the visitor to search 2 AND/OR 3 AND/OR 4, Studio AND/OR 1, etc.
Here’s what I’m thinking… If I change the Search Input and Data Entry to Free Text for this field it will import correctly. But, searching forces the user to type free text on front end which is not ideal. Should I do this for now, and when you push the update to fix multi-select I can change the search input from Free Text to Multi-Checkbox for this field or will that not work like I’m thinking?
Let me know.
Adam,
I think, you missed the option which allow you to use multi-select search for your terms on front end. Please, see: http://screencast.com/t/PZyxV9RI2qW
Regards.
Ok I see multiselect for front end now. The only problem I foresee with changing from an attribute to term is it will affect my property feed elements. I would prefer to use the attribute instead of term. I will mark this resolved after the next update corrects the import multi-select attribute behavior.
