Different Object Properties Based on Collections
Would it be possible to have different sets of properties based on collections? Now, that we have labels, which work so much easier for grouping (especially with the new Kanban view), I was thinking that collections would be perfect to define different sets of object properties. For example, the "Person" object is great, but I have customers, which will need a certain set of properties, for example, I have a URL for SalesForce here. I have other persons, like friends, who don't need a SalesForce link, but it would be great to have a birthday and anniversary date property, and perhaps a link field to other family members. However, my doctor, another "Person", won't need a SalesForce link, and probably not an anniversary date, either. I have a lot of these objects that have varying sets of properties and I wish I didn't have to carry all of the properties just to cater for one use-case.
I hope that makes sense. Ideally, there would be a "core" set of properties you set per object, and then a set of properties you set per collection.
1 Comment
Sign in to comment

Challenge:
My workaround:
App change proposals: