Quantcast
Channel: Microsoft Dynamics CRM
Viewing all 71679 articles
Browse latest View live

Blog Post: Interacting with Power Automate Flows

$
0
0
Introduction It is well-known that Power Automate is a low-code, no-code solution to automation with various triggers that it supports including Event driven, HTTP request, Timer/Scheduled and Manual flows. Manual/Button flows help in designing powerful Canvas Apps that can offload complex logic executions to flow while focusing on user experience of the app. In this article we will discuss an example to call a flow and pass user inputs received in Canvas Apps to the flow – have the logic execute there and return resulting value to the Canvas Apps for display. In this example, we have a canvas app that accepts requested meeting time, the app then calls the flow to check availability for the said time, if the time slot is unavailable, it will return false to app to notify the user accordingly. I have shared the key settings to achieve this by using Case entity from Dynamics 365 CRM. A quick design of the entry form is given below: Note the customer field when placed on form does not show up the field on Canvas for data entry. Lookup fields are not currently supported. Here is how I got this to work: Select the Data card created for Customer when you include that field on the form from tree view and then choose Insert Drop Down. Set the properties of the drop-down as shown below: Items = Sort(Accounts,’Account Name’) – This will show the list of accounts sorted by name. With the Customer_DataCard3 still selected in the tree view add a Label and set the name to ‘Customer’. With this done, we now get the drop down of accounts listed. However, the value selected in the drop-down will not be submitted as the value for Customer Card and therefore will not be saved in database when we submit the form. To be able to edit the property to the Card, we need to first Unlock it by clicking on lock icon. Next, we edit the Update property of card to set the value as Dropdown1.Selected as shown below: With this done, any change in the value of dropdown will bind the selected value to the customer property. Next let’s work on designing the Power Automate Flow that need to call to check availability. For this, choose the OnSelect property of Request button and choose Action à Power Automate to bring up the following screen. As we do not have our flow already designed, we choose ‘Create a new flow’ which navigates us to the flow designer. Type PowerApps in the connector search bar and select the PowerApps trigger. This would be the trigger to be used to invoke the flow from Canvas Apps. Do note that only flows that are based on PowerApps trigger would show up in the Power Automate action list for selection. Here is a screenshot of a very simple flow designed for this blog. In order to generate a parameter for the flow, choose the ‘Ask in PowerApps’ option from Dynamic content. This will auto generate a parameter for you for the base time field as shown below. In order to return a value back to the calling App use the action ‘Respond to a PowerApp or flow’. Now set the value you need to return. Define the data type that you want to return by clicking on ‘Add an output’. Note that you could return more than one value back to the calling App. It is received in the calling app in the form of a record with each output parameter name as a field in that record. Save the flow and now let’s move back to the canvas app to call this in our app. On the Request button in canvas app, we pass the date value selected in the First Response By field and send it to the flow as a parameter for evaluating availability. The flow returns a Boolean value based on its evaluation. Set the following on the OnSelect property of Request button. Set(Available, ‘PowerApp->Performanunboundaction,RespondtoaPowerApporflow’.Run(‘First Response By_DataCard1’.Update));If(Available.result,SubmitForm(Form1);NewForm(Form1), Notify(“Invalid date entered”)); Using Set() function we are storing the return value from the Flow to the variable named Available. ‘PowerApp->Performanunboundaction,RespondtoaPowerApporflow’.Run(‘First Response By_DataCard1’.Update)) In the above statement, we make a call to the Power Automate Flow and pass the value of the First Response By field. Notice, we access the output parameter returned from flow as Available.result – where result is name of the output parameter defined. This now completes the canvas app, and you are ready to test it by entering values in the app. Notes: Begin designing the canvas app and flow from within the context of a solution Work with the Common Data Service (Current) connector. When Perform Unbound Action action is added, we are unable to invoke the flow from the Canvas Apps, hopefully that would be fixed soon. Conclusion In this way, we would be able to design a Canvas App (no-code) and have the business logic execute written as a Custom Action (pro-dev) by using a (no-code/low-code) Flow – The no-cliff solution to building powerful apps.

