Advertisements
Category: Dataverse
Search this view capability on Grid in Dynamics 365
Search this view capability which was added in the product with 2020 Release Wave 1, searches on the fields specified in quick find view, but takes into consideration the selected view definition, when performing the search.
This is enabled by default.
Here Search this view will perform the search within the selected view i.e. All Contacts in this case.
The results show 3 records found within the All Contacts view, for the search term “alex”
The same search term returns blank in the case of Inactive contacts is selected.
The same applies to the sub-grids
To turn off this, select Yes for Use quick find view of an entity for searching on grid and sub-grids from General tab of System Settings
After applying the above change, we can see the text renamed to Quick Find within the Search Box.
Searching now, irrespective of the view selected, will perform the search across the records as per the definition of Quick Find view.
More on it
https://docs.microsoft.com/en-us/powerapps/user/grid-filters#use-search-on-a-grid
Also read – Search limit on Quick Find
https://docs.microsoft.com/en-us/powerapps/user/grid-filters#use-search-on-a-grid
Hope it helps..
Advertisements
Share It -
Fixed – Error – “Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server” – while trying to use Dataverse connector in Power BI
While trying to use Dataverse connector inside Power BI Desktop
we got the below error
Details: “Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)”
Later we realized we were not entering the environment details in the correct format as expected
i.e.
[orgname].[crm].dynamics.com
We were entering it incorrectly below with the https
Entering URL in correct format fixed the issue for us.
In case if TDS endpoint it not enabled –
we will get the below error
i.e. Microsoft SQL: TDS Protocol endpoint is disabled for this organization.
Check more posts on Power BI
Hope it helps..
Advertisements
Share It -
Agent scripts in Omnichannel and Customer Service Workspace – Dynamics 365
Agent scripts are available within the Productivity pane in the Customer Service workspace and Omnichannel for the Customer Service app.
Agent scripts contains series of steps that will guide the agents while working, helping them to be more efficient.
More on Customer Service Workspace – https://nishantrana.me/2020/08/13/new-customer-service-workspace-app-preview-in-dynamics-365-2020-release-wave-2/
Omnichannel for Customer Service –https://nishantrana.me/category/omnichannel/
To define Agent Scripts – navigate to Customer Service Hub > Service Management > Agent Scripts or Omnichannel Administration > Agent Experience > Agent Scripts
Create a new Agent script record, and specify steps for the same by creating new agent script step record.
We can define 3 different types of Action – Text, Macro, and Script.
For simplicity, we have selected Text here.
We have defined 2 script steps for the agent script as shown below.
Next, we need to associate the Agent Script with the Session template.
Inside the Omnichannel Administration > Agent Experience > Sessions, select the template we want the script to be associated.
Here let us select the Case entity session – default template
We can also define the conditions for the default agent script to be applied using the Enable Build expression option.
For now to make the example simple, we leave it as No (default).
Back in Customer Service Workspace or Omnichannel for Customer Service App– Shift + click the case record to open the new session in the Active Cases grid.
We can see the script populated there for the agent on the case record opened.
If we have multiple scripts associated with the Session template – the agent has the option to select the appropriate script.
Hope it helps..
Advertisements
Share It -
Check access to a record in Dynamics 365
Using the Check Box button in the command bar, the user can now check the privileges he has on the record.
It also provides the details on how he has that particular privileges on the record, either through Security Roles assigned directly or through the team user is part of or through the Hierarchy security.
To see it in action, open a record and select Check Access
E.g. the below user has Read, Write, Create, Delete, Append, Append To, Assign, Share rights on the contact record, assigned directly as he has the system administrator role.
The admin user can also use the User lookup to check the access of the other users.
Here the test user 1 has rights to the record through the security roles assigned to him directly and also through the team he is part of.
Get all the details here –
https://docs.microsoft.com/en-gb/powerapps/user/access-checker
Hope it helps..
Share It -
In-app or Push notification – Model-driven App – 2021 Release Wave 1 Power Apps / Dynamics 365
With 2021 Release Wave 1, the in-app notifications feature has been added to the Model-driven app, earlier it was only available for Canvas Apps.
To see it in action à
Login to Power Automate
https://us.flow.microsoft.com/en-us/
Create a new flow, select start from blank – Automated cloud flow, make sure the appropriate environment is selected.
Specify the flow name along with the trigger
Here for the trigger, we have specified the condition as contact creation.
For the action, select Send Push Notification V2 (preview)
For Mobile App, we can select either Power Apps or Field Service app to send the notifications to.
Here we have selected Power Apps mobile app.
Your app field will list down all the Model-driven apps available for the environment.
In recipients specify the email address and define the message.
In the Open App option, we can specify whether to open the app or not, on tap of the notification.
Finally, we can specify the entity, form for that entity (or view) to be opened.
We are setting the record id (of the contact record created) that should be opened in the form.
Save the flow.
Creating a contact record will trigger the flow and will send the notification to the mobile as shown below.
We can click on the notification, which takes us to the record as shown below.
Get all details here
https://powerapps.microsoft.com/es-es/blog/now-available-model-driven-app-push-notifications/
Blog posts on 2021 Release Wave 1 – Dynamics 365
Hope it helps..
Advertisements
Nishant Rana's Weblog 