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

In this article, I will talk about some of the basic settings we made for Visual Studio, the Dynamics 365 Finance and Operations development environment. First of all, I have to say that for those who have used the MorphX IDE for 15 years like me, there is an adaptation period. Drag and drop is not like what we are used to. Compiling and seeing what you have done quickly is still a little different, but X++ is basically the same. You will adapt in a short time. Sometimes, you may complain like me about the missing features, but the innovations that come are far beyond these deficiencies. So we should look at the bright side and move forward.

We can say that we X++ developers were developing software with an old method, and the new version actually upgraded us. We have caught up on the current software development methodology. From this point of view, it seems like we are in the right place. I don’t know of any other application that contains such an advanced and up-to-date software language. Let’s appreciate X++. JIn fact, with this update, a project was carried out to completely replace X++ and switch to C#, but it was not successful. In my opinion, X++ will last as long as the product is available. Perhaps one day we can even see X++ as an independent language. This is a dream, of course, there is no such plan. But why not? Currently, we can quickly develop a web page completely independent of the design layer. There is actually a framework that will take care of the basic web needs of many businesses.

Let’s talk about some settings that are useful for you to do before starting development in Visual Studio. First, let’s look at the Options section under the Dynamics 365 menu.

Image-1

When you open the Dynamics 365->Projects page from the screen that appears, there are two options. First, it creates folders according to your object types and makes your project more compact. We used to use tools or project templates for this, but they are no longer needed. Second, it starts synchronization when you create a new object. This is a matter of preference, but I don’t want it to work every time since it would slow down my speed. Of course, do not forget to synchronize manually afterwards. Especially your tables and data structures will not work properly.

Image-2

I’m leaving the settings in the Build section as is. Sometimes, if you want Best practices not to work, you can remove them from here.

Image-3

You can choose which Best Practices will work here. My choice is based on my point of view. You can choose all the necessary ones. Compiling will be a little slow. It is possible to add new rules here. I will talk about it separately.

Image-4

Here I check the Line numbers box. Be careful with Work Wrap, it can be confusing. I’m in favor of not using it. Word Wrap is a feature used to display long lines with Scroll or underlines. Moving to the bottom line can be confusing in LineNumber. It is best not to write too long lines and use it on a wide screen. If you are in a mobile environment like me, you will manage with a 14 inch screen.

Image-5

Complete the basic settings by clicking OK. Now open the Team-Team Project Collection Settings->Source Control screen.

Image-6

Here you can adjust Check-out and Check-in settings. I disable multiple Check-out. This is up to you. It feels right to me. After check-out is done, automatic get latest is a feature that is very useful in my opinion. Make sure it is checked.

Image-7

There are good features in the Check-in Policy section. For example, you can create a Changeset Comment Policy and allow developers to enter comments in a certain format.

Image-8

In this article, I have talked about the basic Visual Studio settings for DevBox. Visual Studio is a very advanced tool. Besides these, there are many settings and features. You will get used to it in time. A topic I want to mention here is naming and adding comments. In the old version, these had very clear rules. But in the new version, I have not yet settled on what the best method is with Extension and TFS. We try different things for each project depending on the team. I am planning to write an article about this.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, LCS, Azure, Azure DevOps, Visual Studio, 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 talk about the 2nd step required to start development when you start a new project for Dynamics 365 Finance and Operations. I mentioned the first step in my previous article. I explained how we can connect a new DevBox Deploy to our Azure DevOps project. In this article, I will try to explain how to create a new Model and Package and what they do.

A model is usually a distributable software solution and can contain customizations of an existing solution or it can be a new solution. It is a structure that contains Metadata and source code files. A model always belongs to a package. Package includes one or more models. The package includes model Metadata, Binary files and other associated resources. One or more packages can be made into a Deployable package. The deployable package is used to move code to test and live environments.

To create a model, go to Dynamics 365->Model Management->Create Model.

Image-1

Fill in the required information for the model. Model name is important. You need to name it knowing that you will use it constantly and see it everywhere.

Image-2

You will see two options when you continue with Next. If this is your first model, you will want to create it in the package with the model. Therefore, choose the one above. If you already have a package and want to create a new model in it, you should choose the second one.

Image-3

This is one of the most important parts. Here you should select the reference of the standard packages you will need in the model you will create. For basic development needs, those shown in the image plus Dimension and Directory will suffice. You should not select all of them here, since it will affect your package size and compilation speed.

Image-4

When you continue, you will see the last screen. If the information is correct, you can click Finish.  If you want to set this model as the default model, don’t forget to check it. The default model can be changed later from the Config file. If you want to create it in a new project, you can use the relevant checkbox.

Image-5

The automatic project creation screen is opened. We create a Dynamics 365 Finance Operations project. Pay attention to naming the project, you can use the previous approach. My logic includes Company Code + Person + Project name. For example. Such as DmrFDTrvLedgerJournalCreate. Be careful not to write too long. Also in the Location field I use K: or I create a folder named VSProjects and place it there. The path should not be long either. Do not skip the Add to Source Control part, you can add it later.

Image-6

This is the edited version. I didn’t use my name as the project name because it was an experiment.

Image-7

