I was relying on the Queue Topic path to determine if a request was for Product A vs. Product B. However, some requests are getting sent down the wrong path and I'd rather not have the requestor re-enter the request. I'd like to set up a field indicating Product A or Product B and use that field for reporting rather than relying on Queue Topic. Is there a way to "pre-set" the field to Product A if it goes down the Product A path? But also be able to change it to Product B if it was sent down the wrong path?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
I doubt it but you can set custom forms based on topic. That could solve your problem by having a "Form A" and a "Form B". And you can also set up a form that shows certain fields if the user makes a specific choice on another field if you wanted a single form.
TIP: if this solved your problem, I invite you to consider marking it as a Correct Answer to help others who might also find it of use.
If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/mysocalledideas
Views
Replies
Total Likes
As far as I know, you can't set default answers per form though. So, Form A can't have Product A as the default choice in the "Product" field and Product B as the default choice in Form B. Default choices are set at the field level, and not at the Form level. If they could, that would have solved my issue.
Views
Replies
Total Likes
You would need to make a Product A field and a Product B field as radio buttons and hide any other choices. The user could then select the relevant one of them and leave the other alone, if you wanted a single form.
If you wanted 2 forms, you could preselect Product A on one of them and Product B on the other. Queue topic "Product A" would have "Form A",… etc.
Views
Replies
Total Likes
Views
Likes
Replies