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

In this article, I will try to explain how to define an authorization for any object in Dynamics 365 Finance and Operation application. I do not recommend using this. The more details you go into, the more difficult it will be to manage security. However, in some cases, this will be needed. One mistake I see in these cases is to solve this with code, not with the security infrastructure. Never write code for security related work. It seems like a quick solution at first, but there will be a lot of trouble in the future. The support and subsequent requests become very difficult to meet. In this article, I will continue with the project I used in my previous articles. We had authorized a test user for the Customers form. Now they can open the form and see its data. Assume that the Customer group field was asked to appear on this user. Let’s see how we can do this.

Image-1

I add a new Privilege.

Image-2

Under Privilege, right click the Form Control Permissions section and click New Form.

Image-3

In the Name field, select CustTable form.

Image-4

Right click on CustTable to create a new object and type the name of the object you want to authorize. Grant is the key part. With No Access, we ensure that those who own this Privilege do not see this object. It may not appear in the lookup here. It doesn’t matter, you can directly write the name. These definitions will not be sufficient. We need to change a property of the object for which we will define the authorization.

Image-5

In order to make this change, we need to create an extension for our form at this stage.

Image-6

Open the Extension you created. Find the object you want to authorize and from its properties, change NeedPermission to Manual. It means that you will manage the authorization of this object. It’s better to use the Extension as the first step.

Image-7

Then add the Privilege to Duty we used in our previous articles.

Image-8

Save and compile our project and run DB synchronization for our project only. After that, when you log in with the test user and open the Customers form, you will see that the Customer Group field does not appear.

Image-9

In this article, I tried to explain how a low-level object is authorized. It can be done very simply, but if you define too many low-level authorizations, it is very difficult to work it out. Try to authorize from the entry point as much as possible.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Security, 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 introduce Dynamics 365 Finance and Operations data management infrastructure (Data Management Framework). The scope of data management is very large. I will try to talk about the basic principles in this series. Data is very important for every application, but the reason for the existence of ERP is to collect the data correctly and to create meaningful reports from the collected data. For this reason, the product has always had powerful tools for data management. With the cloud, these are now very advanced. Many different technologies such as CDS and Azure DataLake were involved. Of course, SQL and table structure remains, but with the added Data entities structure, we have a much more flexible and easily managed structure. In this section, I will try to explain how to manage Data Entity and Entity Packeges using the data management infrastructure.

The data management infrastructure consists of the following objects.

• Data entities – They are meaningful data sets. It is a structure that consists of one or more data sources to view and process a certain data. Data Entity allows us to bring these data sources together and perform transactions over a meaningful data set. It is suitable for reuse. It is used for integration, data transfer and many other purposes.
• Data project – A project record that holds edited Data Entity and relationships. It can be reused.
• Data job – Includes run Data Projects, uploaded files and recurring processes.
• Job history – Keeps the history of transactions.
• Data package – It is a compressed structure with Data project manifest and Data files. It is created over the data job. It allows importing and exporting multiple files in one operation.

You can use this structure for three different scenarios:

• Data migration
• Set up and copy configurations
• Integration

Let’s get to the topic of this article. We’ll start with a very simple data transfer. We will transfer the vendor group. (VendGroup). Log in to Dynamics 365 Finance and Operations and open Workspaces > Data management worksheet.

Image-1

Click Framework parameters Tile. Tile’ı nasıl çevirmek lazım emin olamadım. En iyi uygunu tuğla veya fayans gibi duruyor ama ben karo diyeceğim. J  You can make many settings from the screen that opens. Now just select the View defaults section as Enhanced view.

Image-2

This is now the advanced view. You can return to the old view by selecting Standard view.

Image-3

Click on the Import tile.

Image-4

Enter the basic information and click Add File.

Image-5

By the way, the data I will transfer is a csv as shown below.

Image-6

From the window that opens, I first select the Entity I want to transfer from. I determine the format. I select my file by clicking Upload and add.

Image-7

I click Yes.

Image-8

Here it says some relationships are missing between my file and the Entity. I can do it here if I want. I lick No for now.

Image-9

Transfer failed due to lack of relationships. However, the project was created. I click the icon under view map.

Image-10

It shows the links between my file and the Entity. Since the headings in my file are tags, it could not auto-match. I can do it manually from here.

Image-11

I have completed my mappings and I save.

Image-12

I go to my project and click Import.

Image-13

It adds the transfer to the working list.

Image-14

It quickly completed the transfer because my data was too little.

Image-15

Now I can open the VendGroup form and see the records I imported.

Image-16

In this article, I made an introduction to data management and performed a very simple data transfer. I will talk about very different uses of this structure in my following articles. Both consultants and software developers need to know the capabilities of this very well. There are many different uses. It is a structure that will save you a lot of time with proper use.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Data Management Framework, 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 explain how to install the Deployable Package created with Build, which is the last step of moving the developments we made from Visual Studio for Dynamics 365 Finance and Operations to Test and Live environments, to Asset Library and then how to carry this package to test and live systems. I talk about performing a simple development movement with this article. Of course, there are too many details here. There are many steps that need to be examined, especially when problems arise.

This process may be more troublesome compared to the old version, but it is definitely a better method. It will be difficult for customers who still develop live and move codes to live every day, but they should definitely switch to moving at least once a week. Even for the old version, we recommend moving to live once a week (twice at most). In this version, moving to live more frequently causes a great loss of time. The problem I usually see in projects that require intervention to live too much is that your test and design stages are insufficient. Developments that are not well designed and tested, constantly create a need to intervene to live environment. With this work logic, you cannot create projects in the new version.

In the third article of this series, we downloaded the Deployable Package, which was the result of Build. We can now upload this package to Lifecycle Services. Log in to the LCS and select our project. Open Asset Library from the menu.

