Engineer / Solution Architect / Dynamics 365-AX Technical Consultant / Instructor (MCT)

Bu yazıda Dynamics 365 Finance and Operations için versiyon kontrol kullanmak artık bir zorunluluk. Eski versiyonlarda da kullanma imkanı vardı ama çok iyi çalışmıyordu bu yüzden bu zamana kadar çalıştığım onlarca projenin sadece bir kaçında versiyon kontrol kullanmıştık. Tabi artık geliştirme ortamımızın Visual Studio olması bunu çok kolaylaştırıyor.  Şimdi proje başlangıcında yapılması gereken temel birkaç ayarın nasıl yapılacağına ve Branch mantığına bakalım. Branch dal demektir ve kodunuzu yönetmeyi ve geliştiricilerin bağımsız çalışmasını sağlar. Birçok Branch stratejisi mevcut. Ben bu konuda bir uzman sayılmam bu yüzden mümkün olduğunca basit hallerini kullanmaya çalışıyorum. En çok kullanılan 3 yaklaşım şöyle. Main, Main ve Dev, Main, Dev ve Release. Bu 3 farklı yöntemi kullanabilirsiniz. Daha geniş bilgi için Branching strategies yazısını inceleyebilirsiniz. Ben genelde Dev ve Main yapısıyla ilerliyorum. Eğer proje küçük ve sizden başka geliştirme yapan birileri yoksa sadece Main ile de devam edebilirsiniz. Tek Branch olduğunda birleştirme işlemi gerekmiyor daha hızlı canlıya alım yapabiliyorsunuz ama belli şeyleri almak istemediğinizde tek Branch işinizi çözmediği için en azından Dev ile çalışmak gerekiyor. Şimdi ilk tanımlar nasıl yapılıyor ona bakalım.

LCS üzerinden Azure DevOps bağlantısının nasıl yapıldığını önceki yazılarımda anlattım. Bu bağlantıyı yaptığınızda Azure DevOps projenizin içinde aşağıdaki Trunk klasörü oluşacak. Bu yapıyı korumalısınız. Sadece ilk oluştuğunda Main de klasör olarak oluşuyor. Bunu Visual Studio içinden Branch’e çevirmelisiniz. Bende sıfır bir ortam olmadığı için resmini alamadım bu yüzden resimde Main Branch olarak var.

Resim-1

Read more

Bu yazıda LCS üzerinden yeni bir ortam ayağa kaldırmak gerekli olan Dynamics Deployment Services Account yetkisi nasıl verilir adım adım tarif edeceğim. Öncelikle Admin hesabıyla Azure Portale giriş yapıyoruz. Cost Management +Billing > Subscriptions kısmını açıyoruz.

Resim-1

Read more

Bu yazıda size Dynamics 365 Finance, Dynamics 365 Supply Chain Management veya Dynamics 365 Commerce için yeni bir lisans satışından sonra uyarlama projeyi başlatmak için gerekli olan adımları anlatmaya çalışacağım.

Öncelikle firmanın Tenant Administrator hesabıyla Azure Active Directory (Azure AD) de aşağıdaki adımları takip ederek aktivasyon işlemi yapılmalı:

1. InPrivate/Incognito olarak yeni bir oturum oluşturun ve Microsoft 365 Admin Center’ı açın.
2. Tenant Administrator hesabıyla giriş yapın.
3. Billing > Products & services gidin ve orada aldığınız ürünün olduğundan emin olun. Eğer yoksa iş ortağınızla iletişime geçin.
4. Eğer ürün aboneliği (Subscription)  aktifse uygulama projesi (Implementation Project) oluşturmayı tetiklemek için LCS ye giriş yapın.
5. Yeni bir sayfada LCS’e Tenant Administrator hesabıyla giriş yapın.
6. Ekrana çıkan kutucukları onaylayın böylece proje oluşturulmuş olacak.
7. Tenant Administrator otomatik olarak Project Owner rolüne atanır. Bundan sonra projeyi LCS de görebilirsiniz.

Yukarıdaki adımları tamamladıktan sonra eğer bir sorun yoksa Resim-1 de görünen uyarlama(Implementation) projesi oluşacak.

Resim-1

Read more

In this article, I will try to explain step by step how to deploy a new virtual machine for new X++ developments. In this example, I will explain how to do this in a client environment. It has a similar logic in virtual machines for partner or educational purposes.

First, we log in to Lifecycle Services. Select your project and select Cloud-hosted environments from the hamburger menu.

Image-1

A page will open and list your environments. Here you can view the details and manage their status. For a new environment, click the + Add button.

Image-2

The first screen that opens has Application Version and Platform Version. You usually select the most recent one. Of course, you should select the version of your environment here. Click Next to proceed.

Image-3

Here you select the type of the environment. Available options are Demo and DevTest. For development, you should select DevTest.

Image-4

There are two options here. First one is used for Build or Test. For development, you should select Develop. For additional Test or Build environments, you should use the option above.

Image-5

Here you can adjust the environment settings. First give a name. This name is not virtual machine’s name. We will set it from the advanced settings. The most important option is D12 machines that are recommended for you, but if you want it to be a little faster and money is not an issue, definitely choose D13. Think of it like D13 is exactly twice as D12 in terms of money and configuration. You can view the advanced settings by clicking Advanced Settings.

Image-6

You can make advanced settings from the screen that opens. You don’t need to change many settings.  I will talk about the important ones. Visual Studio Version has two options.  Pro and Enterprise, use whichever suits you best.

Image-7

Here you can find the details of the version. Generally, you need to keep all development versions the same.

Image-8

Here you can choose whether you want Demo data in your environment. Generally, this is not necessary for the customer environment. If you are going to use Management Reporter, you can select demo data for it as well.

Image-9

In this section you can adjust the disk sizes. These settings are sufficient for general improvements.

Image-10

You can enter the virtual machine name here. If you leave it blank, it automatically assigns a name, and it’s not a good one.

Image-11

After completing the settings, you can start the deploy process by clicking Next.

Image-12

You will then be able to see your new environment in Deploying status in the list below. It usually takes 3-4 hours to complete. I’ve seen it take less. I did not start Deploy because it was not needed for this environment.  When these steps are done, the virtual machine will be ready. Even if you see the virtual machine when you go to the Azure side, do not try to open it before the process is completed. In order to properly use the environment, this must be Deployed.

Image-13

In this article, I briefly explained how to deploy a new development machine and I will explain the necessary settings to start developing on this machine in my next articles.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps,X++, Project onboarding, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, Dynamics 365 Insights Power BI, Power Automate, Power Apss, Power Virtual Agents, what is Dynamics 365, Dynamics 365 ERP, Dynamics 365 CRM

In this article, I will try to tell you the steps required to start the adaptation project after the sale of a new license for Dynamics 365 Finance, Dynamics 365 Supply Chain Management or Dynamics 365 Commerce.

First of all, the activation process should be performed in Azure Active Directory (Azure AD) with the company’s Tenant Administrator account by following the steps below:

1. Create a new session as InPrivate / Incognito and open the Microsoft 365 Admin Center.
2. Log in with the Tenant Administrator account.
3. Go to Billing> Products & services and make sure the product you purchased is there. If not, contact your business partner.
4. If the Subscription is active, login to LCS to trigger the Implementation Project creation.
5. Log in to the LCS with a Tenant Administrator account on a new page.
6. Confirm the boxes that appear and the project will be created.
7. Tenant Administrator is automatically assigned to the Project Owner role. You can then view the project in LCS.

After completing the above steps, if there is no problem, the Implementation project will be created as shown in Image-1.

Image-1

When you click and enter the project, you will see a menu on the right as shown in Image-2. The first thing to do is to click on Project onboarding and start making the necessary definitions. When you click it, a wizard will open and steps will appear. You can skip the steps. You can return to them later.

Image-2

After completing the steps, you will have a project screen similar to Image-3. I will try to explain the Environments section on the right in detail in another article.

Image-3

I had already defined the steps for this project and had not taken a picture. So I clicked on Project Onboarding from the hamburger menu and reopened it and took the pictures.  It is not exactly the same as the first form, but the definitions are the same.

