Resolving Duplicate Lookup References in Import Process

Exploring Dynamics CRM

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

To resolve these types of records we need to make a small tweak before submitting the import job. Here we go

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 🙂

View original post

Add New (+) button behavior of sub grid in D365

While working with a sub-grid in D365, a question was thrown regarding behavior of Add record (plus) button. Many of you must have observed that for few sub-grids, click action of Add record button opens a new form to create a new record while for others a new line is added in sub-grid where one can add the record name and associate it. You might have figured the reason for this earlier but it was now that a college helped to figure out why it happens for me.

For those who were still looking for the reason of this behavior like me, this is all related to requirement level of the look-up field on child record. If Look-up is configured as business required then a new form is opened else the grid provides an inline row to associate the record. My assumption for this behavior is that if the look-up is business required, then it is assumed that all the existing records are already associated with some parent record thus user should create a new record. Always correct me if i’m wrong 🙂

Installing the latest version of Voice of the Customer (v 9.0.x.x)

@ramontebar

Last week I was running a new Dynamics 365 trial (v 8.2.1.289) 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 😉

View original post

[Workaround] CRM Workflow: Send Email Action – “From” field greyed out

Credit for the workaround goes to Chris Doran for sharing the solution on Dynamics Forum https://community.dynamics.com/crm/f/117/t/206486 

In some cases if the “From” field for “Send Email” step is disabled (mostly after 2016 update 1) which restricts sending emails from workflow, follow below steps.

 

It is a known issue with below workaround from MS Support.

  1. Create a new solution and add in the ‘from’ field from the email entity – just that nothing else from the email entity.
  2. Export the solution as an unmanaged solution.
  3. Edit customizations.xml and look for the line that says for “From” field. The tag is available for other lookups too (like created by) which should not be touched.            <LookupTypes />
    Replace that line with:
    <LookupTypes>
    <LookupType id=”00000000-0000-0000-0000-000000000000″>8</LookupType>
    <LookupType id=”00000000-0000-0000-0000-000000000000″>2020</LookupType>
    </LookupTypes>
  1. The attribute will look like this:
    <attribute PhysicalName=”from”>
    <Type>partylist</Type>
    <Name>from</Name>
    <LogicalName>from</LogicalName>
    <RequiredLevel>none</RequiredLevel>
    <DisplayMask>ValidForForm|ValidForGrid|RequiredForForm</DisplayMask>
    <ImeMode>auto</ImeMode>
    <ValidForUpdateApi>1</ValidForUpdateApi>
    <ValidForReadApi>1</ValidForReadApi>
    <ValidForCreateApi>1</ValidForCreateApi>
    <IsCustomField>0</IsCustomField>
    <IsAuditEnabled>1</IsAuditEnabled>
    <IsLogical>1</IsLogical>
    <IsSecured>0</IsSecured>
    <IntroducedVersion>5.0.0.0</IntroducedVersion>
    <SourceType>0</SourceType>
    <IsGlobalFilterEnabled>0</IsGlobalFilterEnabled>
    <IsSortableEnabled>0</IsSortableEnabled>
    <LookupStyle>single</LookupStyle>
    <LookupTypes>
    <LookupType id=”00000000-0000-0000-0000-000000000000″>8</LookupType>
    <LookupType id=”00000000-0000-0000-0000-000000000000″>2020</LookupType>
    </LookupTypes>
    <displaynames>
    <displayname description=”From” languagecode=”1033″ />
    </displaynames>
    <Descriptions>
    <Description description=”Enter the sender of the email.” languagecode=”1033″ />
    </Descriptions>
    </attribute>
  2. Put the new customizations.xml back in the solution zip file replacing the existing one.
  3. Import the solution back and publish.

 

“Next Stage” button do not set the stage as active in D365 BPF

While working with Business Process Flow in Dynamics 365, one of my colleague faced issue with “Next Stage” button. On clicking “Next Stage” on first stage, user is navigated to second stage but the second stage is not marked as Active. User is required to set it as active manually by clicking “Set Active” button.

BPF next stage issue

Upon checking found that it is a known issue in Dynamics 365. Background workflows related to the entity on which the BPF is configured are causing the issue.

The issue is expected to get resolved by July 2017. For now as a workaround, we are required to deactivate all the workflows related to the entity for which BPF is configured and activate them again. Second workaround is to convert the background workflows to real time workflows.

Details are available at below community link.

https://community.dynamics.com/enterprise/f/759/t/222616

Editing Sitemap in Dynamics 365

Work and Study book - Dynamics 365 (CRM) Blog

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).

XrmToolbox-Sitemap.png

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

Multi-Select Picklist control for Dynamics CRM by XrmForYou.com

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

via {New Utility} Multi-Select Picklist control for Dynamics CRM — Debajit’s Dynamic CRM Blog

Enhanced Business Rules in Dynamics 365 (Dynamics CRM)

Microsoft Dynamics 365

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:BS0.png

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” :

bst0Step 2:  Drag and drop desired component to right mark to perform that action if condition evaluates…

View original post 130 more words