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

Segregation of Duties görev ayrılığı olarak çevriliyor. Let me explain it with an example. Let’s say you want two critical Duties not to be assigned to the same person. For example, two duties such as invoice processing and payment should not be assigned to the same person. You are in a company where thousands of people work and it is not possible to track at a certain stage. Here SoD comes into play. A definition you make through Duty gives you a warning for such situations and allows you to control them.

Let’s see an example using the security objects we used in previous articles. Open the Security Configuration form.

Image-1

From the Segregation of duties tab, click on the Segregation of duties rules button. This form is also available directly on the menu. You can see it in Image-9.

Image-2

There are no records yet in the form that opens. Let’s create one by clicking New.

Image-3

Specify a name and select two Duties. I have chosen two sample Duties. The only thing I pay attention to is, I know which roles these two Duties are used in. I will need it to show the example. Of course, you will make this definition according to your business needs.

Image-4

After saving, it comes to my test user. FD Customer listing task is attached due to its current role. I add a new role and select one that includes Customer Invoicing. When I click add, there is a warning saying that a conflict occurred. If I click Yes, it will create a solution record for me.

Image-5

The record created includes information about this operation. I can accept assignment with the Allow Assignment option.

Image-6

Accepting means overriding the rule, so it asks for an explanation. After providing one, we have added the role. We could have blocked it if we wanted to.

Image-7

When you create a new SoD, you can check if there are anything that does not follow this rule. There is something that doesn’t follow my rule, but since we created an override record it didn’t appear here.

Image-8

You can follow the created records from the menu in Image-9.

Image-9

In this article, I have tried to explain briefly what Segregation of Duties is. Although it is a very nice feature, it still has many deficiencies. For example, it only works with Duty, but there is no solution for direct Privileges assigned to a Role. It asks when adding it to the role, but it does not have a mechanism that controls the changing duty contents afterwards. It is possible to use it. Especially if you do not define authorization other than Duty and create your Duties with the right logic, you can use it very easily. Investments are still being made in this feature, I think it will become much more developed in a short time.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Segregation of Duties, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, Dynamics 365 Insights Power BI, Power Automate, Power Apps, Power Virtual Agents, what is Dynamics 365, Dynamics 365 ERP, Dynamics 365 CRM

How to Move Developments to Dynamics 365 Finance and Operations Test and Live Environments? 3- Build

In this article, I will talk about how to perform the Build operation required to move the developments we made from Visual Studio for Dynamics 365 Finance and Operations to Test and Live environments. Build needs to be performed on a certain Branch. When Build is complete, if there is no error, it will generate a Deployable Package for us. We need this package for code migration.

You have to perform Build through Azure DevOps, not from Visual Studio. After logging in as a user with admin rights, open the Pipelines tab. Unified Operations platform – Build Main will be created automatically when you set Azure DevOps settings via LCS. We will take this as basis. Since our environment is only Main Branch, I continue without making any changes in the basic settings.  First let’s see how we can run it, then we will examine the other settings.

Image-1

Click the Edit button from the ellipsis menu.

Image-2

Build steps are listed.

Image-3

If you want to build a different Branch, you need to change the Server path. We are making a change here.

Image-4

You can right click and Disable steps that are not required at this time. I disabled the Deploy Reports step because I do not have a report development.

Image-5

The main step is Build the solution. Our Branch path is here again. If you want to build a different Branch, you should change this as well.

Image-6

Click Queue. Whn you click Run in the popup window, Build operation starts.

Image-7

You can follow the Build steps.

Image-8

If it completes with no errors, it will look like the following. If it gives errors, it is necessary to examine the logs and errors. Generally there are not very complex problems. There are cases such as missing reference, incorrect Check-in, but there may be situations that need to be further examined. You can open it by clicking on the record.

Image-9

When you enter, all your previous Builds will be listed. You can view their status and information. The first record is our last Build, completed without error. Click to open it.

Image-10

You can see details about the Build here. Click and open the relevant part (3 published).

Image-11

Under Packages, Deployable Package starting with AxDeployableRuntime is created. We need to download it from here and upload it to the LCS. I will explain this in my next article.  At this stage, the Build operation is done. Now let’s look at how you can create a new Pipeline.

Image-12

Main Pipelines are created by default. If you want to create them in other Branches, you either make all the definitions manually, which is very demanding, or you can use the Clone or Export features. For both cases, do not forget to change the path settings for the new Pipeline.

Image-13

You can Import the Exported file from the following path again. Generally code is transferred to live environment from Main or Release Branch, and to test environment from Dev Branch. Of course, these are approaches that vary depending on the project and the team.

Image-14

In this article, I tried to explain how Build is triggered through Azure DevOps. A machine is required for Build right now, but we will soon be able to do this thanks to an agent. It will be a faster and inexpensive solution. By completing this stage, we have reached the final stage in code migration. In my next article, I will explain how we deploy code over LCS.

Regards.

www.fatihdemirci.net

Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Build, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, Dynamics 365 Insights Power BI, Power Automate, Power Apps, Power Virtual Agents, what is Dynamics 365, Dynamics 365 ERP, Dynamics 365 CRM

