Posts Tagged ‘ MsDyn365CE

How to make new mobile forms on Dynamics 365 Finance and Operations web forms?

In this article, I will try to explain how to generate new mobile forms from Dynamics 365 Finance and Operations forms. In my previous article, I explained how to publish standard mobile screens and how to install Dynamics 365 Mobile App on mobile devices.

In this example, we will make a very simple listing screen. I selected the all products form as an example. Open the Product information managment -> All products and product master form.

Image-1

Click on the Mobile app from the settings icon.

Image-2

Click the ellipsis icon from the form that opens and click Create.

Image-3

Enter the information of the mobile form you want to create. Then add a page by clicking Add page.

Image-4

When you click Done, the page creation screen opens.  Here, click Select fields to open the screen where you can select the fields you want.

Image-5

Select the fields by clicking the + icons.

Image-6

I added two fields. After finishing the process, click Back and return to the first page.

Image-7

You see the page you created on this screen. You can create multiple pages.  Continue the process by clicking Done.

Image-8

Id is created here. Complete your mobile worksheet by clicking Save.

Image-9

You can now see it in the list. Publish it by clicking Publish. You will now be able to see the product list form from the application on your phone.

Image-10

Open the application on your phone and log in.

Image-11

Check I understand and tap Connect.

Image-12

My Products appears on the page that opens. If you entered before, you need to refresh.

Image-13

Once you enter, you see the list form you created.

Image-14

When you click and enter, your products are listed. We added two fields, and they are one under the other.

Image-15

In this article, I tried to explain how you can create mobile forms from any form. I exemplified it with a very simple form, but you can do it with forms with more complex data entries. I will also refer to more advanced examples in my next articles. Preparing such easy mobile forms will be very useful in projects. Thanks to this, many simple needs can be solved at no cost. Application consultants should learn the capabilities of this thoroughly and direct the emerging needs to this.

Regards.

www.fatihdemirci.net

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

X++ :3- Container Nedir?

X ++ Temel veri tiplerinden biri olan Container farklı tipteki verileri içinde barındırabilir. Tablolara açılan alanlar Container tipinde olabilir. Birçok fonksiyon ile veri yüklenip alınabilir. Özellikle farklı tipteki verileri bir yere göndermek ve çekmek için kullanılır.

Yeni bir Job oluşturup bir örnek kod yazalım.

Resim-1

class FDContainer

{

public static void main(Args _args)

{

int             number1;

str             name;

AccountNum      AccountNum;

CustTable       custTable, custTable2;

container       c;

Gender          gender;

utcDateTime     dateTime;

;

name        = “Fatih Demirci”; // Değişken ataması

custTable   = custTable::find(“M000017″);// Değişken ataması

c = conins(c, 1, name); // Contianer Insert işlemi

c = conins(c, 2, custTable);

c = conins(c, 3, 12321);

[name,  custtable, number1] = c; // Container’daki değerleri değişkenlere alma.

c = ["fatih", 12, custtable, Gender::Male]; // Tek seferde çoklu değişken atama

dateTime = dateTimeUtil::newDateTime(systemdateget(), timeNow());

name        = conpeek(c, 1); // tek bir değişken seçme

custTable   = conpeek(c, 3);

c           = conins(c, 4, dateTime);

info(“OK”);

}

}

Bu yazıda Container’ı size tanıtmaya çalıştım. Çok kullanışlı bir veri tipi çok sık kullanıldığını göreceksiniz. Bende bunu basit işler için kullanıyorum. Çok büyük veriler için uygun bir yapı değil. Dizi gibi düşünün.

Selamlar.

www.fatihdemirci.net

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

How to set up Azure Connector for Lifecycle Services?

In this article, I will try to explain how to set up the Azure connection required to Deploy Dynamics 365 For Finance and Operations via Lifecycle Services. First, open your project from Lifecycle Services. Under Environments, click on Microsoft Azure settings.

Image-1

Your Azure Connectors will appear from the Azure connectors tab, if any. Since I have an available connection for this environment, it appears on the list. When you check here again after completing these steps, the connection should be established.  You can start adding a new link by clicking the + Add button.

Image-2

In the window that opens, Name will be the name we gave for the link.  In the Azure subscription ID section, you must enter the code of the Azure membership we want to connect to. Tenant Domain information will automatically be available. You should mark Azure Rsource Manager(ARM) as Yes. Proceed to the next page by clicking Next.

Image-3

You must have given the Dynamics Deployment Services authorization that I mentioned in my previous article before this step. If you have, you will see the screen below. Proceed to the next page by clicking Next.

Image-4

Before continuing, you need to download the Management certificate and upload it to the Microsoft Azure Portal. You can leave this page open.

Image-5

