Tag: Dynamics 365
Disable Security Defaults while login into Power Platform / Dynamics 365
Security Defaults provides preconfigured security settings such as MFA – Multi-factor authentication for all users, blocking legacy authentication protocols, etc.
Any tenant created on or after 22nd October 2019, will have this setting enabled for default.
An organization with complex security requirements could disable the security defaults and consider using Conditional Access instead.
Use Azure AD Conditional Access to block user access by device platform (Dynamics 365)
Use Azure AD Conditional Access to block access by country (Dynamics 365)
To disable Security default, login to Azure Portal
Navigate to Azure Active Directory > Properties
https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Properties
Toggle it to No and Save.
Hope it helps..
Advertisements
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..
Open forms, views, and dashboards through URL in Dynamics 365 Mobile / Tablet App
Recently we had a requirement to open an existing lead record within the Dynamics 365 Mobile App from another app.
Using the application handler for mobile clients this can be achieved.
Custom browser protocol – https://nishantrana.me/2020/09/22/use-custom-browser-protocol-to-launch-desktop-applications-from-dynamics-365/
We can either open an empty create entity form or an existing record by passing the GUID of the record.
Similarly, we can open a view and dashboard.
Below is the URL format
ms-dynamicsxrm://?pagetype=[entity/view/dashboard/create] &etn=[EntitySchemaName]&id=[GUID]
ms-dynamicsxrm://?pagetype=[entity/view/dashboard/create] &etn=[EntitySchemaName]&id=[GUID]
To open an existing lead record we would use the below URL
ms-dynamicsxrm://?pagetype=entity&etn=lead&id= e5975ea3-531c-e511-80d8-3863bb3ce2c8
Say for e.g. below is the lead record we want to open in the Dynamics 365 Tablet app from a desktop application.
The Windows Form Application –
On the click of the Open Lead button, the lead record is opened in the tablet app as shown below
In case we are not logged in to the app, it would ask us to sign in first and after successful login, it will open the lead record.
The same from an HTML page
The same is the experience for the mobile app.
Clicking on the link in the browser opens the Dynamics 365 Mobile App with the lead record specified in the id.
Similarly we can open a View, Dashboard, or the Create form for an entity.
Get all the details here –
Also check out the custom workflow activity for it
Check other posts on Dynamics 365 Mobile App
https://nishantrana.me/2020/05/12/dynamics-365-for-phones-and-tablets-blog-posts/
Hope it helps..
Advertisements
Macros in Omnichannel and Customer Service Workspace – Dynamics 365
Macros enables users to perform the set of sequential actions – repetitive and monotonous – in a more process complaint manner, which can be reused across different sessions, making it faster, more efficient and less error prone.
To define a Macro, navigate to Omnichannel Administration app > Agent Experience > Macros
Check other posts on Omnichannel
The interface is similar to Power Automate with some predefined automation actions.
Session Connector has the following actions >
Omnichannel Connector has the following actions >
Flow Connector has the following actions >
Productivity Automation has the following actions >
Get all the details here –https://docs.microsoft.com/en-us/dynamics365/app-profile-manager/macros
Now back to our Macro, select Productivity Automation trigger.
Select the action Start macro execution.
Select Clone current record.
Specify the title of the cloned record.
Let us create a new Agent Script with Agent Script step having Action Type as Macro.
Agent Script – https://nishantrana.me/2021/03/02/agent-scripts-in-omnichannel-and-customer-service-workspace-dynamics-365/
Navigate to Omnichannel Administration > Agent Experience > Agent Script and create a new Agent Script.
Follow it by adding a new Agent script step.
Below is our Agent script step record
which is associated with the Agent Script record
Now to test it let us open an existing record within a new session (Shift + record click) within Customer Service Workspace.
More on Customer Service Workspace –https://nishantrana.me/2020/08/13/new-customer-service-workspace-app-preview-in-dynamics-365-2020-release-wave-2/
Select Clone Record for the record to be opened in the new session.
As expected selecting on Clone Record – opens the clone of the record in a new Tab as shown below
We can also check the run history of the Macro using View run history option
That was a very basic example we saw, now with the option of running flow i.e. Run Flow as Macro using the Flow Connector, the possibility is limitless.
Hope it helps..
Advertisements
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..
