For example, there are only 6 custom string fields that we can map too, 3 decimal and 3 Integer.
This is a system table so we can't create more. Any plans to allow more fields per type? This came up w/ a customer in support.
New Idea
More than 6 custom string mappings in AO participants mapping
Is it on the roadmap to allow more than what is currently set up in the AO participants table for custom mapping?
For example, there are only 6 custom string fields that we can map too, 3 decimal and 3 Integer.
This is a system table so we can't create more. Any plans to allow more fields per type? This came up w/ a customer in support.
For example, there are only 6 custom string fields that we can map too, 3 decimal and 3 Integer.
This is a system table so we can't create more. Any plans to allow more fields per type? This came up w/ a customer in support.
Yup, this would be great. I am trying to provide a data-rich email to customers, thus I need data to pull in to tokens. Removing the limit or increasing would be great.
This goes for Date fields and other types also.
This goes for Date fields and other types also.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.