D365FO: application version dropdown is empty when creating new configuration for UDE envrionment

Microsoft released D365FO UDE environments long time ago, still they are barely used by partners and customers. There are many reasons for that, one of them is multiple bugs.

Several days ago I decided to try UDE one more time and created a new test environment. Besides challenges with environment creation, I was not able to save newly created "local XPP configuration". There were no options in the mandatory "Application version" dropdown, so the new configuration could not be saved.

When I moved mouse over the "Application version" dropdown, the hint appeared saying that there is no database backup for Cross Reference.

The solution was to go to "Tools" -> "Options -> "Power Platform Tools" and uncheck "Enable auto setup for Dynamics 365 when using the Unified environment."

Then use "Tools" -> "Download Dynamics 365 FinOps assets" to get the backup file. After this the "Application version" dropdown will be properly populated when creating new local XPP configuration.

D365FO: workflow editor could not be started

Several users reported the issue with D365FO workflow editor. During workflow editor startup the following error appears: "Application cannot be started. Contact the application vendor."

The fix is to open CMD as Admin, then execute the following command:

rundll32 dfshim CleanOnlineAppCache

D365FO: "Object reference not set to an instance of an object" error while updating 10.0.39 on local Hyper-V machine

There is a known issue when you try to update D365FO Hyper-V machine with 10.0.39 by installing new D365FO update. You may get "Object reference not set to an instance of an object" error during installation.

The solution is to run the following PowerShell code, then retry installation.

#set Dynamics Deployment folderpath in registry and create folder structure
$Installinfodir = "c:\Logs"
Write-Host "Checking InstallationInfoDirectry in registry for path $($Installinfodir)..." -foregroundcolor Yellow

if ((Get-ItemPropertyvalue HKLM:\SOFTWARE\Microsoft\Dynamics\Deployment -name InstallationInfoDirectory -ea 0) -ne $Installinfodir){
	write-host "Changing DynamicsDeployment folder path in registry to $($Installinfodir)..." -foregroundcolor yellow
	Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Dynamics\Deployment -Name InstallationInfoDirectory -Value $Installinfodir -Type String
}

@('HotfixInstallationRecords', 'MetadataModelInstallationRecords', 'Runbooks', 'ServiceModelInstallationRecords') |
    ForEach-Object {
    	if (!(test-path (Join-Path "$Installinfodir\InstallationRecords\" $_))){
        	New-Item (Join-Path "$Installinfodir\InstallationRecords\" $_) -ItemType Directory -force | out-null
	 }
}

More details here and here.

Windows RDP: error connecting to remote VM while using correct credentials

I was trying to connect to a remote VM running Windows Server 2019 with correct credentials, got the following error:

An authentication error has occurred.
The credentials supplied to the package were not recognized

Found the solution here: just add "AzureAD\" to the username.

D365FO: missing design elements in Financial Report Designer

Another possible issue with D365FO Financial Report Designer - missing design elements:

The solution is the following:

1. Open CMD prompt in Admin mode
   
   
2. Run the following command:
   rundll32 dfshim CleanOnlineAppCache
   
   
3. Relaunch Report Designer

D365FO: unable to run Financial Report Designer on 10.0.39

There is a bug in D365FO 10.0.39, impossible to open Financial Report Designer. The following error appears: "Unable to log in to <URL> or the login attempt has timed out. The application will exit."

The solution is to deploy latest D365FO quality update for 10.0.39 from LCS.

More details here.

SQL: SQL71626 error during DB export to a bacpac file

Few days ago I got the following error while trying to export SQL database to a bacpac file:

Connecting to database 'AXDB_copy' on server 'localhost'.

Extracting schema

Extracting schema from database

Resolving references in schema model

Validating schema model

Validating schema model for data package

Validating schema

*** Error exporting database:One or more unsupported elements were found in the schema used as part of a data package.

Error SQL71626: The element Certificate: [cert_name] is not supported in Microsoft Azure SQL Database v12.

The fix is to open SQL Management studio, create database copy, expand "

<myDBcopy> -> Security -> Certificates" and delete all certificates. After this export copied database to a bacpac file.