Before you start doing any development for D365 FO there are some configurations which are recommended to make. (Note: Below configurations are not mandatory but recommended)
- Rename D365 FO machine: It’s good practice to rename VM machine to some meaningful name. This becomes necessary if we have multiple VM’s connected to same Visual studio team service site(VSTS) as VSTS cannot accept same work space name while mapping folder’s. Follow below steps to successfully rename D365 FO VM.
- Right click “This PC” icon and click properties.
- On the System windows click on “change settings”.
- On “My property” window” click on “Change” button.
- Type a new name e.g. “D365FO-Dev-Suri-Office” or any name of your choice and click Ok.
- After that restart your VM machine to reflect the name change.
- After restart of machine check the name has successfully changed. Next step is to change the reporting service database, this mandatory to do after rename of VM machine.
- Open reporting service configuration manager and connect to default instance which is using in D365 FO microsoft VM
- After connect go to “Database” tab and click on change database and select “Choose an existing report server database” on the “Report server Database Configuration Wizard” and click “Next”.
- On next page change server name to “.” a dot which denotes to connect to local database server in SQL terminology. and click “Next”.
- On next page select the reporting service database in “AX7 RTW June update” VM it is “DynamicsAxReportServer” and click Next.
- One next page put SQL authenticate keep it default and move to next page “Summary” and make sure things looks ok and click “Next”.
- After clicking “Next” on “Summary” tab database change name process start and should be successful and that’s it.
- Configure Visual studio team site in Visual Studio: The next is to connect your Visual studio to your project team site or customer team site.
- Open Visual Studio and click on “Team” menu and click “Manage connections”.
- Now click on “Server” button and add the VSTS site URL and click “OK” button. You must use the credentials which have access to this VSTS site url.
- One authenticate succeeded your you must see the project collection and team projects. Select your default team project which is “Front” in this scenario and click connect.
- Now you should see a team explorer pane on right side inside Visual Studio explorer. Click “Source control explorer”.
- Now we need to map the VSTS site project folder with their local repository or folder. Select “Metadata” folder on left pane and click “Not mapped” on right. This needs to map with with our “D365 FO” “PackageLocalDirectory”. In June2016 VM update “PackageLocalDirectory” exist at “C:\AOSService\PackageLocalDirectory”.So map source Metadata folder to this location. [Note: remove metadata from the path if it shoes in “Local folder & make sure Recursive is checked”].
- Next is to map the “Project” folder. This is where your Visual Studio solution files and project file will be saved.Map it to default location.
That’s it. You VM is now ready for development and you can now able to add your development to VSTS site so that other developer can do the “GetLatest” to always have the update version of code.
At last but not least you need to first time build/compile the all models and full database sync so that customized model objects can be compiled and sync to your local VM successfully.
I will write my next blog on how to add “AX7″ model and other AOT objects to VSTS” soon. So watch this space :).