I’m quite new here and I’m struggling to understand if I should use a Property or an Association Label.
We’re associating Contacts and a Custom Object called Projects.
A contact works on many projects but has the same role in them (For example, Developer, PM). Our goal is to use this Role in reports, so we can measure different things.
My question is: Should I create a Contact property called Project Role, or in this case should I use the Association Label. By reading the documentation I still don’t understand if there might be any long-term consequences of using one or the other?
If in this case contacts could have more than one role for each project, I would definetly go for an association label (for example I can be PM in one project and QA Engineer on other), but in this case I’m not entirely sure which should I go for.
My gut was telling me the same, so thanks for confirming!
Only one last question: can you think of any downsides (if any) of having association labels instead of properties? My reporting needs are met with both, but just wanted to check.
I don’t see one; you can build lists from association labels, which will allow you to take actions as well like enrolling them into workflows based on their “roles” etc.
Im working through a similar devision on a similar role issue. I’m struggling to find directions of creating an Active List for association label. Might you point me towards it if you know? Thanks in advance!
