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.
Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more