Open TracyLinder opened 3 years ago
If we want to populate Council District based on the Project Address, we will need to identify a spreadsheet of data either zipcodes, streets, or segments that belong to which District and update our Geo object accordingly. For reference, if we did by Segments, that would be about 65,000 records that would need to be updated. For zipcodes that is about 80 records. Streets would be somewhere in between. I think if we cant identify Districts by Zipcode this may be too heavy of a lift just to autopopulate the Council District.
This is probably not MVP. Discuss w/ Stakeholders.
@ChrispinP will you please add your notes about the possible solution & what that would involve?
Knack is capable of auto-populating fields on an application where users would enter the same information. Say for example a specific Job Application where all applicants are applying for the same position, we could pre-fill that position title.
Since Council District can change per applicant this solution would not apply. Therefore, the only reasonable solutions would be a mapping solution where we embed a map with a Council District layer where users can search by Address and choose their Council District or we use an Integration that associates a Council District with an Address that is entered.
Based on Chrispin's findings, and this not being identified as MVP by the stakeholders, this has been moved to the icebox.
We'd like the system to auto-select the council district based on the case location.