Tip #1413: Components Required in the Solution for Relationship Mapping Deployment

Three bowls with fresh blackberries, raspberries and blueberries symbolizing the components (of a dessert)

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 […]

Tip #1166: Dynamic Help now included in Solutions errors

Life buoy, fire alarm

Troubleshooting solution errors has always been either somewhat a guessing game or painful tracking of the solution dependencies. I’m sure they are not fun to deal with for Microsoft support either. Dana Martens, Supportability Program Manager at Microsoft, has some good news about Dynamic help. Yes, Dynamic not Dynamics. Read on. The Solutions feature team […]

Tip #897: Alternate key, duplicate data, and solutions: part 2

Alternate key

The alternate key saga did attract some attention and we received the definite say from Brandon Simons, who’s probably as close to the proverbial Dynamics 365 metal as it gets. tl;dr Alternate keys can be in an inactive state when the definition is created but the unique index is not. These pending keys can be […]

Tip #894: Alternate key, duplicate data, and solutions

Duplicate key

tl;dr If you have duplicate values present in a field, creating alternate key on that field will fail. However, when a solution that includes alternate key is imported into the deployment where duplicates are present, the import does not fail and completes with the warning indicating that alternate key was not created. Long story Not […]

Tip #857: Missing component id {0} error when publishing customizations

Today’s tip comes from Daryl “Always Raising” LaBar. (And you can submit your tips too by emailing them to jar@crmtipoftheday.com.) I recently had the issue described here when publishing customizations. It results in the error message “There was an error calculating dependencies for this component. Missing component id {0}.” In case anyone hits this error… it […]