I am building a manufacturer website that is using extra fields (EF) to show specific info on each product. There are hundreds of categories of products. I was creating an EF group per category but then realized that if a EF is left empty then it will not display on the front end.
I also was having to create duplicate EFs like "Diameter" and then associate it with a EF group for that category. So far I have 11 "Diameter" EFs for 11 EF groups. The site has 77 EFs but only 20 unique EFs, then rest are duplicates. (Feature Request: Be able to assign one EF to multiple EF groups)
So I figure, I could just put all 200+ EFs into one EF group. The manufacturer would just fill in the appropriate EFs and ignore the EFs that do not apply to that particular category of items.
It appears that Extra Field Groups are only to reduce the number of Extra Fields listed in the k2 item extra field tab.
So my question is why would I want to create multiple EF groups?
I also was having to create duplicate EFs like "Diameter" and then associate it with a EF group for that category. So far I have 11 "Diameter" EFs for 11 EF groups. The site has 77 EFs but only 20 unique EFs, then rest are duplicates. (Feature Request: Be able to assign one EF to multiple EF groups)
So I figure, I could just put all 200+ EFs into one EF group. The manufacturer would just fill in the appropriate EFs and ignore the EFs that do not apply to that particular category of items.
It appears that Extra Field Groups are only to reduce the number of Extra Fields listed in the k2 item extra field tab.
So my question is why would I want to create multiple EF groups?