The project is automatically created in the new DmrWMS model we created. Let’s add a ne new Job and see how it looks in the package and project.  I added a new Job named DmrWmsJob1.

Image-8

When you enter K:\AosService\PackagesLocalDirectory, you will see your own package and when you enter it, the folders in the picture will be there. There is a file under Descriptor with definitions for the package. You must add this to version control.

Image-9

When you enter the package, you will see that the code for the DmrWmsJob1 you created is here. Actually, all X++ objects will be under the DmrWMS folder.

Image-10

When you look at your K:\VSProjects\DmrWms1 project, you will see that there are only project definitions here. Codes and objects are not stored here. This logic is specific to X++.

Image-11

In this article, I tried to explain what models, packages and projects are and how they are created. These are the three most important tools in the new version. Layer still exists, but it’s not so important anymore. In particular, it is necessary to understand the package logic and file structure well. We also have a project logic that is different from normal Visual Studio projects. Do not be confused by it. In my next article, I will explain how to connect these folders to version control.

Regards.

www.fatihdemirci.net

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

Merhaba,

X++ Set Based Operations : RecordSortedList & RecordInsertList

İyi seyirler.

Merhaba

Çok beğendiğim bende nostanji yaşatan iki makaleyi sizinle paylaşmak istiyorum.

History of AX

Technical History of Dynamics AX – From Axapta 3.0 to AX2012

Axapta’yı ilk olarak 2006 yılında Turkmedya firmasında tanıdım. Axapta 3.0 kullanılıyordu. Ben başladığımda proje canlıya geçmişti. Destek ve yeni geliştirmeler ile giriş yaptığım AX dünyasında 12 yılı devirdim. Hayatım üzerinden bu kadar etkisi olacağını tahmin edemezdim.

Selamlar.

Merhaba

Ax’ta  ilk versiyonlardan beri transaction (ttsBegin ttsCommit) blokları dediğimiz bir yapı vardır. Veri tutarlılığı için çok önemli olan roleback dediğimiz bir hata durumunda o blokta yapılan işlemlerin tümünü geri almayı sağlayan bir yapıdır. Ax ta çok sıklıkla kullanılır. Veri tabanında yapılacak işlemlerde mutlaka kullanmak gerekir. Benim bu yazıda bahsedeceğim konu bu bloklar arasında bir hata oluştuğunda roleback in dışında tutmak istediğim bir işlemi nasıl sağlayabileceğim. Genelde bu log atma bildirim gönderme gibi işlemler olur.  Bir örnekle açıklamaya çalışayım.  Eski sistemden satış verilerinin geldiği ve axta sipariş oluşturulup deftere nakledinlen bir yapı olsun.  Herhangi bir sebepten sipariş  oluşturulamadığında bir log tablosuna kayıt atmak istiyorum.   Örnek kodlar şöyle  olsun:

server static void FD_UserConnection1(Args _args)
{
    DmrSalesOrderHeader DmrSalesOrderHeader = DmrSalesOrderHeader::findByRecid(325355554);
    DmrSalesOrderLine   DmrSalesOrderLine;
    ;
    ttsBegin;
    try
    {
        // Sipariş başlığı oluşturma kodu
        while select DmrSalesOrderLine
            where DmrSalesOrderLine.OrderId == DmrSalesOrderHeader.OrderId
        {
            // Sipariş satırı oluşturma kodu
            throw error("hata");
        }
    }
    catch
    {
        DmrExceptionTable::findOrCreate("Satır oluşturulurken bir hata oluştu.", "DmrCreateSalesOrder",
                DmrSalesOrderHeader.recid,DmrSalesOrderHeader.tableId,DmrSalesOrderHeader.recversion);
    }

    ttsCommit;

}

Bu metod sipariş oluşturmaya çalışırken herhangi bir satırda hata veriyor. Bizde hata verdiğini yakalayıp hangi kayıttan sipariş oluştururken hata verdiğini bir tabloya yazmaya çalışıyoruz. Normalde hata verdiği ve tts blokları olduğu için bizim yazmaya çalıştığımız veriyi de geri alacaktı ancak UserConnection ve UnitOfWork kullanarak bunu engelliyoruz. Metot aşağıda.

static server void findOrCreate(    str1260          _exceptionDetail,
                                    str 100          _className,
                                    RefRecId         _RefRecId,
                                    RefTableId       _RefTableId,
                                    RefRecId         _RefRecVersionId)
{
    DmrExceptionTable   DmrExceptionTable;
    UserConnection      UserConnection;
    UnitOfWork          UnitOfWork;
    ;

    UserConnection = new UserConnection();
    UserConnection.ttsbegin();
    UnitOfWork = new UnitOfWork();

    DmrExceptionTable.ExceptionDetail       = _exceptionDetail;
    DmrExceptionTable.ClassName             = _className;
    DmrExceptionTable.RefRecId              = _RefRecId;
    DmrExceptionTable.RefTableId            = _RefTableId;
    DmrExceptionTable.RefRecVersionId       = _RefRecVersionId;

    UnitOfWork.insertonSaveChanges(DmrExceptionTable);
    UnitOfWork.saveChanges(UserConnection);

    UserConnection.ttscommit();

}

Selamlar.