The post is bit old but still relevant. Need a no code solution to automatically share a record? Use GrantAccess Dataverse unbound action in Power Automate to share a record. Thanks Nishant Rana for re blogging this post.
Sharing Records in CDS/ Dynamics CDS automatically based on a specific action??!!! we used to write Custom Workflow Activity or some kind of plugin to Achieve it which may take some hours to develop deploy and Fix.
Well ! NO CODE 1 Step workflow can achieve this!
By using the Common Data Services ( Current Environment) -> Select Perform Unbound Action
2. Choose Grant Access
3. Now the Target should be entitylogicalname-plurarl(recordid) or entitylogicalname-plurarl/recordid , record if will be pulled from the Dynamic Contents Property
4. PrincipalAccess which needs to be in JSON format, which will include user or team to which the access will be provided and the Access Mask for the Privilege they will be given.
Click on the Command checker to open the window on the side pane, where we can then select our button.
In the command properties tab, we can see our custom enable rule showing an error.
Also here clicking in View rule definition solution layers provides us the detail that this rule has been added as part of an unmanaged layer.
Clicking on the Unmanaged layer further provides us with the definition of the enable rule.
Last year, I already posted a LinkedIn post in which I discovered that there had been an improvement in the UI of Model-driven Apps. This turned out to be part of the 2022 Release Wave 2.
The design is based on Microsoft’s Fluent UI Framework, which is also used in office applications such as Outlook, Word, Excel, and PowerPoint. However, this improvement goes a step further than what was announced last year. This time, elements such as controls, command bar, header, navigation, and grid views have also been tackled. In this blog post, I will make a comparison for each element and share my thoughts on it.
The Wave 2 updates for Power Platform and Dynamics 365 were rolled out to UK between 8th and 10 Oct. After the updates, few of our clients reported that hyperlinks of lookup columns from related table, on a view or subgrid stopped working for them.
To explain the issue in more detail, I created 3 test tables with the name Table A, Table B and Table C. Table A has a lookup column to Table B and Table B has lookup column Table C.
On the Active Table A view, I added the Lookup to B and added the Lookup to C from related Table B, please see the screenshot below
Double clicking on the row or clicking on hyperlink of Name column value opens the Table A record works as expected , same as how it worked on previous versions of the view control.
Clicking on the Table B Record hyperlink also works as expected, it opens the Table B Record.
But, clicking on the Table C Record hyperlink does not open the Table C Record, It used work fine before the Wave 2 update.
I checked if there are any environment/admin settings that would allow us to flip the switch and go back to using the previous version of the view control and did not find any. I also googled and could not find any useful link related to the issue.
Since most of the UCI controls are based on CCF/PCF, I checked if there are any other grid controls and found out there are two read-only grid controls, Read-Only Grid (Default) and Read-Only Grid. The view had the Read-Only Grid Default (This is the latest view control being used by all the views and subgrids) one set, and I changed it to use Read-Only Grid and tested it. It renders the previous version of the grid control and the hyperlink to Record C on the view works as expected.
The Power Platform / Dynamics 365 team @ Microsoft may already know about the issue or will come to know about it and they would most likely fix the hyperlink issue and roll out a patch soon. Until a fix is released, if you or any of your clients’ solution heavily rely on lookup column from a related table added to a view, you can use the workaround I described in this post to go back to the previous version of the grid control.
If you are creating a Custom API and if it is an unbound API to perform any common or global action, and if you selected “Yes” for (Enabled For Workflow), you will get the following errors when you try adding input (Custom API Request Parameter) or output (Custom API Response Property) parameters of type Entity Reference or Entity.
Exception Message:Type “EntityReference” is not supported for workflow-enabled unbound custom API
Exception Message: Type “Entity” is not supported for workflow-enabled custom API
When I got these errors, googled the error message and did not find any link that described the reason for the error but I finally found the doc page that details the limitations of Custom API enable for Workflow. Please see the screenshot from the doc page below
As you can see from the screenshot, you can only use Entity Reference parameter in a bound Custom API when its Enabled for Workflow. And Entity, EntityCollection and String array parameters cannot be used in a Custom API enabled for Workflow, whether it is bound or unbound.
Power Platform Developers who were using the Dynamics 365 Developer toolkit had issues connecting to online Dataverse instances after the regional discovery service was deprecated in June 2021. This toolkit was last updated in 2017 July and its source is not on GitHub. After the regional discover service deprecation this effectively stopped connecting to online instances, and no updates/fixes were published by SDK team. Dynamics 365 community member Mehdi El Amri (XrmTricks) had found a work around and details are on his blog post here. Since its not open source, community members cannot update the toolkit to work with the latest versions of the SDK.
Well, Power Platform SDK team at Microsoft has been busy and they have now published the preview version of the reborn developer toolkit with the name Power Platform Tools for Visual Studio.
I have installed and tested this toolkit and was able to connect to Dataverse, create solutions, plugins, workflows activities and deploy them with no issues. It is still in preview but seems to be working fine for all the features I tested so far. I renamed the VSIX file as zip and checked and compared the file and folder structures of this new toolkit with the old version, most of the structure is same and there are some changes and improvement to work with latest versions of the Dataverse and SDK. So in my view, the old developer toolkit has been reborn with a new name and obviously with some improvement and support for latest version of the SDK.
Its got the exact number and types of templates as the old developer toolkit, they have just been renamed as Power Platform templates
Is it backward compatible?
The preview version is not fully backward compatible and the official documentation states its not backward compatible however, based on the testing I have done so far the Package project seems to be backward compatible and it does not recognise the workflow or plugin projects (Project type GUIDS are different) if you open a solution based on old toolkit in the new extension. The screenshot below is taken when I click on Deploy from package project for a solution based on old toolkit, it only recognises items within the Package project not from the workflow or plugins. We might be able to update the project type GUID for Workflow and Plugins and then if we click Deploy, it may recognise plugins/workflow project types but I have not tried that yet and I will update this post if and when I test this scenario.
Please note you will not see the new templates shown in the screenshot above and you will not be able to create solution or project using them if you have the old developer toolkit installed for the same Visual Studio version. You have to uninstall the old developer toolkit extension to be able to see the new templates. I hope the SDK team will look into and improve so that we can have both toolkits installed side by side.
Because I am working with many projects that are based on old developer toolkit, I have VS 2015 and 2019 in one setup where 2015 has the old developer toolkit installed and 2019 has the latest Power Platform Tools extension installed. I have also tested another scenario where VS 2019 Enterprise and Pro versions installed and installed the new toolkit on Enterprise version and old on Pro and that combination seems to work fine as well.
Screenshots from the toolkit – old UI elements have been renamed
“Survey respondents can partially fill in a long survey, pause it, and then resume later to complete it. This functionality allows respondents to take their own time and complete the survey at their own pace. “
Auto prefill answer enables survey owners to prefill survey answer based on the survey respondent’s information from Azure Active Directory (for example, prefill a user’s email address when a question asks for email) or Dynamics 365 (for example, last product purchased by the customer).
Dynamics 365 Customer Voice provides out-of-the-box survey response trigger for custom follow-up workflow actions. This will trigger Power Automate flows whenever a survey response is received. Users can use the survey response values in the follow-up actions in a flow.
Survey authors can specify whether to accept partial response in which any unsubmitted answers are collected and reported. When survey respondents submit the survey, the partial response is updated with the final response.
Dynamics 365 Customer Voice automatically categorizes text responses into different categories, which helps a user to quickly determine the key areas customers are talking about and the distribution of sentiments based on these areas.
03.Simplified survey authoring
Simple-to-use experience to create personalized surveys based on customer information from your business application.
Survey authors can upload a .csv file with contact information and use any contact attribute to personalize survey questions and survey invitations. Changes to the contact information can be updated directly in Dynamics 365 Customer Voice.
Cascading question enables survey owners to upload a list of related answers (such as country, city, and state) and create questions that automatically filter the answer options based on a survey respondent’s previous answer. For example, if you select United States as an answer to a question about country, the next question shows only the list of US states.
04. Survey Administration
Enable administrators to manage survey usage in the organization.
Dynamics 365 Customer Voice supports an organization’s administrators to configure a sender’s email address to use the organization’s email address instead of the default Dynamics 365 Customer Voice email address.
Designing the look and feel of your survey to match your organization’s branding is not only important to make your survey look professional but also to provide trust to your survey recipients. Your customers are more likely to open and respond to the survey if it looks familiar. Dynamics 365 Customer Voice makes it easy for survey authors to configure the survey look and feel by customizing the survey header.
Dynamics 365 Customer Voice supports a built-in over-survey management policy to prevent customers from getting too many surveys. As an administrator, you can specify the time between sending surveys. Any surveys sent during the specified time are stopped and the survey owner is warned for over-surveying risks. Administrators can specify whether a survey owner can proceed with sending the survey after the warning.
As part of 2021 Wave 1 updates, a new feature will be added to allow System Administrators and System Customizers to configure if they want to allow a Resolved or Cancelled case to be updated using APIs, Flows or Plugins. This will be a very handy feature as we could avoid unnecessary opening and closing Case records to update fields on the Case record. The release plan does not mention classic workflow, but I do not see why we wont be able to perform the update using classic workflow / action if the record is unlocked at platform level. Please note the end user behaviours will still be the same, a read only Case record (Resolved / Cancelled) cannot be updated from UI.
Public Preview – Not Announced | Early Access – Not Announced | General Availability – April 2021
“Administrators and customizers can now update case information by using Power Automate flows, APIs, or a plug-in for cases that are in the resolved or cancelled status. The user experience on the case form will continue to be read-only.”
Schedule : 2021 Wave 1 features are released between April 2021 and September 2021 and previews and early access made made available before the GA date
Products Area Covered : Power BI, Power Apps, Power Apps portals, Power Automate, Power Virtual Agents, AI Builder, governance and administration, ISV experiences, and data integration.
Key dates for the 2021 release wave 1
Release plans available
January 27, 2021
Learn about the new capabilities coming in the 2021 release wave 1 (April 2021 – September 2021) across Dynamics 365 and Microsoft Power Platform.
Early access available
February 1, 2021
Test and validate new features and capabilities that will be a part of the 2021 release wave 1, coming in April, before they get enabled automatically for your users. You can view the Microsoft Power Platform 2021 release wave 1 early access features now.
Release plans available in 11 additional languages
February 23, 2021
The Dynamics 365 and Power Platform release plans published in Danish, Dutch, Finnish, French, German, Italian, Japanese, Norwegian, Portuguese (Brazilian), Spanish, and Swedish.
01. Search records in Microsoft Dataverse using relevance search
This feature allows to perform the Relevance Search from Power Automate cloud flows. The results returned in this search will be similar to what you will get when you search using the global search box in the navigation bar on Dataverse.
Public Preview – Not Announced | Early Access – March 2021 | General Availability – June 2021
“With this feature, you can create cloud flows that include a Microsoft Dataverse action to search records using relevance search, which is an AI-based fuzzy search that’s built on Azure Cognitive Search. Apart from basic cross-entity search, this action provides support for matches based on Lucene query syntax. This gives you capabilities like Boolean operators, wildcards, fuzzy search, proximity search, term boosting and regex matching.”
02. Trigger flows when a Microsoft Dataverse action is called
Traditionally, we write plugins to execute custom logics on Action events but cannot trigger a classic workflow when an action is performed. With this new feature addition to Cloud flows, we will be able to create flow that trigger when an action is executed. This will be a very handy feature especially when we are adopting to more and more low-code or no code development.
Public Preview – Not Announced | Early Access – March 2021 | General Availability – June 2021
With this feature, you will be able to create flows that trigger when an action is performed in Microsoft Dataverse. This feature improves working with the common events model and even provides better integration with Dynamics 365 Finance and Operations.
When we go to My Flows area on maker portal, it lists only the flows that are not part of any solution. Normally we will have our cloud flows spread in multiple solutions depending on what solution strategy we follow. In these scenarios, we will have to find the right solution and open the flow from there or we have to check in default solution if our flows are scattered in too many different solutions and if we do not remember which one is in which. Well, with the 2021 Wave 1, we no longer have to navigate to too many different places to find our cloud flows, all of them are going to be listed under My Flows.
Public Preview – April 2021 | Early Access – Not Announced | General Availability – Not Announced
“Makers can create and manage solution-based flows in the My flows experience, along with flows that are not in solutions. Here, makers can quickly add any flow into a solution.“
You must be logged in to post a comment.