Image-4

Welcome page. It is useful to read all the explanations in the steps carefully.

Image-5

There are some important fields on this page. First of all, a name and a description are required for the project. It is useful for everything to be in English. Because Microsoft employees who will assist you need to be able to understand the information about your project. Here you choose the business partner you will work with on the project.

Industry: The field of activity of the company is important because the FastTrack engineer to be assigned to you is selected according to the industry expertise here. For example, if the project is a retail project, an engineer specialized in retail is assigned to you.

Implementation team country/region: The location of the main project team.

Legacy system: If there is a migration from an older version or a different ERP, you can select it here.

Preferred Azure region for production: Currently the optimal choice for Turkey is Data Center West Europe. Generally we choose this in projects.

Future user licenses: If you expect an increase in the number of languages when the whole project goes live, you can specify it here. It is useful to do this because the live server configurations are set according to your license and some information you provide.

Image-6

In this section, we select the modules to be used for the project and the necessary settings. We marked warehouse management and MRP, since they will be used in this project. Also, we mark any of the other Dynamics 365 products that will be used. We marked Power Platform, since only that will be used in our project.

Image-7

In this section, we define the project team. You do not need to enter the whole team at the first stage. It is useful to define Project Manager and Architect roles especially for the FastTrack team to communicate.  Those starting with Microsoft come automatically, you don’t need to do anything for them.

Image-8

Project dates are required to be entered at the first stage.  A separate window opens for that. The dates can be changed later, but you need to enter the correct dates at the first stage. The whole project plan is created according to these dates and the FastTrack team supports you according to these dates.

Image-9

This is one of the most important steps. Dynamics 365 projects are now managed through Azure DevOps. First, you need to set up Azure DevOps with the given Admin account and create a TFVC type project. Unfortunately Git is not yet supported. I’ve come across Git uses in some articles, but haven’t tried it yet.  You will then establish the relationship between LCS and Azure DevOps here. There are a lot of details on Azure DevOps, which I will cover in another article.

Image-10

After connecting the project, you should establish a link between LCS and Azure DevOps steps. I leave this part as it is. In the future, there may be projects that we change according to the project needs.

Image-11

FastTrack introduction and related links are available on this page. Especially TechTalks has very good content, you should definitely watch it before the project.

Image-12

This section provides general information about the project steps and useful links.

Image-13

In the last step, we complete the project start.

Image-14

One of the most important settings you need to set after you finish is to add Azure Connection. If the company does not have an Azure account, you must start a membership through the Azure Portal with an Admin account. Here there are a few steps you need to follow. To connect LCS with the Azure you have opened, you must download the certificate and upload it to the Azure Portal. You must also authorize Dynamics 365 application installation via the Azure Portal. I will prepare a separate article for this section.

Image-15

After completing all these steps, you are ready to set up the media. Depending on the license you purchased, Microsoft gives 3 media rights shown in Image-16. There is no charge in these media. You pay according to the pay-as-you-go method for each additional environment you want to set up. Often additional environments are needed for DevBox and Test. You can install these machines from the Cloud-hosted environments menu.

PRODUCTION: It is deployed by Microsoft in the final phase of the Project.

SANDBOX: STANDARD ACCEPTANCE TEST: This machine is Tier-2 and is mainly used for Testing. We setup this environment. By setup, I mean we adjust the settings, determine its type and Microsoft prepares it for us.

SANDBOX: DEVELOP AND TEST: We usually set this machine as the Build machine. They have removed connecting to these machines with the Admin account, so you shouldn’t use this machine for development.

Image-16

In this article, I tried to explain the necessary steps for starting the project after licensing. It is necessary to consider many different options depending on the size and complexity of the project. There are now three indispensable places for an ERP project and you should know them well. LCS, Azure and Azure DevOps. Knowing the basic features of these three products, each of which is a separate world, makes it easier to project and reduce costs. I have made an introduction to the LCS and I will continue to explain the details.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Project onboarding, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, Dynamics 365 Insights Power BI, Power Automate, Power Apss, Power Virtual Agents, what is Dynamics 365, Dynamics 365 ERP, Dynamics 365 CRM