Skip to main content

Dynamics eCommerce source control development strategy

Recently, Microsoft released their eCommerce solution. I got started by looking at how to do a bit of development locally. The guide is here https://docs.microsoft.com/en-us/dynamics365/commerce/e-commerce-extensibility/setup-dev-environment

One of the first steps to development is to clone Microsoft github repo. That's fairly easy to do.
But, the next question I had was, “how do I do my development in my own private version control and continue to pull Microsoft's latest releases?”. I don't want to manually merge folders and deal with painful files.
I am not an expert in git and still have a lot to learn. However, below is the approach we have taken and will test out over the coming weeks to see how it works for us.

Go to Azure DevOps (my choice of version control) and Import the repository.
Click on Import repository.
Give it the github URL and name.
 
After a minute it should show an Import Successful message.


Using git bash, clone your Azure DevOps repo by the following commands. I used a clean folder called gitRetail.
cd “c:/gitRetail”
git clone git clone https://MyProject@dev.azure.com/MyProject/_git/Msdyn365.Commerce.Online
Then you can add a remote connection to the original github by the following command.
cd “c:/gitRetail/ Msdyn365.Commerce.Online”
git remote add Microsoft https://github.com/microsoft/Msdyn365.Commerce.Online.git


Now you can fetch/merge or pull from the Microsoft master branch.
By doing a git fetch
E.g.
git fetch Microsoft master
git pull Microsoft master
git remote
Below are some screenshots.

Useful links:

https://docs.microsoft.com/en-us/azure/devops/repos/git/import-git-repository?view=azure-devops
https://www.atlassian.com/git/tutorials/syncing/git-pull
Thanks to my colleague and friend Pontus for helping out and always giving advice on git.

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