A. Take a back up of AXDB on the On-premises environment

B. Restore the database on the Cloud hosted environment(CHE).

C. Run some sql script against the CHE to update certain values.

D. Synchronize the CHE database.

I would skip the steps A and B and move straight to the scripts.

Step 1

USE AXDBonprem;
SELECT s.name
FROM sys.schemas s
WHERE s.principal_id = USER_ID('axdbadmin');

Step 2


ALTER AUTHORIZATION ON SCHEMA::db_owner TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_ddladmin TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_datareader TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_datawriter TO dbo;


step3

USE AXDBonprem;
declare
@userSQL varchar(1000)
set quoted_identifier off
declare userCursor CURSOR for
select 'DROP USER [' + name +']'
from sys.sysusers
where issqlrole = 0 and hasdbaccess = 1 and name != 'dbo' and name != 'NT AUTHORITY\NETWORK SERVICE'
OPEN userCursor
FETCH userCursor into @userSQL
WHILE @@Fetch_Status = 0
BEGIN
exec(@userSQL)
FETCH userCursor into @userSQL
END
CLOSE userCursor
DEALLOCATE userCursor

step4

–now recreate the users copying from the existing database:
use AXDB –******************* SET THE OLD TIER 1 DATABASE NAME****************************

go
IF object_id('tempdb..#UsersToCreate') is not null
DROP TABLE #UsersToCreate
go
select 'CREATE USER [' + name + '] FROM LOGIN [' + name + '] EXEC sp_addrolemember "db_owner", "' + name + '"' as sqlcommand
into #UsersToCreate
from sys.sysusers
where issqlrole = 0 and hasdbaccess = 1 and name != 'dbo' and name != 'NT AUTHORITY\NETWORK SERVICE'


step 5


go
use AXDBonprem --******************* SET THE NEWLY RESTORED DATABASE NAME****************************
go
declare
@userSQL varchar(1000)
set quoted_identifier off
declare userCursor CURSOR for
select sqlcommand from #UsersToCreate
OPEN userCursor
FETCH userCursor into @userSQL
WHILE @@Fetch_Status = 0
BEGIN
exec(@userSQL)
FETCH userCursor into @userSQL
END
CLOSE userCursor
DEALLOCATE userCursor


STEP 6
COPY ADMIN USER

use AXDBonprem
--Update the Admin user record, so that I can log in again
UPDATE USERINFO
SET SID = x.SID, NETWORKDOMAIN = x.NETWORKDOMAIN, NETWORKALIAS = x.NETWORKALIAS,
IDENTITYPROVIDER = x.IDENTITYPROVIDER
FROM AXDB..USERINFO x --******************* SET THE OLD TIER 1 DATABASE NAME****************************
WHERE x.ID = 'Admin' and USERINFO.ID = 'Admin'


STEP 7

Now, let’s rename the orginal AXDB to AXDB_old

USE master
GO
ALTER DATABASE AxDB
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE AxDB
Modify Name = AxDBold
GO
ALTER DATABASE AxDBold
SET MULTI_USER
GO

Step 8

Rename AXDBonprem to AXDB


USE master
GO
ALTER DATABASE AxDBonprem
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE AxDBonprem
Modify Name = AxDB
GO
ALTER DATABASE AxDB
SET MULTI_USER
GO


The post Copy database from D365FO On premises to Cloud hosted environment appeared first on Monsieur Winner.

Hence , create a new Azure DevOps project would have you choose Git as default version control and TFVC is totaly missing.. This tell us we need to start using this for future project and obviously migrate current D365FO repositories from TFVC to Git.

If you probably are not ready to start using Git, fear not :). At least for now, you can enable the TFVC option form the organization’s setting.

You should have it turned off as shown above.

The post Missing TFVC Option in Azure DevOps: Creating a New Project appeared first on Monsieur Winner.

    public Description dateInWord(TransDate _date)
    {
        Description day, month, year;

        day = int2Str(dayOfMth(_date));
        month = mthName(mthOfYr(_date));
        Year  = int2Str(Year(_date));

        return strFmt("%1th %2, %3",day,month,Year);


    }

08/06/2024 ( MM/DD/YY) will is outputted as 6th August, 2024

The post How to convert from date to string using x++ 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.

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.

Warning:[DWCE0001] Export was skipped. Max lookup count supported in Initial Sync stage is 10. Current lookup count 11. Lookup fields:

transactioncurrencyid.isocurrencycode,

msdyn_customergroupid.msdyn_groupid,

msdyn_billingaccount.accountnumber,

msdyn_paymentday.msdyn_name,

msdyn_customerpaymentmethod.msdyn_name,

msdyn_paymentschedule.msdyn_name,

msdyn_paymentterm.msdyn_name,

msdyn_vendor.msdyn_vendoraccountnumber,

primarycontactid.msdyn_contactpersonid,

msdyn_salestaxgroup.msdyn_name,

msdyn_company.cdm_companycode.

To fix the issue refer to https://docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/retrieve-related-entities-query

After few checks here and there, it turns out that, there is a limitation when copying data from Dataverse. The entity must not have a table map lookups more than 10 as stated on MS Learn

Resolution:

Like the error message says, we need to remove one mapping ( a non-mandatory one). So what I did was to delete the Payment day mapping, did initial Sync successfully then re-added the field mapping.

The post Warning:[DWCE0001] Export was skipped. Max lookup count supported in Initial Sync stage is 10. Current lookup count 11. appeared first on Monsieur Winner.