We all D365 Developers came across this annoying error
often. Today, we will try to understand
this one and quickly resolve it if it appears next time.
When connecting to Dynamic CRM we are required a couple of
DLL’s which are
Microsoft.Crm.Sdk.Proxy : 9.0.0.0
Microsoft.Xrm.Sdk : 9.0.0.0
Microsoft.Xrm.Sdk.Deployment : 9.0.0.0
Microsoft.Xrm.Tooling.Connector : 3.0.0.0
Now these DLL’s must be in one common version only either
8.0.0.0 or 9.0.0.0. If any one of these DLLs is not synced version-wise, then during
runtime we have an error.
We can check the version of DLL’s from a property window
in Visual Studio.
Remove the wrong version of the DLL’s and add the correct
version of the DLL’s
Now the NuGet way, verify if you have the same
version installed.
Important Note: If you see the version of the NuGet same
and still, run into the problem, then Uninstall the NuGet and Clean and Re-Build
the solution or try verifying individual DLL’s version as explained above.
Here are some other links for Troubleshooting and learning:
Now we can use a single
lookup field to refer multiple entities for searching (including a custom entity)
A lookup value submitted will
be matched to a record in all the related entities.
Note: For now, to achieve
this it is possible only via SDK or Web APIs. Interactive user interface
support will be coming in a future release.
Example:
Let's say you are hosting
media for users in a library. You have many different MediaObjects, like
“Books”, “Audio”, and “Video”. Creating a multi-table lookup called “new_Media”
that has 1:M relationships to “new_Books”, “new_Audio”, and “new_Video” will
result in a “new_Media” lookup table that provides quick identifications of
records stored in specific tables.
Shown below
is an HTTP post to CREATE Multiple lookup attribute.
It will create three relationships as depicted below
image.
POST [Organization
URI]/api/data/v9.0/CreatePolymorphicLookupAttribute HTTP/1.1