Skip to main content

AX and Scrum: Setting up your environment

Scrum encourages version control. Below is the setup we have. Our development environment is local to all developers.

When a unit of work is complete and meets best practice it is checked in. Then on a regular basis the Test environment will be updated using the TFS synchronise functionality. This should update the test environment will all checked in work.

This diagram below illustrates this process.

2013-08-19_1750

We have 3 environments for product development:

Environment name

AOS

Comment

Daxeam_Dev

Developer machine

Install on developers machine and TFS is enabled.

Daxeam_Test

AX6-AOS-TEST

Installed on the server and TFS is enabled. When a developer is finished with a piece of functionality it is synced into this environment for testing.

Ideally a nightly build is recommended to ensure that everything is fine and it can be picked at as soon as a problem occurs. We actually do this on the last 5 days of our sprint- every night.

Daxeam_Release

AX6-AOS-RELEASE

This environment is built on release of a sprint. This environment is updated towards the end of the sprint during the last week (built every night). The environment is updated by a model import. We call this our FIT (Functional Integration Testing) environment.

During each sprint we branch our code in TFS. So, we could potentially build an environment at any particular point. We package everything up:

  • Model file (signed)
  • Help file installer (signed msi file)
  • Documentation (Implementation document, release notes, technical document etc)

If new developers join it is quite easy to add them on. Just install a base database and starting synching with TFS.

 

Resources:

There are a number of resource online for build scripts,

Change management and TFS integration for multi-developer projects (white paper) [AX 2012]

http://technet.microsoft.com/en-us/library/jj713631.aspx

http://blogs.msdn.com/b/axsa/archive/2012/10/22/tfs-integration-with-microsoft-dynamics-ax-2012-and-automated-scripts-for-build-and-deployment.aspx

http://daxmusings.codecrib.com/p/alm-tfs.html

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi