Hi Everyone,Awaited moment is here, we finally have Power Apps designated application for Windows. Currently its in Preview so use only for testing as of now until its pushed globally. Here’s the steps to download and use Power Apps for Windows Step 1: Go to Microsoft Store and search “Power Apps” Step 2: Install the application. Step 3: In order to run this application, we need to check WebView2 Runtime version on our device. It should be version 99.0 or later. To check this, go to Settings > Apps > Apps & features. Search for WebView and verify that you have version 99.0 or later installed. For those who don’t have this, follow below steps. To install WebView2 Runtime, download the WebView2 Runtime. Download version 99.0 or later. Installing an earlier version may cause Power Apps to crash. Under Evergreen Bootstrapper, select Download. Go over the license terms and privacy statement and then select Accept and Download. When the download is complete, then run the MicroEdgeWebview2Setup.exe. Step 4: Open and sign-in with your ID Step 5: After logging in, you will find list of Model and Canvas Apps that are shared to you or you having access by security roles. The screen will show all Apps from all the environments present in you tenant. You can also see other model-driven apps if you enable Show non-production apps in settings under Model Apps. That’s all about installing Power Apps on Windows. Find the Microsoft Documentation for Installing – Microsoft Docs Find the Usage of Power Apps Windows – Microsoft Docs List of known issues – Microsoft Docs Hope this was informative and helped you.

I have a contact record with a role option set field with options Billing, Decision Maker, Client, Influencer.  The Requirement is to only show billing contacts i.e. contacts with role billing related to the account selected on the Opportunity in the lookup of the contacts on the Opportunities.  Let’s see how I to filtered the contacts lookup to just show billing contacts :   Step 1:  Create a contacts view such that the role is billing(or any field on which you want to filter is set to the value by which you want to filter that record ).  Step 2:  Set the filter criteria of the contacts lookup field on the opportunity as shown below.  In the Additional properties  turn of the view selector and set the default view to the view you created in #1Step 1  In the Field Behavior Tick the “disable most recently used items for this field”.  Now you will only see contacts with role billing in the lookup of the contacts on the opportunity form.  Hope this helps!   Thank you. 

In this blog we will see the steps in order to send a automated message via Teams as soon as an Opportunity is created in Microsoft Dynamics 365. Step 1: Go to portal.azure.com and select the Azure Logic App Resource. Step 2: Enter all the details such as the Name, Resource Group, Subscription, Region, etc. required while creating a Logic App. Step 3: Select the Dynamics 365 trigger When a record is updated. Step 4: Select Opportunities entity after setting by the Dynamics 365 CRM connection Step 5: Set the data refresh time as required. Step 6: Select the IF action in the next step and the condition would be status_label=won for true. Step 7: Inside True Block select Post a message in a chat or channel option. You can also handle the condition for False block, but in this case we can leave it blank. Step 8: You can post this message in a Group, Channel or send it as a Personal chat. Step 10: Wait for the trigger successful notification. Step 11: Go to Dynamics 365 CRM and navigate to opportunities entity. Step 12: Open a test opportunity or create one if doesn’t exist and close the opportunity as won. Step 13: As soon as you closed this opportunity you may have received the following message. Hence in this blog we saw how we can send messages on MS Teams using Azure Logic Apps on triggering certain conditions. Hope this helped!

Hello,Consider a scenario where we need to have a table (entity) which is a replica of other table or you need some fields replicated into another table. This tool will save a lot of precious time. Let’s say I have a table called ‘Scoping’ and I want fields from that data replicated into another table called ‘ScopingClone’. Steps you’ll take to do this in a time-efficient manner. Step 1: Create a new Table/Entity. (In my case, I created ScopingClone) Step 2: Navigate to XrmToolBox and install ‘Clone Field Definitions‘, connect to your environment and open the tool. As you can see, the fields that I selected are successfully cloned. I hope you found this blog useful.

In this blog we will see how we can open a PDF document on click of button from a record in CRM Let say we have User Guide button on Lead Entity and on click of User Guide button, a PDF document which is User Guide document should be open in next tab. Solution Create a solution and add lead entity only. Then open the same solution in XRM Toolbox – Ribbon Workbench var openUserGuide = { //openUserGuide.userGuide userGuide: function () { “use strict”; Xrm.Navigation.openUrl(“https://sinerleak.sharepoint.com/:b:/s/SingerLewak/EaQO2OWjWA1BnHFCCENV-6EBDkILbg3EfPSFLEu-KCeraw?e=ofVyVB”); } } 4. Add action to command and Publish the solution from XRM Toolbox Output –

Introduction Autonumbering feature is useful to uniquely identify records and comes in handy when there are many records to filter. This blog will be the walkthrough for steps need to be performed in order to enable the auto numbering for field service entities. Lets take a scenario, there is a need to auto number the Work Order entity. So, let’s begin with the steps to configure the same. Step 1: Navigate to ‘Field Service Setting’ area and click on ‘Auto-Numbering’ button on ribbon bar. Now we can enable the auto numbering for Work Order entity. Click on ‘# Auto Numbering’ button. Step 2: This will open the pop-up window to Configure Auto-Numbering and ask you to select the entity for which you want to enable the auto numbering. So, select Work Order from the drop-down list. Step 3: Enter other configuration details as shown in the below screenshot. Let’s consider that we have 2000 existing work orders in CRM. The numbering for next work orders should start from 2001 with Field Service Auto numbering. For this we need to specify the Starting Number as ‘2001’. Click on ‘Apply’ in order to apply the changes. Step7: After clicking on Apply a message will be displayed — ‘Work Order settings have been successfully updated’. Now, Work Orders are ready for auto numbering and whenever new Work Order is created, Work Order number will be auto numbered from ‘2001’ since we have provided Starting Number as ‘2001’ in the configuration. Conclusion ‘Auto Numbering’ feature allows us to auto number the field service entities in field service and avoid duplicate records in CRM.

Introduction: Let’s say we want to set an icon for a button on a form in Dynamics 365. We will use the Ribbon Workbench to do this. Let’s add this to our Quote form. First, create a solution and add Quote Entity: To add buttons, we will use SVG images. For the Web Client, we will use PNG images. There are online tools ( https://www.iconfinder.com/) to download these 2 formats. Let’s create a Approval button with approval images and save it as a Web Resource. PNG file: SVG file: Now open the Ribbon Workbench: Add a new button to the Form, and add the PNG and SVG images from above. The PNG images are Image 16 and Image 32, and the SVG image is Modern Image, then Publish: Once published, go to the Unified Interface app and pull up an Account. You will see the new button: Hope this helps…

In this blog, we’ll see how to create a button on ribbon by using ribbon workbench in XRM toolbox and on click, open quick create form. Step 1- Insert a ribbon button on any required record form using ribbon workbench on XRM toolbox. Step 2- Name the ribbon button (anything as required) Step 3- Add button properties- Give ID name Label name Icon for the button Step 4- Add the following code to open a quick create form on click of the button var RecordaMeeting = {     //RecordaMeeting.OpenRecord     OpenRecord: function (primaryControl) {         var entityFormOptions = {};         entityFormOptions[“entityName”] = “Add the entity name”;         entityFormOptions[“useQuickCreateForm”] = true;         var formParameters = {};         // Open the form.         Xrm.Navigation.openForm(entityFormOptions, formParameters).then(             function (success) {                 console.log(success);             },             function (error) {                 console.log(error);             });     }, Step 5- After adding the script, add the command for the button- Web resources library name Web resources function name CRM Parameter: PrimaryControl Step 6- Add command on button properties. Step 7- Publish the button. Screenshots of implementation: Step 8- Button appears on the ribbon for the required entity. Step 9- On click of button, quick create form opens. Hope this helps!!

In this blog, I am going to showcase how to create and post statements manually in D365 retail. In Dynamics 365 Commerce, the statement posting process is used to account for the transactions that occur in POS. The statement posting process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ). Steps for creating and posting the statement. Go to Retail and Commerce > Retail and Commerce IT > Distribution schedule. In the list, find and select the desired record. Click Run now. Click OK. Go to Retail and Commerce > Inquiries and reports > Commerce Data Exchange > Upload sessions. Refresh the page. Go to Retail and Commerce > Retail and Commerce IT > POS posting > Validate store transactions. Create the statement This step identifies the store that the statement is manually created for. In the tree, select ‘Contoso Retail\Contoso Retail USA\Central\Houston’. Click Add and Ok. Go to Default dashboard. Go to Retail and Commerce > Channels > Stores > Statements. Click New. In the Store number field, enter or select a value. In the Staff/register field, enter or select a value Format for Staff/register value is Register number: Shift ID Enter the Transactional interval value. Click Calculate statement. Click Yes. In the Counted field, enter a number. Post the statement When you post a statement, sales orders and invoices are created for the sales in the statement. Cash and carry sales are aggregated onto one sales order and are invoiced for the default customer who is assigned to the store. Sales for which a customer was added to the transaction in POS generate separate sales orders and invoices, one for each unique customer. Click Post statement. Once the statement gets posted. You can check that statement in the Posted statement. Retail and Commerce > Inquiries and reports >Posted statements Hope this helps!

In this blog, we will see how to integrate Microsoft Teams with Dynamics 365 for custom entities using Postman. Step 1- Go to portal.azure.com and select Azure Active Directory Step 2- On App Registration, click on new registration  Step 3- Register an application and follow the steps  Name  Select Multitenant  Enter the required URL  Click on register  Step 4- Add API permissions and add a permission. The request API permission window will appear where you need to select Dynamics 365.  Step 5- The permission window appears and select Dynamics 365. Step 6- As you select Dynamics CRM you will be presented the permission window. Select “Delegated permission” and Check the User Impersonation then click Add Permission button.  Step 7- After permissions assigned, Grant admin consent confirmation: Click on yes. Step 8- Go to Manifest and change “allowPublicClient”: true  Step 9- Go to Overview, save client ID  Below table will help out to fill in the values in Postman: Variable Name URL url Dynamics URL Version 9.0 Webapiurl {{url}}/api/data/v{{version}}/ Clientid Client ID (Showed in above screenshot) callbackurl http://localhost authurl https://login.microsoftonline.com/common/oauth2/authorize?resource={{URL}} Step 10- Go to Postman, create a new environment and enter all the details in the table: Step 11- Now connect to the environment from top right most corner Step 12- Then create a new request Step 13- Include the following in body: Put status as: Enable: true and Logical Entity Name: Schema name of the entity. Step 14- Go to Authorization tab. From the Dropdown Select OAuth 2.0. Now we will provide the variable values to generate token. Give a name of token Choose Grant Type Implicit and provide corresponding variables for Callback URL, Authorization URL and Client ID. Then click Get new Access Token. Step 15- Now click on Get New Access Token Step 16 – It will prompt you to login Dynamics 365 after you provide your authentication the token will generate. Step 17- Now click on Use Token Step 18- Click on Send button Step 19- Now, collaborate button will be visible in ribbon for required custom entity Hope this helps!!