Recently, I ran across a new ( to me ) data type called "name/value pairs". I'm find lots of uses for this type of field and now I'm analyzing the benefit/costs of using it. For those not familiar with this type of field, it allows you to dynamically define a set of name/value pairs and store them in the field. I'm really liking it to store configuration data for automation purposes. Now that I have a table with a "name/value pairs" data type, I was able to import data into it. Now I'm wondering how useful the field is for reference purposes. I'm finding that the field is no amenable to filters or reporting. Has anyone figured this part of it out?
