This article captures the maximum attribute name lengths allowed in Dynamics 365 (CRM). This is a simple thing but I carry on forgetting it and it is useful to have them always in mind.
- Attribute Display Name max length = 50 characters
- Attribute Unique Name max length = 41 characters
- Attribute Description max length = 200 characters
- Attribute Form Label max length = 100 characters
See below the corresponding screenshots locating those elements:
Normally when we import records which has a related entity, import process will resolve the lookup reference if it finds single record in the parent entity otherwise, it will stop processing the record and ends in fail.
Ex: When we are importing a Contact (Contact1) with Parent Account (Account1) and system has two accounts with same name then Import process gives error when processing Contact1
Click on Edit in the mapping dialog
Go to Parent Account field in the list of mappings and click on Lookup
Set the unique field as the reference
Now in the import file add the data as Account Number for Parent Account field.
Hope this helps 🙂
Last week I was running a new Dynamics 365 trial (v 18.104.22.1689) and I wanted to use the Voice of the Customer module.
Based on the previous versions of this solution (v.8.x.x.x), I followed the same steps that I used to: Office 365 => Dynamics 365 Admin Portal => INSTANCES => Solutions, see below screenshot:
However, when I tried to install it from this Solutions section, the installation process just failed once and again.
After a quick call with Microsoft Support, they told me the new installation process at the APPLICATIONS tab, see below screenshot:
Once you are there, just click on MANAGE and follow the next few steps choosing your corresponding instance (whose version needs to be >=8.2). Then you can track again the installation process in the Solutions section:
Hope this saves you some time 😉
Prior to the release of Dynamics 365, we are helped a lot by XrmToolbox to edit the sitemap without the need of editing the sitemap XML manually. However, with the release of Dynamics 365, it seems the plugin for XrmToolbox doesn’t support the editing of Dynamics 365 sitemap (given now it is possible for a Dynamics 365 deployment to have multiple Apps and each App can have their own sitemap).
So, what should we do now? There are 2 options to configure the Sitemap in Dynamics 365.
Option #1: Creating a new App
With the ability to create App in Dynamics 365, we can create a sitemap that is associated to the App. Following the guide from Microsoft on how to configure/design the app: https://www.microsoft.com/en-us/dynamics/crm-customer-center/design-custom-business-apps-by-using-the-app-designer.aspx
Option #2: Editing the Default Sitemap
Editing default sitemap is similar to what we used to do with XrmToolbox. However, with the unavailability of XrmToolbox…
View original post 151 more words
Very happy new year to all of my blog readers. This is my first post of the year and it could not have started in a better way. I am delighted to announce the new “Multi-Select Picklist control” from XrmForYou.com tools library. Showing a picklist attribute as multi-select is a requirement we get every now […]
Enhanced Business Rules in Dynamics 365 (Dynamics CRM)
There have been many changes in Dynamics CRM with release of Dynamics 365.
Business rule is one among those having major changes in after first introduced in Dynamics CRM 2013.
Business rules got new GUI (graphical user interface) to make it easier to understand and create a new Business Rule:
A new action added in this update is “recommendation” i.e. we can add recommendation to any field so that system suggest you to fill/select something specific.
We have created a test Business rule on case entity:
Task: If origin of case is “phone call” make “contact” field business required otherwise make it non-business required:
Step 1: Set condition in properties window in left right side.
In our case it’s if on entity case, field “origin” have value “phone call” :
Step 2: Drag and drop desired component to right mark to perform that action if condition evaluates…
View original post 130 more words
Microsoft Dynamics CRM 2016 Update 1 brings Email Signatures as an out of the box functionality. They can be used on Users or Queues (based on Teams).
Create a new email and you will see a new icon on the email designer to insert signatures:
To create more signatures, go to Personal Settings or, as an admin, Administration => Templates section.
Administration => Templates:
Notice Email Signatures is a new entity and it is part of the security roles. So, for instance, if the Customer Service Team requires to use Email Signatures, they should have access to the Email Signature Entity. See below an example security role:
Note: My current on-line build version is : 22.214.171.1242 – DB 126.96.36.1999
You can find more information in the following Microsoft CRM article: