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

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

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

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

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 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