Table of Contents

• How do I filter a report to show any rows with tag A or tag B?
• How do I filter a report to show any rows with tag A and tag B?
• How do I create a custom fields out of tags?

How do I filter a report to show any rows with tag A or tag B?

Many of the Easy Insight data sources include reporting against tagged data. In order to optimally report against these tags, we've added special handling for filtering of these tags to get the reports you need.

One scenario is that you have tags A, B, and C in your system. If you want the report to retain any rows with tag A *or* tag B, create a multi value filter on the tag field. For example, if you're reporting against Highrise contacts, create a filter against the Contact - Tags field. When prompted for filter type, choose Multiple Value. In the filter window that appears, drag the appropriate tags into the "Included" section of the window. The result will include any rows where one or more of the filtered tags are present.

How do I filter a report to show any rows with tag A and tag B?

As an alternative scenario, you might want to only show contacts with tag A *and* tag B. For this scenario, create two single value filters on the same tag field and set them to the appropriate tag values. From these filters, the report will filter down to only show rows containing *both* of the selected tags.

How do I create a custom fields out of tags?

Finally, you can actually create custom fields out of tags if you so desire. For example, let's say you have Highrise contacts tagged as A, B, C, and D in your data. You want one custom field to show A or B for a given contact, and a second custom field to show C or D for a given contact.

Start by going to the Data tab and clicking Create New Derived Grouping. Name the custom field as you want.

For the actual calculation string, you'll use the tags function. For our A/B example, we'd use the following calculation:

tags([Contact - Tags], "A", "B")

Upon saving the calculation, we can add it to the report as a custom field. From there, we can do the exact same thing with the C and D tags, creating another derived grouping, naming it, and putting in a calculation string of:

tags([Contact - Tags], "C", "D")

With that, we've created two distinct custom fields out of our tagged contents. The same functionality can be applied to any connection using tags, whether it's Highrise, Zendesk, or other data sources.