Details about this thread
  • State Not Answered
  • Replies 1 reply
  • Subscribers 322 subscribers
  • Views 56 views
  • Users 0 members are here
Related content from around SugarClub

Multi-select from massive dropdown or use related module?

Lisa Marten

I need some help thinking through how we can make something work. Basically, we use Opportunities like subscriptions, and each subscription is linked to an Account. Some of those Accounts are school districts and they have multiple schools that are part of that subscription (one Account/district, one Opportunity/subscription, multiple schools). Right now we just use notes fields, but we want to make it more obvious which schools are subscribing by having some sort of multi-select or related module. We are talking about ~450 districts (Accounts) and over 2000 schools (some districts have just 1 or two schools, others have over 30 schools). 

We would need to be able to copy over the list of schools when we duplicate the Opportunity record (both from the individual record AND while importing). We also need the schools that are linked to the Opportunity to appear on a PDF. 

I like a multi-select idea because I think we can make it appear in paragraph form, separated by commas (Elementary School, Middle School, High School) as opposed to a list (which would make an insane PDF for the ones with many schools). However I realize that would be a crazy dropdown/dependency. Another thought is to create a new module for the schools. Would there be a way to bring a list of those linked schools up into a field in the Opportunity module? Would we be able to carry those linked schools over when duplicating/importing?

Is there an easy way to do this or something I'm not thinking of?

Parents
  • 0

    Instead of creating another module for Schools you could leverage your Accounts module:

    You could add a qualifier for "Account Type" with two values: "School" and "District", then use the existing parent/child relationship to define which Schools are in the District by making the appropriate District the parent of the School.

    On your Opportunity the Account will be the District, and you can then develop a way to populate the names of the schools into a "Schools List" text field to use for the PDF, I would opt for a logic hook (I've not played with BPM but that maybe that could do the job?)


    There is also some work  did for populating and enum (dropdown) from an API call, which might give you an option to select one or more names of "Schools" related to the "District" in a multi-select on the Opportunity; I would need to think that through a bit more though as I'm not familiar with André's code and I am not sure how you would then concat multiselect values into one field in the PDF...

    FrancescaS

Reply
  • 0

    Instead of creating another module for Schools you could leverage your Accounts module:

    You could add a qualifier for "Account Type" with two values: "School" and "District", then use the existing parent/child relationship to define which Schools are in the District by making the appropriate District the parent of the School.

    On your Opportunity the Account will be the District, and you can then develop a way to populate the names of the schools into a "Schools List" text field to use for the PDF, I would opt for a logic hook (I've not played with BPM but that maybe that could do the job?)


    There is also some work  did for populating and enum (dropdown) from an API call, which might give you an option to select one or more names of "Schools" related to the "District" in a multi-select on the Opportunity; I would need to think that through a bit more though as I'm not familiar with André's code and I am not sure how you would then concat multiselect values into one field in the PDF...

    FrancescaS

Children
No Data