Introduction: Here is JavaScript code that you can use to  make the required field show only system user records and also in case you have a requirement to the set the owner of record as default required attendee. Solution: Add below function to your web resource on load event. Conclusion: On load of form the Required attendee will be owner of record and we can add new attendee easily as the dropdown will show only user records. Instead of users, if you need contact records, just change the set entity type->  formContext.getControl(“requiredattendees”).setEntityTypes([“contacts”]);

Introduction: While using Power apps, we might come across situation where we do not want the user to click on the Save button and then move to next screen to fill in child records. In such case we can use timer control to auto save the form and navigate to new screen. Solution: In my Use Case, I have  Order which will be auto saved and then the screen to fill in  order lines will open. Add the timer control on  order form. I have set auto start to yes and the duration to 2seconds, so when my form will load the timer will auto start and run for 2seconds after which it will execute the action OnTimerEnd. 2. I want to submit the form only when the fields have data. So in the formula,  if data is empty, the user will be notified and timer will reset else the form will be submitted, its id will be saved in variable, the form will reset and user will be navigated to next screen. You can modify the formula based on your requirements. I have saved the last submit, so that I can open the same form for further editing on the new screen. Conclusion: You can implement the auto save functionality of CRM in PowerApp by using timer and submit form on timer end.

Problem Statement: We need to update the BPF and move to the next stage using Power Automate. The change to BPF should happen after the DocuSign Envelope is Sent. In our scenario, DocuSign and CRM are not integrated and so we will be using Power Automate to help us achieve the task. Solution: When DocuSign Envelope is sent, trigger Power Automate by using the DocuSign connector. The Envelope event here will be Sent. Since our DocuSign is not integrated with CRM, we cannot complete the update of Opportunity, until we get the Opportunity ID. As a workaround, we have hidden the Quote Id on the Proposal during generation of proposal. On trigger of Power Automate, we extract the Quote ID from the document. To know more about it, you can refer the blog https://www.cloudfronts.com/close-quote-when-docusign-envelope-is-completed-using-power-automate/ In this blog I have directly saved Opportunity ID in Compose Action. To update the business process flow, we need to get the BPF record as below: List the Business Process Flow for the Opportunity ID. Get the Stage Id to which you want to set your business process flow and store in a Compose action. To know how to get Stage Id, refer my blog https://www.cloudfronts.com/get-stage-id-of-business-process-flow-stages/ Store the path traversed by the Opportunity in Compose. You can use the traversed path directly also. Update the BPF record Set the Active Stage and traversed path. Active Stage= processstages(ID of stage you want to set as active) Traversed Path= concat(existing traversed path,’,’,stage id)

Learn the Importance of Azure Service Bus Topic Filters with this Blog.

Learn how to use the SQL and Co-relation Filters for Azure Service Bus Topic Subscription.

Import Bookings is one of the important features provided by PSA for users to do Time Entries quickly and efficiently. An issue faced while using this functionality is the Project Tasks are not imported with the Bookings Records (As Shown in the Image Below). A solution to this issue is two automated flows: To Bring the Project Tasks from Resource Requirements Entity to Bookable Resource Booking. Hence to bring the obtained Project Tasks from Bookable Resource Booking to Time Entries. Let’s Begin with the Implementation of the solution! (Flow To get Project Tasks from Resource Requirements to Bookable Resource Bookings) Step: 1 Bringing Project Tasks from Resource Requirement’s to Bookable Resource Booking. Step: 2 Update the Bookable Recourse Booking Record with the obtained project task. Now we have successfully obtained the Project task in the Bookable Recourse Bookings           Entity from the Resource Requirements, Our Next step is to Take this Project task on the Time Entries. (Flow to get Project Task from Bookable Resource Bookings to Time Entries) Step: 1 Bringing Project Task from Bookable Resource bookings to Time Entries. (Tip : It is better to check if the Project Task Field is empty or not hence we can also put a condition to do so, if the Project Task Field is empty proceed with updating the Project Task field else Terminate.) Step: 2 Get the Project Task from the Bookable Recourse Bookings. Step: 3 Update the Time Entries with the obtained Project task. Step: 4 Import Bookings and there you go you will now be able to see the Project Tasks. Hope this Helps!

Introduction : In this blog we will see how to hide tab using JavaScript. Implementation : Step 1 : Javascript for hiding tab :  Step 2 : Upload script on load of form -> ok -> Save and Publish . Result : Hope this helps

Using Microsoft flow you can automate and organize the flow of data between your Shopify and Microsoft D365 for Finance and Operation This the 1st part of 2. In this, I will show you how customers can be auto-created in D365 for Finance and Operation when it’s created in Shopify. First, log into Shopify as Admin. Navigate to: Settings -> Notifications -> Webhooks (Scroll to the end) -> Create Webhooks and select customer creation, and JSON format. We need a URL for sending customer details, which we will provide later. Now login to power apps or Microsoft automate with D365 account. Navigate to Flows -> New and select Instant from Blank. Now continue as shown in the below screenshots. Here the required URL will be generated after the flow has been saved. Click on the new step and search for Parse JSON. In Content select Body (parameter from previous steps). Now we need JSON schema for customers. You can find a sample Json return response from https://shopify.dev/docs/admin-api/rest/reference/customers/customer?api[version]=2020-04 Copy the response and select Generate from the sample in Powerapps and paste the response. The schema would be now generated. Click on ‘new step’. and search for Dynamics 365 for Fin & Ops. Click on Create record. Select the instance of the environment you want customers in and Entity name ‘CustomerV3’. Now you can place parameters from the previous step (Parse Json) in different fields such as. Mandatory fields that are required to create our customers are Customer account, Currency, Customer group, Company, Organization name. After the values are placed, click on Save at the top right corner. Now expand the first step and a URL will be there. Copy this URL to Shopify webhook and click Save webhook. Now let’s test this. Go to the customer’s section in Shopify and click Add Customer. Write the first name and last name for now and click save. Go to D365 F&O and navigate to All Customers. You should see a new customer created. In the next part, I will show how we can auto-create product in Shopify when created in D365 for Finance and Operation Thank you for reading!

Introduction  – In this blog we will see how can we create new record in editable grid itself. Below is the Time Entry Grid and we wanted to add new row on click on “+” Step 1  : Add  new icon “+” on screen and add patch operation On Select of the new icon. Syntax – Patch(Data source, Defaults(Data Source),{Attribute: value}) Output- Hope this helps!

In this blog we will see how to add Search Box in Canvas App Step 1 –  Add text box in your screen. Hint text – Search Step 2 – Select Gallery and on items of the Gallery write your query Syntax – Search(DataSource,InputText.text,Attributename) for example – Search(‘Safety Checklists’,SearchBox.Text,”mc_name”) Output – Hope this helps !