Karen Maslowski confirmed that: "Custom table fields and custom record types (listed as Aha! record relationships in the custom fields section) are not available for use in the ideas portal."
We use a custom table field for tracking our customers and would like to incorporate it into our Ideas, so we can track which clients have requested which enhancements.
It is now possible to include many-to-many custom table fields in ideas portals and ideas portal forms. This article includes details on how to setup custom fields for your ideas portals.
custom tables serve no need if we cant use them on portals to submit requests on behalf of a customer
Hi Austin and Tony: our firm also has the exact same need as Tony Lopez's. We internal account managers who need to be able specify which customers/clients are requesting an idea in the Ideas Portals and Forms. My email chain with Keith Davenport from Aha Support attached for reference. Thanks!
We are really hoping to see this ability released asap as it would help teams capture information from a requester in a table format that will not clutter our ideas custom field list.
This would be great for our internal access requests, too. I was thinking of adding fields to them so I know if they have received training, ID as a champion, etc.
Voted. Planning to implement. ETA?
this would be good. ETA?
Hi Austin,
Thanks for the quick response. We're only using a internal Idea portal today. Our Account Managers accept enhancements on behalf of our clients and enter those the enhancements. We'd like to give our Account Managers access to specify which client requested the enhancement, and have the client flow through to the Feature/Master Feature.
If we launch a public Idea portal in the future, we would hide the client field for the concerns you outlined below.
Hi Tony, custom tables can be added to ideas within Aha! but not to portals or forms. Can you help us understand your use case a bit better? Would you want customers to be able to select themselves from the ideas form when submitting the idea? The issue with this is that they would also see any other customers in the table as well. For now I will mark this as unlikely to implement but please let us know more details so we can better understand the use case. Thanks!