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 mappings in the solution and deployment the solution to another environment only to find out that the mappings are not […]
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. Often this assumption is not valid. Common examples include medical practitioners, who work for a hospital, have their own practice […]
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 related entity navigation, this will create multiple navigation links with the same name. You might be able to get away with this in […]
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 entity to hold information about their customers but due to Chinese walls within the company, investment manager should not be able to access […]
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 different user than the account owner, or you have a child relationship where only one record should be associated […]
of the