Microsoft Dynamics 365 Global Administrator Unable to Approve Mailbox for CRM User

Hi Everyone,

Recently one of my client tenant had an issue:

Scenario: Microsoft Dynamics 365 Customer Engagement Application have only one License and one Global Administrator.

So there is a requirement to integrate Microsoft Dynamics 365 with Microsoft Dynamics 365 App for Outlook.

Microsoft Dynamics 365 Customer Engagement user(System Administrator) tried to approve email, test and enable mailbox, but the
                    "Incoming Email Status =  Fail",
                    "Outgoing Email Status =  Fail",
          "Appointment,Contacts and Task Status = Fail",

So as a tenant Global Administrator tried to approve the Mailbox for the user, but because the Dynamics 365 license has not been assigned  for Global Administrator, the Application is throughing error..

"Insufficient permissions to approve mailbox".

So there is a work around for this issue..

The system administrator himself assign the Global Administrator rights and obviously he had Microsoft Dynamics 365 User License.

Then the system administrator became a Global Administrator with Microsoft Dynamics 365 License and he should be able to approve the Mailbox for the user..

As you can see the Incoming Email Status = Success, Outcoming Email Status = Success, Appointment, Contacts and Task Status = Success.

The system Administrator can install Microsoft Dynamics 365 App for Outlook and sync the email contacts, leads and tasks with outlook.

I hope this helps..

 SMB'S  and Enterprise Customers requires Support/Development/one off project
Contact us @ www.gmritsolutions.co.uk
Email :           admin@gmritsolutions.co.uk

Javascript Deprecated in Dynamics 365

Hello Everyone,

The following information is handy for developer when customizing Dynamics 365 with Javascript.

The following client APIs are Deprecated in the current release to reorganize the Xrm client, so replacement client API need to be used and the Deprecated Client APIs are continue to be supported unless the Microsoft issue the time limit to replace with new Client APIs

Deprecated:

Xrm.Page

Xrm.Page.context

Xrm.Page.context.getQueryStringParameters

Xrm.Page.context.getTimeZoneOffsetMinutes

Xrm.Page.context.getUserId

Xrm.Page.context.getUserLcid

Xrm.Page.context.getUserName

Xrm.Page.context.getIsAutoSaveEnabled

Xrm.Page.context.getOrgLcid

Xrm.Page.context.getOrgLcid

Xrm.Page.context.getOrgUniqueName

Xrm.Page.data.entity.getDataXml

GridRow.getData

GridRowData.getEntity

Xrm.Mobile.offline

parent.Xrm

addOnKeyPress

removeOnKeyPress

showAutoComplete

hideAutoComplete

Xrm.Utility.alertDialog

Xrm.Utility.confirmDialog

Xrm.Utility.isActivityType

Xrm.Utility.openEntityForm

Xrm.Utility.openQuickCreate

Xrm.Utility.openWebResource

For the replacement of the Xrm Client APIs please refer to Microsoft document
https://docs.microsoft.com/en-us/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#some-client-apis-are-deprecated

I hope this helps..
SMB's Enterprise customers, if you need help on project/support/training/licenses, please contact us
www.gmritsolutions.co.uk
email: admin@gmritsolutions.co.uk

Microsoft Dynamics 365 SDK download using Powershell

Hello Everyone,

Normally we download the Microsoft dynamics CRM SDK from Microsoft  website until Microsoft Dynamics 365 version 9.0.

From Version 9.0 we have two options to download the SDK

1) Using the visual studio Nuget package manager



2)  using the Powershell:

I am gonna show how  to download it on to the local folder.

First create a folder in your local computer
Drive : D
Folder: Tool

So the path would be D:/Tools

Search for the "Powershell" on your computer start menu..
Change the directory to desired directory using cd..
  cd D:\Tools

Copy the powershell script from Microsoft website

$sourceNugetExe = "https://dist.nuget.org/win-x86-commandline/latest/nuget.exe"
$targetNugetExe = ".\nuget.exe"
Remove-Item .\Tools -Force -Recurse -ErrorAction Ignore
Invoke-WebRequest $sourceNugetExe -OutFile $targetNugetExe
Set-Alias nuget $targetNugetExe -Scope Global -Verbose

##
##Download Plugin Registration Tool
##
./nuget install Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool -O .\Tools
md .\Tools\PluginRegistration
$prtFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.'}
move .\Tools\$prtFolder\tools\*.* .\Tools\PluginRegistration
Remove-Item .\Tools\$prtFolder -Force -Recurse

##
##Download CoreTools
##
./nuget install  Microsoft.CrmSdk.CoreTools -O .\Tools
md .\Tools\CoreTools
$coreToolsFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.CoreTools.'}
move .\Tools\$coreToolsFolder\content\bin\coretools\*.* .\Tools\CoreTools
Remove-Item .\Tools\$coreToolsFolder -Force -Recurse

##
##Download Configuration Migration
##
./nuget install  Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf -O .\Tools
md .\Tools\ConfigurationMigration
$configMigFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf.'}
move .\Tools\$configMigFolder\tools\*.* .\Tools\ConfigurationMigration
Remove-Item .\Tools\$configMigFolder -Force -Recurse

##
##Download Package Deployer
##
./nuget install  Microsoft.CrmSdk.XrmTooling.PackageDeployment.WPF -O .\Tools
md .\Tools\PackageDeployment
$pdFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf.'}
move .\Tools\$pdFolder\tools\*.* .\Tools\PackageDeployment
Remove-Item .\Tools\$pdFolder -Force -Recurse

##
##Remove NuGet.exe
##
Remove-Item nuget.exe

Then you can see on the screen shot SDK will be downloaded to the local folder:

As you can see the plugin registration tool, package deployment, CoreTools, ConfigurationMigration folder from  the image.

Then you start using the SDK for the development work.

I hope this helps..

SMB's and Enterprise Customers need of Support/Development/Consultancy/Licenses 

Contact us 

www.gmritsolutions.co.uk

Email: admin@gmritsolutions.co.uk