Forum Post: RE: How to format link properly in Create HTML table in Ms flow?

$
0
0
Hello, Check solution from this post - powerusers.microsoft.com/.../56069

Forum Post: RE: Is there any Typescript/JavaScript & Mocking Test framework suitable for Dynamics CRM?

$
0
0
Hello, You can use FakeXrmJs for that purpose - github.com/.../fake-xrm-easy-js and examples are here - https://github.com/jordimontana82/fake-xrm-easy-js-samples

Forum Post: RE: Custom button is not visible on Dashboard UCI

$
0
0
Hello, Looks like a bug for me. Get in touch with Microsoft, open a ticket and let them help you.

Forum Post: RE: Auto Number Attritube in CRM

$
0
0
Hello Nikita, Please refer to this link: https://community.dynamics.com/crm/b/passiondynamics/posts/create-auto-number-attribute-in-dynamics-crm-365-using-web-api-use-postman-with-crm-online Hope it will help you..

Forum Post: RE: Is there any Typescript/JavaScript & Mocking Test framework suitable for Dynamics CRM?

$
0
0
Hi Abdul, AS we know fake xrm easy testing framework is useful to test the plugins. Regards, Thangamani

Forum Post: Retrieve Entity EntitySetName from Entity DispayName in Javascript

$
0
0
Dear Experts , I am trying to retrieve the EntitySetName from its Dispaly name using Webapi call, below is the query i am using which is giving the error. Query: Xrm.WebApi.retrieveMultipleRecords("EntityDefinitions", "?$select=DisplayName,EntitySetName&$filter=DisplayName eq Microsoft.Dynamics.CRM.Label'person'").then( Error. "The string 'Microsoft.Dynamics.CRM.EntitySetName.LocalizedLabel.Label'person'' is not a valid enumeration type constant.". CRM Version :- D365 v9.0 any help will me appreciated. Regards

Forum Post: The boolean "isdisabled" of the SystemUser Entity is null and I can't change it back

$
0
0
Hello, I have tried to change with Javascript console the value of the field "isdisabled" of the SystemUser Entity, but I got an error and it has set the value of the field to null. When I try to change it back with Javascript, C# or anything else, I get an "Unexpected Error" (object reference not set to an instance of an object). I have also tried to remove the user licence and put it back, but the value is still null. I'm stuck with this... Have you any idea ? Thanks

Forum Post: RE: Upgrade from 8.2 to 9.0 fails with "'Attribute' metadata entity doesn't contain metadata attribute with Name = 'autonumberformat'"

$
0
0
Same issue here when i tried importing an organisation. This worked fine before I updated the farm to CRM version 9.0.10.11

Forum Post: RE: Pending send emails when user manually creates messages

$
0
0
Hi Michael, Can you check the Alerts on one of the affected mailboxes? You can check that by going in Settings > Email Configuration > Mailboxes > Open one of the affected mailboxes > Alerts ( under Related section )

Forum Post: Can not filter on Expanded fields using Web API O-DATA 4.0 Dynamics CRM 365 v9.0

$
0
0
hello every one, Im on D365 v9.0 , and i'm working with Web API, it's working fine for simple retrieve or post requests. Now i am trying to apply filter on a field of a related entity as shown below. i have tried all the combinaisons that've found on the internet but i am always getting bad request. can any one tell me what's wrong with the following request? https:/URL /api/data/v8.2/incidents ?$select=_new_contact_value &$expand=new_contact($select=firstname) &$filter=new_contact/firstname eq 'contact1' Thanks,

Forum Post: RE: Dynamics Portal Mobile Entity form display overflow

$
0
0
Hi Davey, Because the element is an , it won't really support multiple lines. In this situation, I'd use CSS to hide the original input, and then use JavaScript copy the value into a new div where you have more control over the styling. Hope that helps. Nick

Forum Post: RE: Can not filter on Expanded fields using Web API O-DATA 4.0 Dynamics CRM 365 v9.0

$
0
0
Hello, Here is what possible - docs.microsoft.com/.../gg334767(v=crm.8) If you have complex query I would recommend to use fetchXml instead - docs.microsoft.com/.../mt607533(v=crm.8)

Forum Post: RE: Dynamics 365 App for Outlook: Disable Feature Add an email recipient as a contact or lead

$
0
0
Please let me know if there is any latest update on this. We want to remove " Add an email recipient as a contact / account / lead" in the Dynamics 365 App for Outlook?

Blog Post: Want to be notified when a contact is no longer with company?

$
0
0
Knowing if a contact is no longer with a company can help you in many ways Proactively identifying when a buyer has left an open opportunity to help you spot deals at risc Identifying opportunities when customers (potential champions) have joined new companies Identifying all potential out-of-date contacts With the new Data Validation integration between Dynamics 365 and LinkedIn Sales Navigator you will know when a contact is no longer with a company. Contacts who update their employer on LinkedIn will be automatically marked with a “Not at Company Flag” field in Dynamics 365 and can be used to trigger different Dynamics 365 activities to keep Dynamics 365 records updated. The Not at Company Flag The primary feature of Data Validation is the “Not at Company Flag,” which is a newly-created contact record field written into Dynamics 365, that flags if certain contacts are no longer with their company. Data Validation leverages the “ CRM Sync ” integration of LinkedIn Sales Navigator (LISN) to match Dynamics 365 contact and account with LinkedIn Member Profiles and LinkedIn Company Profiles, respectively. When a current company on the LinkedIn Member Profile does not match the account the contact is related to, LinkedIn will return “Not at Company” to the “Not at Company Flag” field associated with the contact entity. If there is no feedback to share (e.g. no match, or confirmed still at company), the field value will remain its default state of “No Feedback.” LinkedIn will examine whether there was a change on the Dynamics 365 contact entity or on the LinkedIn Member Profile every 24 hours – if there is, it will re-run validation and update the field value. Making sure you are notified proactively It’s good that a field on a contact is automatically updated, but what if you don’t notice the update, and miss a vital window of opportunity? Leveraging the brilliant Assistant Card capabilities in Dynamics 365 Sales Insights, together wiht the equally brilliant Power Automate service, you can make sure you will be notified proactively – with an Assistant Card surfaced in the Relationship Assistant widget in your dashboard. You can display information like when the signal was receieved, contact name, company name etc. The Flow in brief To surface an Assistant Card you can build a Flow in Power Automate (previously known as Microsoft Flow) The trigger of the Flow will be when a contact is updated, and the result will be an Assistant Card. In brief the Flow will consist of these five elements Trigger – When a specific field on a Dynamics 365 contact is updated Condition – If that field has a specific value Get local time -if yes- Get account of contact Create Card for Assistant Building the Flow To create the flow navigate to Power Automate > select the environment (1) > click My flows (2) > click + New (3) > select Automated — from blank (4), and then in the Build an automated flow dialog select When a record is updated (common data service) (5) Trigger The flow starts with the “When a record is updated” trigger. In the trigger fill out the blanks according to the below screenshot For environment pick your environment (your instance) For entity name select Contacts For scope select Organization To ensure that the trigger only fires when the “Not at Company Flag” is updated expand the Show advanced options section select the field msdyn_orghangestatus in the dropdown Condition Add a condition action, and select the “Not at Company Flag Value” for the value. Select “is equal to” for the operator, and 1 (one) for the value (1 is the value corresponding to “Not at Company” in the option set) If Yes – overview If the condition Not at Company Flag value = 1 is met we will want to Get local time Get the account of the contact Create Card for Assistant a. Build text fields (Card Header and Text) b. Define actions (button clicked) c. Define variables (Show Where, Show until) Get local time All times in Microsoft Power Automate (aka Flow) are in Universal Time (aka, UTC or GMT) by default. If we will want to display when the change was detected (signal was received) to the user in her local time, we will leverage the Convert time zone action ( link ) to convert to the local time zone Get account In order to display the company name of the contact triggering the flow in the subsequent Assistant Card, we must get the account of the contact from Dynamics 365 We will invoke the Get record action to get the Account of the contact, using the Company Name identifier of the contact Create Card for Assistant Having decided that the conditions for displaying an Assistant Card are met, and having gathered the necessary information, we can go ahead an create the card For the Create Card for the Assistant action we will define the parameters below Defining parameters means 1: Build strings for Card Header and Text 2: Define expressions … leveraging the “Add dynamic content from the apps and connectors used in this flow.” dialog as seen to the right of the following screenshot So lets dig into the some of parameters Card header Type your static text (eg ‘Signal from’ and then add the variable field for converted time. Find the variable for the converted time at the very end of the field picker Card Text Add the static text and fields you see fit Show until Create an expression to control for how long the Assistant Card should be visible (eg 4 days) Open button For the Open button define what you will want to happen if the user clicks is. I’ve selected ‘Open entity’ for the button type and then the Contact Identifier for the record ID that the button should open. Complete Card So the complete card should look something like the below. The remaining steps is to test and publish your Flow, after which you see an Assistant Card in your Relationship Assistant widget on your dashboard when a contact changes company. You could also instruct the Open button to open the contacts account. Having opened the account you can click Open Org Chart. On the org chart you will notice a red dot on the contacts for which the company information may be outdated. You can click one of those contacts to open a task pane in which you can see the company name LinkedIn has on file for the contact, and update your Dynamics 365 info accordingly Enjoy the Dynamics 365 and LinkedIn Sales Navigator information and stay in the know.

Blog Post: Power Pizza: Form Modes

$
0
0
We are in the middle of a Power Pizza Blog Series ! I am walking through lessons learned while building a Power App to track your Pizza Crawls. This will allow your friends to submit their locations, enter ratings and view the winner. Finally, a scientific solution for finding the best pizza! Pizza Crawl Stop #2: Fireworks Pizza, Arlington One of the first challenges I faced with my Power App was the Form Mode. I created the app based off my Common Data Service data. So this automatically created a Gallery page, a view page, and an edit page. The Problem Of course as I am working away and testing sparingly, I rename pages and change navigation links and forget what things used to be. So I was struggling with why I was putting data into this form that was not saving. Then I noticed that the data was saving on that form but the form was not clearing. I was trying many different ways to clear the form or make sure it was submitting. The Solution Finally I realized the issue was that I was using an Edit form not a New form. To check this, select the Form and review the properties. Then you can change the Display Mode to either New (create a new form, submit at the end), Edit (change an existing record), or View (look at data). Power Apps Form Default Mode Form Default Mode Options I would then recommend you re-name everything to fit with the form label. This will keep you less confused. You will notice I did not do that in my screenshot because I enjoy making my life just a bit harder for myself each day. This was a small, quick change but it resolved several issues. I included a few forms so after discovering this setting I was able to easily verify all were set up as I wanted them to be. Tune in tomorrow to learn about other silly mistakes I made on this Power App and how you can avoid them yourself! The post Power Pizza: Form Modes appeared first on Kylie Kiser .

Forum Post: RE: Portals: Redirect not working

$
0
0
Even, if the question is old, i had the same problem and solved it in my case: i have multi language enabled and have to set the full path including the locale, so instead of inbound url /whattoredirect i have to use as inbound inbound /de-DE/whattoredirect - this works for me (and is not bad as i have the opportunity to root diffrent languages to diffrent path (which is of course also rubbish, as the target will be invoked by the current language :-) ))

Forum Post: RE: Dynamics 365 v9 OnPremise Upgrade Fail

$
0
0
I'm getting this error,: Details: Failed to load solution Marketing Sales Patch, version: 9.0.4.3602. See the log file except it's failing to load solution Sales i.e. msdynce_Sales

Forum Post: RE: Unable to delete a Record Creation and Update Rule

$
0
0
Hi GordonJohnston, Additional troubleshooting and further details will be required to troubleshoot this. I would recommend to raise a support request with us to get this resolved / get that Workflow removed.

Forum Post: RE: Customize close opportunity form => Quick create not showing

$
0
0
I am having a similar issue, however i followed what was recommended and now i am receiving a different error. Is there something more i need to do in order to have the quick create form load instead of the dialog box? I have verified that the customize opp close option is selected to yes. Thanks in advance!
Viewing all 71679 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>