Sign in to the Azure portal and choose the membership you want to connect with.

Image-6

Click on the Management certificates section and click the Upload button in the window that opens.

Image-7

Select the certificate you downloaded and install it.

Image-8

When you see this screen, it means the installation process is completed.

Image-9

You can return to the screen in Lifecycle Services and continue by clicking the Next button. After this stage, you can continue without any errors. 

Image-10

In the Azure region, you usually choose West Europe.

Image-11

After clicking the Connect button, you should see an item like the one below in your Azure Connection list. At this point, the connection is complete.

Image-12

In this article, I tried to explain how to set up Azure connection through Lifecycle Services. Since Dynamics 365 is a structure running on Azure, it is necessary to have knowledge about many Azure issues. I plan to continue writing articles on these topics. I hope it is useful for you.

Regards.

www.fatihdemirci.net

TAGs: Lifecycle Services, LCS, Azure, Azure DevOps, Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, Dynamics 365 Insights, what is Dynamics 365, Dynamics 365 ERP, Dynamics 365 CRM, Azure Connections

How to Install and Use Dynamics 365 Finance and Operations Mobile App?

In this article, I will talk about the Mobile app feature that comes with Dynamics 365 Finance and Operations. With Dynamics 365 Finance and Operations, there are many mobile applications that come as standard. You can create new applications, and you can make the existing forms suitable for mobile. I will also explain new mobile application creation process in the following articles. In this article, I will publish a few applications and try to show them through the application I installed on my Android phone.

First, log in to Dynamics 365 Finance and Operations. Click Mobile app from the settings.

Image-1

Available mobile apps will be listed.  You can select the ones you want and Publish.

Image-2

For Android, search for Microsoft Finance and Operations (Dynamics 365) in the Google Play Store, search for Finance and Operations (Dynamics 365) in the App Store for Apple and install the application. I installed it on Android.

Image-3

After the installation is complete, open the application. Enter the link of the environment you want to connect to and click Connect.

Image-4

Here you need to grant permissions.

Image-5

You have to check I Understand and tap Connect. You will need to enter the user and password on the screen that appears.

Image-6

The application is ready. First let’s select a company. Click on Change company from the hamburger menu.

Image-7

Companies will be listed here. Dat is not used because it is the default company. Here you can select the company you want to work with.

Image-8

When you go to the workspace, you will see the applications you Published. You can now start using it. I opened the Project Time Entry application.

Image-9

Once you enter it, a new login page link appears.

Image-10

When you click it, the date selection screen opens. I opened the screen for creating a new record with New Entry below.

Image-11

This is the new record entry screen. Records entered here will appear directly in your Dynamics 365 Finance and Operations environment. Since I do not want to corrupt the data in the environment I use, I did not log in.

Image-12

In this article, we made an introduction to the Mobile App. I tried to explain how we can start publishing and using the installation and standard mobile applications. In my next articles I will try to explain how you can make your own mobile applications.

Regards.

www.fatihdemirci.net

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

How to set up Azure Auto-shutdown for your Dynamics 365 Cloud Hosted machines?

With Dynamics 365, we met Developer VMs and since they work on a pay-as-you-go logic, they must be closed when you are not working with them. Especially in projects where multiple software developers are working, it is useful to arrange the virtual machine opening and closing in order to avoid problems in terms of cost and time management. In this article, I will explain the Auto-Shutdown feature that comes with Azure. I will also talk about a product you can use for more advanced adjustments.

First, let’s talk about Azure Auto-shutdown. This feature allows you to automatically shut down your virtual machines at a certain time every day. It also allows you to take special action with notification emails. Let’s take a quick look at how to set up and get notifications.

Enter the Azure Portal and choose your virtual machine. Click on Auto-shutdown from the menu.

Image-1

On the page that opens, we set the Enabled section to On.  Select the time and time zone you want it to turn off. Send notification before auto-shutdown? This is very useful. Sometimes it is necessary to work overtime, or a process that you run takes a long time. In such cases, notification and postponement links in the notification make it easier. You can send these notifications to a service over a web with Webhook URL. I have never used this. I usually use the Email Address. You can add as many e-mails as you want with semicolons. After completing the definitions, you can save them by clicking Save.

Image-2

When it’s time to shut down, you will receive an email like the one below. Using the links, you can postpone it for 1 or 2 hours, or skip it for once.

Image-3

As the name suggests, Auto-shutdown does not have a mechanism to open the virtual machine, it only performs shutdown. You can use the Start/Stop VMs during off-hours option in Azure Marketplace for this.

Image-4

It tells you what you need when you open it and how to activate it. Just start with Create and follow the steps. It has a simple setup, so I will not go through it step by step. Thanks to this tool, you can turn off/turn on your VMs at any time. For example, if the work starts at 9:00, it would make sense to open it at 8:30.

Image-5

In this article, I talked about the Azure Auto-shutdown tool used to automatically shut down your virtual machines and the Start/Stop VMs during off-hours tool that can also do a turn on operation. It is beneficial to build these tools well in order to manage costs effectively.

Regards.

www.fatihdemirci.net

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

How to give Dynamics Deployment Services Account authorization to Microsoft Azure Subscription in order to deploy Dynamics 365 Finance and Operations?

In this article, I will describe step by step how to authorize Dynamics Deployment Services Account, which is necessary to deploy a new environment via LCS. First, log into Azure Portal with the Admin account. Open Cost Management +Billing > Subscriptions.

Image-1

Select the subscription you want to authorize and click on Access control (IAM) from the screen that opens.

Image-2

Open the new role definition window by clicking on Add> Add role assignment.

Image-3

In the window that opens, select Contributor as Role. In the Assign Access to section, select Azure AD user, group, or service principal. When you type Dynamics in the Select section, the options will be automatically available. From there, select Dynamics Deployment Services [wsfed-enabled] and click save.

Image-4

When the process is completed, you will see the information below.

Image-5

In this article, I tried to explain how the Dynamics Deployment Services Account is authorized over Azure, which is one of the necessary steps to deploy a new environment. This step is usually skipped and an error is received in the Deploy operation over LCS. It is useful to give this authorization beforehand.

Regards.

www.fatihdemirci.net

TAGs: Microsoft Life Cycle Services, Dynamics Deployment Services Account, LCS, Azure, Azure DevOps, Project onboarding, 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 deploy a new X++ development VM for Dynamics 365 Finance and Operations?

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

How to deploy a new Build environment for Dynamics 365 Finance and Operations?

In this article, I will try to explain step by step how to deploy a new Build type virtual machine for Dynamics 365 Finance and Operations.

Before you start, if you have a customer adaptation project, it is recommended to set the SandBox Develop And Test environment that appears here as Build. Because the admin login authorization to this environment will soon be removed and it will not be possible to use it for development. Therefore, it is useful to set it as Build. In addition, thanks to an Agent that will be released soon, we will be able to Build without allocating an entire VM.

In this example, you will see how to create a new Build machine via Cloud-hosted environment. It has the same steps as Sandbox, so it will be a post that will cover both. 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 Build 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 Build, you should choose DevTest.

Image-4

There are two options here. First one is used for Build or Test. For development, you should select Develop. We will choose the one 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  or DS12 V2 machines that are recommended For you, but if you want it to be a little faster and money is not an issue, choose D13. 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. Build Agent Name is the name you will see in Azure DevOps. You should give it an appropriate name. The most important part is the Branch Name. I typed Main here. It is case sensitive, so it is necessary to type Branch name correctly.

Image-7

There is no need for Demo data for the Build environment, you can remove it from here.

Image-8

You can name your virtual machine in this section.

Image-9

Settings are done. Continue with Next. I selected D12 V2 for the For you. However the picture shows D13. Recommended dimension is D12 and its derivatives.

Image-10

The confirmation screen will appear. When you click Deploy, the Build environment will be queued to be deployed. This process is completed in 3-6 hours.

Image-11

In this article, I tried to briefly explain how to deploy a new Build machine and I will explain how to Build in my next articles. I will try to explain how the resulting packages are transferred to the test and live. I hope it is useful for you.

Regards.

www.fatihdemirci.net

TAGs: Build VM, Lifecycle Services, LCS, Azure DevOps, X++, 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

How to create a new Azure Devops account and connect to Lifecycle Services (LCS) Dynamics 365 Finance and Operations project.

In this article, I will try to explain how to create a new Azure DevOps account, start a new project and connect it to Lifecycle Services. Since I did not have a new account while preparing this article, I used some pictures from old projects. However, I think it will be enough to make my point.

If you already have an account, you can use it. If not, you can start creating a new Azure DevOps account with a new mail using the Start free button on the screen below.

Image-1

First, you will pass certain steps and reach the Organization step. If you are making this installation for a customer or company, it is useful to use an appropriate mail and give the names correctly. You can choose where the project will be hosted. It makes more sense for us to choose Europe.

Image-2

When you continue, the screen below will appear. Click on Organization Settings.

Image-3

Since Lifecycle Services supports the old URL format, here you need to turn off Use the new URL.

Image-4

After this step, your account will be ready. If you already have an account like I do, you can log in directly and go to the project page. Start creating a new project with the New Project button.

Image-5

The name and description of the project is very important. We usually choose Private projects. There are two options in Version Control. Git is not officially supported but I’ve seen projects using it. We select TFVC. In the Work Item Process section, you can set up a project and choose the one that suits your methodology.  When you click on the Create button, the project will be created.