In this article, I will try to explain how to define new users for Dynamics 365 Finance and Operations. If you want to add users to the test and live systems, you usually use import from Azure Active Directory. If you want to create a test user for your development machine, you can create a new user. Let’s take a look at both now.

First, open the System Administration->Users form. You must login as a user with the Admin right. If this is a development environment, the account you used for installation already has this right. I explained it in my previous articles.

Image-1

Click Import users, and the page that opens lists the users we can import. You can import the users you want.

Image-2

An information message appears. Then you need to grant the users the necessary roles. In the old version, there was a role assignment tab during Import. The new version does not have it. I think it was a nice feature. It gets messy especially when I transfer multiple users.

Image-3

Now let’s add a user that is not in Azure Active Directory. For example, I need to do some tests on my own development machine, or consultants need to do the initial tests in VM. Of course, security should be involved in these tests because when I open the application via VS, it opens as Admin and does not have any security restrictions. I need a user to assign the required roles. So I need to create a new user.

I click New and start creating. I enter the user information. I used a Hotmail account. You need to change the Provider according to the account you use.

1. If it’s an account that’s in its own AAD Domain: https://sts.windows.net
2. If it’s an account that’s in a different AAD Domain: https://sts.windows.net/XXXXX.XXX, (https://sts.windows.net/emiralfg.com)
3. If it’s a Microsoft account: https://sts.windows.net/hotmail.com

Image-4

User is created after saving. In Image-4 the Provider is missing. It should be as in Image-5. Add new role by clicking Assign Role. Here you can assign any role you want. You can also have your own roles created for testing. Since I want to use it like Admin, I assigned the role of Admin.

Image-5

I try to open an InPrivate browser, paste the address of the environment, and login with my user.

Image-6

I entered the environment without any problems. Since I logged in from a different environment, a few security steps were required, but it didn’t cause any problems.

Image-7

In this article, I tried to explain how to add users to different environments of Dynamics 365. Security and user management is very important. Many details are available and I plan to mention them in the following articles.

Regards.

www.fatihdemirci.net

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

Bu yazıda X++ sorgu anahtar kelimelerinden changeCompany inceleyeceğim. Öncelikle uygulamanın şirket yönetimini anlamak gerekiyor.

Uygulamadan istediğiniz kadar şirket tanımlayabiliyorsunuz. Kullanıcılar uygulamaya girdiğinde bir şirkette işlem yapıyorlar. İstedikleri zaman şirket değiştirebiliyorlar. Tablolarda DataAreaId sayesinde verilerin hangi şirkete ait olduğu tutuluyor. Eğer bir tablonun verisi şirket bağımsız olsun diyorsanız ayarlayabiliyorsunuz. Ancak bu tip tabloların dışında yaptığınız bütün işlemler bulunduğunuz şirkette gerçekleşiyor. Bir sorgu yazıp verileri görmek istediğinizde siz Range olarak şirket vermezseniz bile sistem SQL’e giden koda otomatik bulunduğunuz şirketi ekliyor. Eğer faklı kodunuz farklı şirkette çalışsın istiyorsanız bunun için changeCompany kullanabilirsiniz. Bir örnek yapalım.

static void Dmr_FD_ChangeCompany(Args _args)

{

DmrAuthorTable  authorTable;

DmrBookTable    bookTable;

;

changeCompany(“USF”) // Şu anda USMF şirketindeyim ve çalıştırdığım kodlar burada çalışacak. Ancak changeCompany ile şirket değiştirip bu kod bloğunda USF’te çalışsın diyorum.

{

while select authorTable

notexists join  bookTable

where authorTable.AuthorId ==  bookTable.AuthorId

{

info(strFmt(“%1 %2 %3 %4″, bookTable.BookId , authorTable.AuthorId,

authorTable.FirstName ,  bookTable.Title));

}

}

}

changeCompany çok kullanılan hayat kurtaran bir özellik ancak genelde yanlış kullanıldığını görüyorum. Örnek 3 faklı şirkette 1000 satır veri aktarımına benzer bir kodunuz var diyelim. Arkadaş bu veriyi gruplamadan her bir satıra changeCompany yazıyor ve bunun hızlı çalışmasını bekliyor. Olmaz changeCompany zaman alan bir koddur ve mümkün olduğunca az kullanılmalıdır. changeCompany bloğunda yazılan her kod sanki değiştirdiğiniz şirkette çalışır sadece select değil Insert Update Delete işlemlerinde yapabilirsiniz.

Selamlar.

www.fatihdemirci.net

TAGs: X++, changeCompany, Azure, Azure DevOps, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365

Bu yazıda Dynamics 365 Finance and Operations uygulamasının çok güzel bir özelliği olan Change-Based Alert’den bahsedeceğim. Nedir derseniz sistem içindeki herhangi bir tabloda yapılan herhangi bir işlemden sonra bildirim göndermedir. Bu bildirim ekranda da çıkabilir mail olarak ta alabilirsiniz. Bu özellik kullanıcının kendi ayarlarını yapabileceği bir yapıdadır. Kullanıcı bazlı oluşturulabilir. Şimdi bir örnekle uyarı kurulumu yapalım. Öncesinde Change-Based Alert toplu işini kurmamız gerekiyor.

Resim-1

Read more