Share
ReportWe currently work with local governments and have a slightly complex need. Suppose you have a list of cities:
- New York
- San Francisco
- Houston
Each address in these cities has been specified as a certain type of property:
- Residential
- Commercial
- Agricultural
- Protected
- Wetlands
Each of these 'types' has identical fields:
- Existing Structure? Y/N
- Buildable? Y/N
- Minimum distance from building to edge of property?
- Total size?
Our issues lies with the fact that certain cities only have certain types, so while New York might have Residential and Commercial addresses, San Francisco might instead have Commercial and Protected. To make things more difficult, Commercial in San Franscisco may require at least 5 meters from a building to the edge of the property, but Commercial in New York might require 8 meters.
The initial idea was to create 2 separate entities, 'City' and 'Property Type'. The 'Property Type' would contain all fields needed, such as total size and existing structure, and an entry would be created for each property type for each city. However we are now doubting that this is the correct methodology to accomplish what we want, and still don't fully understand how to bind the City and Property Types. Our goal is to simply select those 2 lookups (City and Property Type) while on an opportunity, and then view the values stored in the Property Type fields.
Any guidance would be greatly appreciated!
All responses (
Answers (
550
