How to connect cloud hosted environment with Data verse / Power Platform

Hello Everyone, 

By this time (now) I hope you have started using Power Platform admin center (PPAC) in your D365FO projects. A lot of new features can be enabled via Data verse on your tier-2 onwards environments. by what about our beloved dev box(es). 

Well, there are architectural difference between could hosted environments which are tier-1 , one box environment and Sandbox/Production environments which are tier-2 on wards and multi box environments. And because of this difference  Power Platform Integration cannot be configured after creating the developer environment, unlike sandbox/Production where you can enable it from LCS even after deployment. 

BUT question remain same, how to access Power platform /Data verse on my Dev box, the simple and the only answer (at the moment) is , you need to redeploy the environment and during process you need to enable Power Platform environment. 

Here are detailed steps, 

1. Navigate to LCS portal and select your project. 

2. Go to Could hosted environment. 

3. Add a new environment, and give a meaningful name. 

4. Click on Advance > Navigate to Power Platform Integration and select values as shown in below image, 

-

5. Once all detailed filled, click on Next and system will start the deployment (it may stay in Queued for some time but that's fine). 

6. On successful deployment, you will be able to have option for 'Setup Dual write application' on environment page in LCS.

7. When you click on 'Setup Dual-write Application', system will take you though wizard where you can review and procced. 

this will initiate 'Configuring Dual-write application' and may about 30 min of time. 

8. Once this step is finished, oyu will get an option to 'Enable Dual-write Connection'. So you may ask what was the previous step, will that step was to configure Dual write and this step is to enable Dual write. 

This step will link both environments. 

Note: This setup needs to be performed by the Lifecycle Services Environment Administrator.

Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

QuickFix: Issue with CAR report generation (The source for referenced module '####' is missing from the model store. Please specify the -packagesRoot parameter to instead use binary metadata for referenced modules.)

Hi Everyone, 

We have multiple ISVs and as per MS documentation I added additional parameter in cmd but While generating CAR report I got error for ISV references. 

I tried to remove reference to one ISV than next time it started giving error for another ISV. Here is the cmd I tried, 

xppbp.exe -metadata='K:\AosService\PackagesLocalDirectory' -all -model='MyModel' -xmlLog=C:\CARreport\BPCheckLogcd.xml -module='MyModel' -car='c:\CARreport\CAReport.xlsx'-packagesroot=K:\AosService\PackagesLocalDirectory


Issue and Solution: 
The issue was I used the cmd car parameter path in quotations. 

xppbp.exe -metadata='K:\AosService\PackagesLocalDirectory' -all -model='MyModel' -xmlLog=C:\CARreport\BPCheckLogcd.xml -module='MyModel' -car='c:\CARreport\CAReport.xlsx'-packagesroot=K:\AosService\PackagesLocalDirectory

The correct cmd should be as below

xppbp.exe -metadata='K:\AosService\PackagesLocalDirectory' -all -model='MyModel' -xmlLog=C:\CARreport\BPCheckLogcd.xml -module='MyModel' -car=c:\CARreport\CAReport.xlsx -packagesroot=K:\AosService\PackagesLocalDirectory

Don't miss the space after .xlsx

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta