It gets a bit funnier when after the restore I get the message :

D365FO : You are not authorized to login with your current credentials. You will be redirected to the login page in a few seconds.

Me: Do you realize I am an administrator ? In fact, I deployed this environment so I need access now !!!

Well, few things to do.

• Run the Reset-DatabaseUsers.ps1 script in the infrastructure folder

.\Reset-DatabaseUsers.ps1 -DatabaseServer ‘<FQDN of the SQL server>’ -DatabaseName ‘<AX database name>’.

• Update the networkdomain to the adfs federation service name https://fsn.contoso.com/adfs.

Replace the portions in bold based on your environment.

Once DB Sync is completed successfully , Happy on-premising :D.

The post Cannot Login after database refresh dynamics 365 FO on Premise appeared first on Monsieur Winner.

This is because the “documents” folder in the file server is missing.

Go to aos-storage and create a new folder “documents” and you should be fine.

The post Document failed to upload. Please try to upload the document again D365FO on premises appeared first on Monsieur Winner.

This error occurs when the local agent tries to download the package from LCS. This file is saved in the fileshare VM.

When the fileshareLocation  value is different what is specified in the localagent-config.json is different from FileShare path in ConfigTemplate.xml,

I am happy to tell you that you just successfully landed yourself a bonus error.

The post Unable to get file endpoint, the network name cannot be found – D365FO on-premises appeared first on Monsieur Winner.

To set your custom model as default, go to

C:\Users\XYZ\Documents\Visual Studio Dynamics 365

Edit the DynamicsDevConfig file.

<DefaultModelForNewProjects>FleetManagement</DefaultModelForNewProjects>

Change FleetManagement to your custom model.

The post Default model for new projects in Visual studio D365FO appeared first on Monsieur Winner.

Why use the active method ?

We want to show record in a particular field on a grid when a record is selected.

In my case, we want to display the Department code on Positions:

Human resources -> Positions -> All positions.

The business scenario here is, the human resources officer is more familiar with the Department code. To achieve this, we can add a new field and assign the department code on selection of the record.

Let’s create a class: A form event handler for HcmPosition form.

internal final class HcmPosition_Form_GEMS_Handler
{

}

internal final class HcmPosition_Form_GEMS_Handler
{
 /// <summary>
 ///
 /// </summary>
 /// <param name="sender"></param>
 /// <param name="e"></param>
 [FormDataSourceEventHandler(formDataSourceStr(HcmPosition, HcmPositionDetail), FormDataSourceEventType::Activated)]
 public static void HcmPositionDetail_OnActivated(FormDataSource sender, FormDataSourceEventArgs e)
 {
   FormRun form = sender.formRun();
   FormDataSource HcmPositionDetail_ds = form.dataSource(formDataSourceStr(HcmPosition, HcmPositionDetail)) as FormDataSource;
   HcmPositionDetail hcmPositionDetail = HcmPositionDetail_ds.cursor();
   OMOperatingUnit operatingUnit;

   select operatingUnit where operatingUnit.RecId == hcmPositionDetail.Department;

   hcmPositionDetail.OMOperatingUnitNumber = operatingUnit.OMOperatingUnitNumber;
 }

}

The post OnActivated form method EventHandler X++ D365FO appeared first on Monsieur Winner.

Warning tells me that my new D365FO environment is fine, however some automated setup are not completed in Azure DevOps.

Script [Run-CommandALMServiceInstallALM] failed execution against VM [XXXX]. Last Result: 0xA01604AF (An error occurred during the build environment setup process. Error details: ALM service model configuration failed. Configuration has 2 errors:
[1] BuildEnvironmentReadiness: PowerShell DSC resource MSFT_ScriptResource failed to execute Set-TargetResource functionality with error message: {“$id”:”1″,”innerException”:null,”message”:”The classic pipelines are disabled for this project / organization.”,”typeName”:”System.InvalidOperationException, mscorlib, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″,”typeKey”:”InvalidOperationException”,”errorCode”:0,”eventId”:0}
[2] AddTrustedTestCertificateToWifConfig: Could not reach desired state. [One or more dependencies may have failed.])

The first error made sense when we check the Azure DevOps project. I discovered that Disable creation of classic build pipelines was turned on.

During the deployment of a new Build environment, a build agent and a classic build pipeline are created/imported. So disabling creation of classic pipeline will surely result into error.

The post D365FO Cloud hosted environment deployment warning 95017 appeared first on Monsieur Winner.

Prerequisites:

According to the Microsoft learn,

1 . You must be running Supply Chain Management 10.0.34 or later. – My environment is on 10.0.37 so I gat no worries.

2 . On feature management turn on : Review changes to confirmed purchase orders based on downstream impact. This is enabled by default on version 26 and later

3 . Enable the SQL row version change tracking license key.

Firstly put the environment on Maintenance mode on LCS then navigate to the License Configuration windows following the path on the screenshot below:

4 . Upgrade the Finance and Operations Virtual Entity solution

