DevOps Source Control strategy for many Customers

(1) Share

Report

Posted on by Vasileios Papoglou

We have a core model that contains our localization and we wish to create a deployement model that will allow us to push only the changes that concern each customer separately.

The issue arises from the fact that we can't realisticaly separate the changes and the only real way seems to be to create a branch for each customer. This in turn doesn't look like a good solution since it will be difficult to manage it. Ideally we would like to use TFVC to have a structure or method that will effectively have dev -> main -> customer. Therefore we can have the main branch feed each customer's branch and we can selectively apply which changes will end up in each customers environment. Any opinions?

Categories:

Dynamics 365 Finance

All responses (4)

Answers (0)

Vasileios Papoglou 88 on at

Like (0)

Report

DevOps Source Control strategy for many Customers

Hello all,

André, we have already implemented parameters settings utility that allows our customizations to be active or inactive. The issue arises from the fact that there are project wide changes that cannot be activated/deactivated from the code or settings such as overwritting the language localization files. That's why we are thinking of a solution with multiple branches since this will allow us to either include or exclude such changes in the final package(from the pipelines).

Thanks to everyone for your time and quick responses.
André Arnaud de Cal... 296,161 Super User 2025 Season 1 on at

Like (0)

Report

DevOps Source Control strategy for many Customers

Hi Vasileios,

When you mention you have a localization, it sounds like a general ISV solution. Why do you have customer-specific changes? That should be considered as project-specific customizations, or you can consider controlling the activation of specific features by parameters.
Mariano G. 3,596 on at

Like (0)

Report

DevOps Source Control strategy for many Customers

I would suggest creating a separate extension for each customization so that, as you said, each one can have its own branch. The main model would be shared across all your customers, and to simplify deployments, I would include that main model in a deployable package and publish it to Azure Artifacts, as explained in this post: How to Push your MsDyn365FO deployable package to Azure Artifacts as NuGet packages – MsDyn365FO.Blog
Jonas "Jones" Melgaard 4,610 Super User 2025 Season 1 on at

Like (0)

Report

DevOps Source Control strategy for many Customers

When I worked as a developer at a consultancy, we hosted some customer implementation projects in our own organization but had customer specific projects.

Can you do something like this? Or a separate repository for each customer.

I.e. feed your localization core to the customer projects / repositories, and then perform the extensions there.

Community site session details

DevOps Source Control strategy for many Customers

Helpful resources

News and Announcements

Quick Links

Ramesh Kumar – Community Spotlight

Congratulations to the June Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

DevOps Source Control strategy for many Customers

Helpful resources

News and Announcements

Quick Links

Ramesh Kumar – Community Spotlight

Congratulations to the June Top 10 Community Leaders!

Announcing the Engage with the Community forum!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates