Clik here to view.
Tip #163: Create a 1:1 relationship
Creating a 1:N or N:1 relationship between two entities is very straightforward, but what if you want to do a 1:1 relationship? For example, say you have a subprocess that needs to be owned by a...
View ArticleClik here to view.
Tip #165: 1:1 with security twist
Usability of 1:1 relationships stretches far beyond UI candy. They can become a very useful tool that secures parts of the same logical record. For example, financial services company might use account...
View ArticleClik here to view.
Tip #303: Name your relationships
Scott “Captain Redlaces” Sewell reminds us to name our relationship display names responsibly. Say you have multiple contact lookups on the account form. If you go with the default naming for the...
View ArticleTip #1118: Ways To Link Accounts and Contacts
There is an on-going problem with most modern CRM systems which is the Account – Contact problem. In short, most CRMs assume a Contact belongs to just one Account and an Account has many Contacts....
View ArticleClik here to view.
Tip #1413: Components Required in the Solution for Relationship Mapping...
Today’s winner is Linn Zaw “I always” Win. And you can be one too if you email your tip to jar@crmtipoftheday.com! Have you ever added the 1:N or N:1 relationship into the solution, created new...
View Article