Image-6

You need to create a Personal Access token from user settings. Click the path shown below to open the Personal Access token creation page.

Image-7

Click on New Token to open a new Token creation page.

Image-8

We define its name and authorization. Currently the longest duration it can be created for is 1 year. It is useful to give it full control.

Image-9

When you click Create, a new Token will be created and a screen like the one below will appear. It is not possible to reopen this page, so make sure to copy and note the Token created.

Image-10

When you select your Lifecycle Services login project, if you click the Azure DevOps link from the hamburger menu, you open the page with a setup link.

Image-11

When you click on Setup Visual Studio Team Services, the following page will open. Paste the URL and Token you created here.

Image-12

If there is no problem, you should see the project you created in the list. Select your project and continue.

Image-13

Automatic relationships are established between Azure DevOps steps and LCS steps. If you want to change them, you can, but it is OK to continue with the initial ones. Click Save to complete the connection.

Image-14

In this article, I tried to explain how Azure DevOps and Lifecycle Services are connected. These topics are new for old X++ software developers like me, but it is really easy to adapt and you may even think that it is too late when you consider the possibilities.

Regards.

www.fatihdemirci.net

TAGs: Lifecycle Services, LCS, Azure, Azure DevOps, Project onboarding, Microsoft Dynamics 365, MsDyn365FO, MsDyn365CE, MsDyn365, what is Dynamics 365, Personal Access token

What is Dynamics 365 Finance and Operations Data Entity and how is it created?

In this article, I will try to explain what the Data Entity is and how it is created with X++. First, let’s talk about what Data Entity is.

Data Entity: We can summarize it as a meaningful data set. Especially with Ax2012, the data structure was divided into many tables in accordance with the normalization logic. For this reason, many tables need to come together in order to see certain data and to perform operations. Data Entity allows us to bring these data sources together and perform transactions over a meaningful data set. As in our example, we have 3 tables related to the book, and these are actually an interrelated Data Entity and we can see these tables in a single structure and take action.

It has a lot of usage areas. I will try to explain them in time. Let’s learn how to create a new Data Entity from Visual Studio.  I created a sample library project for my YouTube channel. I will continue on that.

  1. Right click on the project and select Add > New item to open the Add New Item dialog.
  2. Select Data Model > Data Entity and define the name Data Entity.
  3. Click Add and open the Data entity wizard.

Image-1

Select the main data source from the Primary datasource field. There are many automatic definitions.  There are five options in the Entity Category field. You can select one of them depending on the type of your data.

  1. Parameter: Used for parameter data.
  2. Reference: Used for reference data. Such as units, dimensions.
  3. Master: Used for master data. Such as Customer, Supplier, Stock etc.
  4. Document: Used for study data. Such as sales order and logs.
  5. 5. Transaction: Used for transactional data. Such as customer transactions.

Image-2

In our example, I chose Master since the main Data Entity will consist of master data. Click Next to proceed.

Image-3

Here there are the fields of the table we selected as the data source. We can check or uncheck the ones we want. In addition, features such as Label Is Mandatory come from the automatic table. You can change them if you want.

Image-4

Open a new data source selection window by clicking the Add Data Source button.

Image-5

Select the DmrAuthorTable table from the window that opens. Relation is required for the connection of tables, so select that too.

Image-6

When we add the new data source with Add, the following image appears. Now you can add and remove the fields of the new table.

Image-7

When you click Finish, Data Entity will be created. The fields and data sources we have selected have been created. We can also edit from here. 

Image-8

To add one more data source, right click and select Add New Data Source. Add the DmrBookCategory table. I can do the operations I just made on the screen from here as well.

Image-9

After adding it, define the table name and relationships. Then, right click Fields and select Add New Fields.  Add a field from the DmrBookCategory table.

Image-10

Data Entity is created. It is ready to use. Of course, there are many other features besides these, I will try to talk about them over time. Here, especially if you use Is Read Only in operations such as data transfer, you should definitely set it to Yes. The default value is No. It’s easy to miss. Be aware of that, otherwise you will have a hard time.

Image-11

In this article, I tried to explain what Data Entity is and how to create a new Data Entity. I will continue to explain Data Entities, which have many uses.

Regards.

www.fatihdemirci.net

TAGs: Data Entity, LCS, Azure, 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

Page 13 of 14« First...1011121314

Türkiye'nin en doğru, dolu dolu ve hatasız anlatımları ile teknik yazılarına, makalelerine, video'larına, seminerlerine, forum sayfasına ve sektörün önde gelenlerine ulaşabileceğiniz teknik topluluğu, MSHOWTO