We need to update the mentioned solution on the powerplatform by logging to Power Platform admin center.

1. Go to Power Platform admin center.
2. Select the Power Platform environment that’s connected to your finance and operations app, and open the detail view.
3. In the Resources field, select Dynamics 365 apps.
4. Find the app that’s named Finance and Operations Virtual Entity.
5. If the status is Installed, you’re already running the latest version. If the status is Update available, you must update the solution by following these steps:
   1. Select the ellipsis button (…), and then select Update.
   2. Accept the terms of service, and then select Update.

5 . Install the Copilot application in Supply Chain Management on PowerPlatform environment.

6 . Enable required security roles in Dataverse.

The procurement officer needs to have some access on the dataverse : The AIB Roles and Finance and Operations AI security roles in Dataverse.

Sigh! Now that we have done all the setup , let’s move to Dynamics Finance and Operations App to see how the copilot interacts with the procurement module to make the job much more easier for a purchasing manager or a Buyer.

Let’s head to our new found love, the Confirmed purchase orders with changes workspace.

One of the likely challenge companies into sales, production face is when purchase orders have been confirmed and dependent sales order or production orders have been created and the vendor comes back with changes. It could be that the vendor will not be able to deliver the exact quantity or the delivery date would have to change. You will agree with me that, it will impact on the business. To have a better view of these changes, the developer would create some reports that both sales, purchasing department have to analyze these data.

The new workspace with copilot will not only identify these Confirmed purchases with changes, but it also classify them by the severity of impact; low or high on downstream orders.

• Low impact changes – This tile highlights changes to purchase orders that have no known impact on downstream orders that have been created by planning, also called pegged orders. A summary of changes is generated to help you review and validate the purchase orders.
• High impact changes – This tile highlights purchase orders that have known downstream impacts on pegged orders. These high-risk changes are summarized together with the detected impacts, to help you investigate further and decide what action to take.
• Impacted downstream orders – This tile summarizes impacts on pegged orders by the number and type of orders, and it shows the purchase order changes that cause each impact. This information helps you review potential downstream impacts based on the latest master planning run.

Order with low impacts can be confirmed since we can deal with the changes.

To disagree or communicate the impact of these changes to the vendor, copilot can easily help with a text or an email that can be sent by just clicking the Send Email button.

And the email is auto generated with the vendor’s email address as the recipient.

Copilot intelligently suggest a format with the number of lines on the Purchase order and you could easily modify before sending out.

Preparing to demo this new feature to our existing customer has been a great experience.

We hope to see such coming in Dynamics Finance which set to be generally available in early 2024.

https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/collectionscoordinatorsummary?WT.mc_id=DX-MVP-5005271

https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/collectionsworkspace?WT.mc_id=DX-MVP-5005271

The post Copilot in supply chain – Dynamics 365 Finance and Operations appeared first on Monsieur Winner.

missing prvReadmsdyn_paymentschedule privilege (Id=59c99a27-eae9-49e1-8204-e28e3600139f) on OTC=11187 for entity ‘msdyn_paymentschedule’ (LocalizedName=’Payment Schedule’) in Business Unit: (Id=699a433e-f36b-1410-81cd-00c87dfd4262). context.Caller=987b2374-02d9-ed11-a7c7-0022489ae673. Consider adding missed privilege to one of the principal (user/team) roles.

Locate the team with the id shown in the error, (709a433e-f36b-1410-81cd-00c87dfd4262) in my case and assign the system administrator right on Dynamics D354/CE

This will resolve the missing privilege for entity ‘msdyn_paymentschedule’ error.

That’s it! You should be free like a bird.

The post Dual write error – missing prvReadmsdyn_paymentschedule privilege for entity ‘msdyn_paymentschedule’ appeared first on Monsieur Winner.

Using dual write recently, we had cause to create custom entities on Both CE and FO.

While setting up the mapping , we got the error :

Account category or AX is a company-specific entity with primaryCompanyField set to DataAreaId and new_accountcategories of CRM is a cross-company entity that doesn’t have primary company field set. Please make sure the entities are both cross-company or company-specific entities.

This is simply because my custom table support cross company data sharing as stated in Microsoft documentation:

To resolve the error we can do the following:

1 . Go to Dataverse and add a new field (company) to our custom table.

2 . Add a new Key with Colum Company

and lastly

3 . Set the newly added field as an entity key on Dual write.

Voila!

The post Account category or AX is a company-specific entity with primaryCompanyField set to DataAreaId and new_accountcategories of CRM is a cross-company entity that doesn’t have primary company field set. Please make sure the entities are both cross-company or company-specific entities. appeared first on Monsieur Winner.

This happens often when an already data entity is modified. Upon synchronization, the table DMFEntity gets updated with the updated data entity. Meanwhile, the DMFEntity table has the EntityName as a primary Key.

Resolution:

Delete all records in DMFEntity via the SQL Studio.

The post Cannot create a record in Entity (DMFEntity) D365FO appeared first on Monsieur Winner.