24 February 2017

D365 | Install Platform Update 4 on a local development VM

First of all there should be no overlayering of the application platform !!!

  • Application Platform
  • Application Foundation 
  • Test Essentials 
Download the platform update

  • Log onto your dev environemnt 
  • Go to your LCS project’s Asset library. 
  • On the Software deployable package and click Import  
  • Select Platform Update 4 and click Pick
  • Click on the Name to start the download

Prepare the installation

  • Unzip the file to a local directory 
  • navigate to: ...\AOSService\Scripts\PlatformUpdatePackages.Config 
    • change the MetaPackage value: to dynamicsax-meta-platform-development
      (This is important if you are updating you dev vm)
    • If you are updating a local VM you can leave the Machine name in DefaultTopologyData.xml file as localhost, otherwise change it to the name of the pc
  • Open a command prompt as admin and navigate to the folder update folder#
    • AXUpdateInstaller.exe generate -runbookid="OneBoxDev" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="OneBoxDev-runbook.xml" 
    • AXUpdateInstaller.exe import -runbookfile=OneBoxDev-runbook.xml
    • AXUpdateInstaller.exe execute -runbookid=OneBoxDev
    • If you need to rerun a step use the following command:
      AXUpdateInstaller.exe execute -runbookid=OneBoxDev -rerunstep=1 
  • rebuild your application

Update Visual Studio Extension 

  • Open Visual Studio and click Tools - Extensions 
    • Uninstall Dynamics 365 for Operations extension
    • restart and close VS 
  • Run the installer
  • After that Version should be installed

Regenerate form adaptor models 
  • Cd C:\AOSService\PackagesLocalDirectory\Bin 
  • xppfagen.exe -metadata=C:\AosService\PackagesLocalDirectory -model="ApplicationPlatformFormAdaptor" -xmllog="c:\temp\log1.xml"  
  • xppfagen.exe -metadata=C:\AosService\PackagesLocalDirectory -model="ApplicationFoundationFormAdaptor" -xmllog="c:\temp\log2.xml"  
  • xppfagen.exe -metadata=C:\AosService\PackagesLocalDirectory -model="DirectoryFormAdaptor" -xmllog="c:\temp\log3.xml" 

Install the new Data Management service 

  • Cd into \DIXFService\Scripts  
  • msiExec.exe /uninstall {5C74B12A-8583-4B4F-B5F5-8E526507A3E0} /passive /qn /quiet 
  • msiexec /i "DIXF_Service_x64.msi" ISSQLSERVERVERSION="Bin\2012" SERVICEACCOUNT="NT AUTHORITY\NetworkService" /qb /lv DIXF_log.txt 

Open D365 and check the About Page it should show Platform Update 4 7.0.4425.16161 :)

04 February 2017

D365 | Recurring Integration - Application ID

When you create a recurring data job in Dynamics 365 (AX7) you will be asked for an application id in the "Setup authorization policy" tab.
If you don't have already created your application id within the azure active directory you need to follow these steps to get it done. This relates to the new azure portal: https://portal.azure.com

  1. Login to the azure portal and click on azure active directory
  2. Manage -> App registration and click ADD
  3. In the Create dialog enter a name, select Application type Native and provide a uri. For example the address of your onebox development environment: https://usnconeboxax1aos.cloud.onebox.dynamics.com
    Click Create - and wait a second
  4. Navigate to the newly created app - now you should already see the application id that you're looking for
  5. Before you continue in D365 click on required permissions - Add
  6. Select: Microsoft Dynamics ERP (Microsoft.ERP) as the API and select permissions as needed and click select and done
  7. Now your required permissions should look like this

That should be it. Copy the application id and enter it in Dynamics 365. Now you can go on with the recurring integration.