Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Created by Guest
Created on Nov 2, 2022

Taxonomy Hierarchy

Our taxonomy is very big - some labels could have thousands of options. We'd like a better way to organize it, as there is a hierarchy to the way things fit into verticals, product lines, products, etc.

We want to ensure users only see relevant values. For example:
If the top level label has values of "pets/wild animals" a user picks "pets", then we want to show them "cats/dogs" (and not allow them to pick from the list "elephant/lion"). Next, if they pick "dogs", then we want to show them "husky/pug" (and not show them "ragdoll/shorthair").

  • Guest
    Reply
    |
    Mar 10, 2023

    Along this same notion is the ability to use logic when identifying the metadata fields on the campaign records that will be inherited onto the tasks and ultimately the asset, like we can on Form Templates. I want to use metadata-driven rules to display select values of a given metadata field depenent on other metadata choices made.


    And to put icing on the cake, would be the ability to identify default values in the Form templates like you can when identifying the fields on a campaign.