A while back several community members gave me some great advice about how to associate a picklist field on a web-to-case form with Account IDs in SF. The use case was for students to self-serve their college info so we could track existing scholarships automatically.
That worked so well that now we are being asked to automate the application part of the scholarship process too. Leading me to this Q:
We want a student to be able to choose more than one scholarship offered in our community (among approx 100 total) to apply for on a single web-to-case form. Many students apply for more than one scholarship - perhaps up to 10.
When the Case record generated from this form arrives in SF, I want to write a Process / Flow that creates one record (probably Opportunity) per chosen scholarship. So if a student choose 10 scholarships on the webform, the automation would create 10 records.
We model scholarships as a custom object Fund, with a lookup field to Fund on Opp. Let's assume that all the scholarship Funds among which a student could choose are already existing records in SF, and that I want the record ID of each student-chosen scholarship Fund to arrive as a field on the Case.
Here's the Q: what type of field on the webform, associated with what data type of field on the Case record, would be most appropriate to use, so that a flow would be able to parse and loop through the chosen scholarships, create Opp records, and fill in the Fund field on each Opp record with the associated Fund ID?
Or is this just asking too much of Web To Case? I have been trying to avoid using a forms product like FormAssembly for cost savings, but have I gone as far as I can with an HTML web-to-case form?