Image-1

Open the Software Deploable Package tab. Open the new package download page by clicking +.

Image-2

On the page that opens, enter a name and description. It is useful to set a standard here.  Click Add a file.

Image-3

Select the package you downloaded.

Image-4

After the installation is complete, click Confirm.

Image-5

Our package appears in the list. It is not yet confirmed. After a few minutes the Valid part will also be checked. Now we can install this package in our test and live environments.

Image-6

Since it is not live in this environment, I will first show it from the test. The same steps are required for live as well.  Open your SANDBOX Test environment by clicking Full details.

Image-7

Click Maintain-> Apply updates.

Image-8

Select the package you installed from the window that opens. Apply is not active without naming it. You need to specify a suitable name format. In the new version, one of the most difficult things seems to be naming. You have to give names so many times that it is difficult to set and apply rules everywhere. After you click Apply, the test environment will automatically start to install the package and you will not be able to access the environment for at least 1 hour. You should be aware of that. You can follow the status of the installation process on the detail page of your environment.

Image-9

The process of making the package live is the same, except there are two differences. Firstly, you need to mark the Package as Release Candidate. Second, you need to set the date you want the package to go live. This is done by using the Schedule button. I could not provide an image of it because it was not live in this environment yet.

Image-10

In this article, we completed the process of moving a development environment to test and live. Of course, I explained it through a very simple and problem-free scenario. In real life, things are not that simple, but not so difficult as well. There are many tools to solve problems. Being organized is very important. You should pay attention to naming and standards. I will continue to explain the details and solution methods of this whole process. I hope it is useful for you.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps , Release Candidate, Deployable Package, 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

When you install a new DevBox for Dynamics 365 Finance and Operations, the default model is Fleet Management. If you create a new model, you can mark it as the default model while creating it. However, to use an existing model, it is necessary to make changes to the DynamicsDevConfig file.

In my previous articles, I created the DmrWMS model and marked it as the default model. Therefore, my every new project opens in the DmrWMS model.

Image-1

I have two models in this environment. If I want to work on the other model, unfortunately I cannot choose it while creating the project.

Image-2

As you can see, it is not possible to choose a model in the new project creation screen, or I could not find it. Of course I did some research.

Image-3

To change this, it is necessary to open the DynamicsDevConfig file in C:\Users\Adminb17ce65567\Documents\Visual Studio 2015\Settings.  You must go to this path with your own user. Adminb17ce65567 is my auto-generated admin user. That is the user I connect with Remote Desktop. You can find very useful information in the DynamicsDevConfig file. Let’s go over these 3 features for now.

<DefaultCompany></DefaultCompany> // You can set the default company here.

<DefaultModelForNewProjects>DmrWMS</DefaultModelForNewProjects> // You can change the default model here. When first opened, you will see Fleet Management here.

<DefaultWebBrowser                   i:nil=”true” /> // You can set the default browser here. Sometimes if you want to use Chrome for tests you can change this.

Image-4

In this article, I tried to explain how you can change the default model with the DynamicsDevConfig file. It is imperative to work with the model and it is necessary to set up the model management correctly and make sure that the software developers develop the right model. It becomes troublesome to fix them later.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, DynamicsDevConfig, 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 talk about what needs to be done after creating a new development environment. The first step is to log into Visual Studio. Then, I will explain how to connect to the Azure DevOps project. I intend to summarize the steps to be taken before starting development in a few articles.

In these installations, I will use the development environment we built on Azure. I explained how to deploy a development environment in my previous articles. Once the machine is deployed, you can download and connect Remote Desktop connection information via LCS. Currently Visual Studio 2015 comes installed, but there will be a migration to new versions of Visual Studio soon. Visual Studio must be opened with Run as administrator. For convenience, right click on Visual Studio and click Pin to taskbar.

Image-1

Right click on the Visual Studio icon in the task bar and click Properties

Image-2

Click Advanced from the screen that opens. Check Run as administrator and click OK. This eliminates the need to do this every time you open it. Also, if you forget this, some functions do not work, and you will waste time.

Image-3

We need to Sign in with an account authorized for Visual Studio.

Image-4

I use an account created for this project.

Image-5

Software developers like to use Dark themes, but I use the classic theme because I have difficulty reading on dark screen.

Image-6

If there is no problem with your user’s authorization, your login will be completed. Dynamics 365 menu is available. I will talk about the menus here in my next articles. Now open the Team Explorer screen.

Image-7

Open the connection page with the Manage Connections link.

Image-8

Nothing appears in the Select a Team Foundation Server section. The reason for this is that the user login I used to connect to Visual Studio is not authorized for the Azure DevOps project that we connect to LCS.

Image-9

Open the Azure DevOps project and invite the user to the project by clicking Invite.  Of course, you must log in with an authorized user in Azure DevOps. Since I have the information of the Admin account, I logged in with it.

Image-10

When I type my username from the search, it automatically appears. I select and add it.

Image-11

Also, since I want to have Admin rights in this project, I add my user to the Administrators section as shown in the picture.

Image-12

When I looked back to Visual Studio, I could see my project. To do this, you need to restart Visual Studio. Refreshing doesn’t work.

Image-13

When you click Connect, you will be connected to your Azure DevOps project. You will see the link under Visual Studio Team Services as shown below.

Image-14

In this article, I talked about the initial settings required for a new Devbox. First of all, it is very important to open Visual Studio with admin rights. It is often forgotten, so I explained how to make a definition to automate it. Then, we established the connection to our Azure DevOps project, which is required for the version control of our application. Now we can move on to the other settings. I will talk about Model, Package and Branch setups in my next articles.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, 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