Adnan Al-Yassin

Current situation:

You do have Dynamics 365 for Outlook lightweight installed on your Outlook.

You received an e-mail from one of your CRM contacts.

You want to create a case for this contact.

The form auto-resolve the "Contact" filed based on the sender email address which is in this case a Contact. Please note that Contact field is not mandatory for case creation.

The "Customer" field is mandatory and you need to lookup for  CRM record (Contact or Account) to associate this with, it requires a parent record of the "Contact" field, hence an Account. Many customers do not use Account entity. and thus cannot create the case unless they do the following:

Empty the auto-resolved Contact field, go to the Customer field and lookup for the same CRM contact. Then in this case you may create the case.

This current situation is not practical for business based on customer service and to create cases all the time.

I tried so many things to remove the contact filed from the case form since it is not Business neither system required or recommended, however this field cannot be removed from the field because there is a padlock on it even thought it is not a required field. Today's Microsoft answer said, it is a read-only field.

I tried to disable the automatic resolution of the contact field but still did not help, it always automatically resolved base on the sender of the email.

This is not good at all.

Suggestion:

We need the tool to give the possibility to the end user to select whether they need to use the auto resolution or not for the contact field, like for example a check box where you enable the CRM for Outlook lightweight plug in. In this case if the customer disabled the auto resolution from the contact form then they will be able to directly lookup for the contact in the Customer field and this way they will save so many steps of the work around and manually emptying the contact field.

Thank you.

Dynamics 365 (Online) has a feature to establish a Hybride Server-Side Synchronization with an On-Premise Exchange server. This is a good idea but still however has a downside.

The downside is that Basic Authentication "on the exchange server" is a must in order to establish a successful communication between D365 online and Exchange On-Premise.

Many Exchange service provider do not easily accept allowing Basic Authentication because of security risks.

My suggestion is to have Dynamics 365 allows all authentication types available for Exchange server. This way, Exchange admins will not be obliged to change any settings on their server.

Thank you.

Hello,

I think I have submitted this idea before but it looks like is disappeared from the site. The oldest idea here I can see is 2 months ago while mine was few months (may be 6 or more months). Anyway I am resubmitting it here:

We are a Microsoft partner. We do have customers with Dynamics 365 for Financials among other licenses.

We do have delegated access (Unlicensed) to our customer's tenants.

When accessing Dynamics 365 online (CRM for example) our names as delegated admins are not stuck in the system and end users do not even see it unless they enable auditing.

With Dynamics 365 for Financials we see that our names as unlicensed delegated admins are stuck there among licensed user.

It would be nice if there is away to delete those users and even hide them as the purpose of the delegated admins is to help customer to troubleshoot or understand the problem.

Keeping those delegated admins in the list cause some confusion to the customer.

I hope it is clear.

Thank you.

Hello,

In Microsoft CRM 4.0 when you import data using the data import wizard there is a checkbox in the wizard that says: "Enrich data by updating existing records rather than creating new records", I think this feature benefits from the data duplicate rules to see whether the record exists or not then it will update the existing one if exists.

In Dynamics 365 online there is no such option. Instead, the user need to Export existing data then reimport etc... so that the second imported file will contain the GUIDS and based on that it will update.

My suggestion is to implement a similar checkbox as the one explained above that was available in CRM 4.0. This way is easier and more convenient than exporting and importing.

Thank you.