Artika Dutt

Overview I have been preparing for the PL400 example and thought to share my learnings with this. In this article I will be giving you a brief overview of the components of Power Platform which are based on the learning materials available on the Microsoft certifications site. Power Platform uses environments to store, manage and share data for an organization. For every new environment a dataverse instance is created which will host the Database.  This will be then be utilized across other technologies, such as Apps and Flows For administrative requires use the Power Platform admin center Includes the following; Other portals - Power Automate - for automated flow - Power BI - for reports - Power Virtual Agents - for chatbots - Power Pages - for websites Security - Has policies an procedures for data loss prevention to prevent organizations from unintentionally exposing data Connectors are as follows - Non - Business - for data related to personal use. Default (data from here can b...

This article explains how to create a periodic task or batch job within Dynamics 365 for Finance and Operations using  SysOperationServiceController As part of this example, I will be creating a simple periodic task that requires parameter input from user. To achieve this we need to create the following elements Data contract class UI Builder class (only recommend if you need custom UI fields) Service class Controller class Action menu item Data contract This class is required for handling user data. All parameters defined in this class will be rendered as parameters within the batch job dialog in UI.  Class declaration DataContract Attribute Required to mark this class as a data contract class. SysOperationContractProcessing Attribute Specify the UI builder class within the SysOperationContractProcessing attribute to register the UI builder with the data contract (This is only required if you have a UI builder class. This step is optional and can be skipped) Parameters D...

D365FO - Create a multi-select lookup in batch jobs In this article, I will be describing how we can create a multi-select lookup for display within the batch job dialog. Contract class Create a new variable of type 'List'. This will store the selected values of the user for the dropdown from the dialog. Create a parm method to access the new list object Ensure to specify the DataMember attribute Add an appropriate label Specify the data type for the list's content Ensure to specify the DataContract and SysOperationContactProcessing attributes above the class declaration. An UI builder is also required. The requirements for this is explained in the next section. Example: UI builder class Create an UI builder class that extends SrsReportDataContractUIBuilder Add a new variable of type 'DialogField'. This will be displayed on the UI for user. Implement the postBuild method. Initialize the contract from this.dataContractObject() and bind the dialog field variable to th...

In this article I will be going over how we can setup a git repository for managing our customizations for D365 FinOps within Azure DevOps. Create a new model This step is only required for the purpose of this article. If you already have an existing model you can use that for further steps.  See this article for details on how to create a new model. D365 FinOps Creating, updating, deleting and deploying model For example,  Copy the contents of the model folder created with your AOSSerive/PackagesLocalDirectory folder and store it somewhere. We will use this later to upload the contents of the model to git source control. Remove the model from the environment so that it longer exists under AOSSerive/PackagesLocalDirectory. This is so that we can clone the source controlled version of the model on this location.  Setting up a GIT repository Navigate to your Azure DevOps project and click on the repos tab page. Click on new repository Provide an appropriate name for your re...

 I have given a brief description of a model in my previous article . In this article I will be giving an overview of how we can create, modify, remove and deploy a FinOps model.  Note: The instructions in this article are for a FinOps development environment that has the dynamics 365 extensions enabled on Visual Studio Studio  2019. The location of the Dynamics 365 menu may differ in other versions of Visual Studio.  Create a new model file  Open Visual Studio in admin mode Navigate to Extensions > Dynamics 365 Select Model Management > Create model Enter the model details Model name - the name of the model, for example, MyNewModel Model publisher  - the name of the model publisher, for example Artika Dutt Layer - this represents the level you intend for your deployment. If you are a Microsoft partner then choose isv. If you are performing development for a customer then choose cus layer. If you are developing for users then choose usr.  See t...