Useful commands to manage models

Export model -

 

ModelUtil.exe –export –metadatastorepath= packages path  –modelname="ur model name" –outputpath="where the model is to be saved"

​

 

Example : ModelUtil.exe –export –metadatastorepath=K:\AosService\PackagesLocalDirectory –modelname="Model1" –outputpath="D:\BackupModel"

 

 

Import model -

ModelUtil.exe -import -metadatastorepath=packages path -file="path where u want to save with model name"

​

example : ModelUtil.exe -import -metadatastorepath=K:\AosService\PackagesLocalDirectory -file="C:\TheAxapta\Dev_To move\Model1.axmodel"

 

 

Delete -

ModelUtil.exe -delete -metadatastorepath=package path  –modelname="name of ur model to delete"

​

example : ModelUtil.exe -delete -metadatastorepath=C:\AOSService\PackagesLocalDirectory –modelname=Model1

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

[Solved] Application login redirects to other domain than customer's domain #MSD365FO

[Last updated : 25 August 2022]

Hi Folks,

Recently I was facing an issue with one of the customers, whenever any user is trying to login into any environment the login screen redirects to another domain than the customer's domain. 

After doing a bit of research and connects, I figured out that while deploying this tier-1 environment I have used my email id (which was not part of the customer domain). And system took my domain as the default tenant and ignored which azure connector was used to deploy this environemnt. 

Solution: You have to use the customer's domain email to deploy any environment on their LCS so it will take their domain as default tenant than your(Partner/Vendor) tenant. 

Now, this issue becomes more critical in case you rolled out a tier-2 or UAT instance (I haven't tied this but technically this can also happen), and non of the users can log in to this and you will end up, redeploying this from scratch. Imagine the scenario where your team already did the configuration on any of these servers and you end up redeploying, A complete mess. and a lot of rework. 

However DB backup and DIXF export can cover you there, but again a lot of rework and time is needed. Plus justify this to your customer. 

So, always use the customer's domain email id to deploy any environment for your customer. 

If this issue might have been raised a few months back, I could have used the AdminUser provisioning tool (How to set new admin user) to change it, but with the recent update, this tool is deprecated. (Yeah I also didn't like this idea).

Hope this will help and save you from ending up in a similar mess. 

For more details pl check this link

Deploy and access development environments

Update: 25 August 2022, 

If you have some old Dev VM you can actually copy the admin provisioning tool from there and paste it into the new vm at the same location. This should help you as a workaround to set new admin to dev boxes. 

Cheers!!!

-Harry 

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

Microsoft D365FO Development box walkthough in Hinglish

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

[Solved] Your connection is not private, issue while browsing DEV box

Hi Folks, 

In case of this sunny morning, you tried to login into one of the dev box which you accessing after a long back you may get the below error on the browser 

Your connection is not private

Attackers might be trying to steal your information from

This issue was caused because of the expired SSL certificate on the server, as these VM are azure hosted and Microsoft takes care few things on their own, hence this once. To fix this, you need to log into LCS and select the project and the cloud hosted environment. 

Under maintain tab, select rotate certificate, 

Select Rotate SSL certificate (NOTE: This will restart your VM, pl save any of your work before performing this action.)

It may take some time to complete this action, you can monitor the progress on the right top corner of the environment page. Sometimes, the screen doesn't refresh automatically, you may need to refresh the browser after a few mins. This action normally takes 45 min.   

Once that is done and your environment is showing up and running on LCS you can try to access it. 

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