Viewing entries tagged
Dynamics 365

Treat PowerApp On Phone Like Apple Test Flight

Treat PowerApp On Phone Like Apple Test Flight

Most of us get frustrated that the PowerApps we build do not show up as individual apps on someone’s phone.

Well, here’s an idea: Go in to PowerApps on your phone. Find the app you built. Create a shortcut for it right on your phone’s main screen. Done. And, it has a custom icon because you add that directly when building the PowerApp.

Ron De Giusti
Purely CRM Consulting Inc.

Dynamics 365 Teams Linked to Azure AD

Dynamics 365 Teams Linked to Azure AD

Teams CAN BE added to Azure AD?

Recently one of our clients had an interesting question that regarded the use of their Active Directory. Our client hoped to have their Active Directory manage security within Dynamics 365 via Teams.

From the collection of research that we conducted, it seemed obvious to look at any recent functionality that may have been available. This sent out research towards Teams in Dynamics 365 online. Fortunately I was able to find Debajit’s blog who’s information on this subject was excellent .

Let’s start with a revelation – Now Azure AD groups can own records in Dynamics 365. All this time there used to be owner teams. Now both Azure AD office and security group can own your business records.
— Debajit Dutta
Through our research, we are able to say that the Teams entity in Dynamics 365 online, there is indeed a new Teams functionality!

Through our research, we are able to say that the Teams entity in Dynamics 365 online, there is indeed a new Teams functionality!

The Azure AD Object Id for a Group field on the team record sounded exactly what we were looking for but then how does this work?

It seems that you can now link Teams in Dynamics 365 to Azure Active Directory Groups.

This is a really exciting development for Dynamics 365 and this means of course that if you add security roles to the linked AD Team that you create then you could have a security setup managed by Office 365 Exchange.

Azure Setup

After coming across Debajit’s Dynamics 365 Blog, he explained the setup process in a seamless fashion that is very easy to follow. With his step-by-step guidance, and further research our client was able to enjoy their new solution. Take a look of our screenshots alongside with Debajit’s blog to further assist you in creating this solution.

Essentially the setup for this could not be simpler and it seems to work very well. Note the original blog article for the curve ball though. Your members (of the Team) seem not to show up in Dynamics until they login, which is fine as everything still works just fine.

2.jpg

Have a great day,

Alan Ashton

Purely CRM

Breathing New Air Into Dynamics CRM

Breathing New Air Into Dynamics CRM

I could not agree more with Juuka Niiranen’s latest blog post regarding Power Apps breathing new life into Dynamics CRM.

Lately I’ve been having this feeling of premonition combined with dejavu. Like being special agent Dale Cooper, investigating the events that are taking place in a strange town in Pacific Northwest, far away from your normal surroundings, encountering The Giant in a dream sequence and being told that “it is happening again”. Only this time the Giant is Power Platform and the place isn’t Twin Peaks but rather Redmond.
— https://survivingcrm.com/2019/06/why-you-should-become-a-poweraddict/

Create An App Instead Of Using Business Unit Security

Create An App Instead Of Using Business Unit Security

I heard great commentary on a podcast suggesting the use of an App instead of implementing business unit security. I can definitely see this as an option in some cases. The App could limit the views that someone has and in essence the records they have access to via those views. Sure is simpler than adding the overhead of business units if it is not truly required.

Was thinking about this after listening to The CRM MVP Podcast, episode 53: Top 10 FUNCTIONAL TRICKS in Dynamics 365.

Ron De Giusti
Purely CRM Consulting Inc.

Our Annual Trip to Whistler BC!

Our Annual Trip to Whistler BC!

Our Trip

This past Thursday I had the chance to travel to Whistler with the entire Purely CRM team. Although the weather forecast was not on our side, fortunately it was a very sunny day in the village. Our trip to the mountainside was supposed to include a short trail walk, however, the mountain had other plans! Hail had started en route to the peak, but once we were at the peak flurries were flying in!

As we were doing our Peak 2 Peak to the drier side, we were fortunate enough to see a couple of bears and the beautiful scenic views of our beautiful province.

The entire trip was very fun, and on a personal note, I had the privilege to meet the entire team, and create new relationships. With our dynamic and broad team coming together from all distances, it helped us reflect on our accomplishments, and future goals.

Have a great rest of your day,

Gurkirat

White & Black Modern Coffee Quote Photo Collage.png

PowerApps Component Framework

PowerApps Component Framework

Microsoft seems quite excited about the new PowerApps Component Framework (PCF).

“(PCF) is a significant step towards empowering [third]-party developers to build compelling visual components using the same framework which Microsoft team uses,” stated Microsoft’s Hemant Gaur, product owner for the PowerApps component framework, in a blog post. “The framework enables developers to create fully custom components for use across the full breadth of PowerApps capabilities.”
— https://msdynamicsworld.com/story/beyond-citizen-developer-why-pros-see-promise-microsofts-powerapps-component-framework

Easily see the implementation order of solutions

Easily see the implementation order of solutions

You can now easily see the order in which you implemented solutions in Dynamics 365 CRM.

Solution layers allow you to view all component changes that occur due to solution changes over time. Within a solution layer, you can drill down to view specific changed and unchanged property details for a component.
— https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solution-layers

Here is an image of solution layers in the toolbar:

solution-layers-toolbar.png

How to Hide/Display a Delete Button on the Command Bar Based on a Field Value on a Related Entity

How to Hide/Display a Delete Button on the Command Bar Based on a Field Value on a Related Entity

I want to show you how to hide/display a button on the command bar based on a field value on a related entity.

Here's how you do it!

As an example we have a custom entity called “Contact Role” and we want to hide the delete button on the command bar based on a field value on another entity called “Role”. Contact Role has a 1-to-many relationship with “Role”. On “Role” entity, there is a field called “Professional Only”. If this field’s value is equal to Yes, then we want to hide the delete button on Contact Role record, otherwise we display it:

1) First we need to use the REST service to get the value of the "Professional Only" field:

2) The next step is to use Ribbon Workbench. On Ribbon Workbench we need to add a display rule that can detect the current user’s permissions for a specific entity. Choose Contact Role entity on the Entities Navigation panel. Right click on Display Rules and add a “EntityPrivilegeRule” with “AppliesTo” set to PrimaryEntity, “PrivilegeDepth” set to Basic and “PrivilegeType” set to Delete

3) We also need to add several 'Enable Rules':

a) First we need to attach the REST service to an Enable Rule. Right click on Enable Rules and Add New rule. Right click on the act.act_contactrole.DeleteButton.EnableRule and Add Rule. Select Custom Javascript Rule.

Image6.png

On the right pane set “Default” to False, “FunctionName” to your Javascript function, “InvertResult” to False, and Library to your Javascript library.

b) Add another Enable Rule and call it Mscrm.CanDeletePrimary. Right click on this rule and add the rule with the type “RecordPrivilegeRule”.  On the right pane, set the “AppliesTo” to PrimaryEntity and “PrivilegeType” to Delete

c) Add the last Enable Rule and call it Mscrm.FormStateRule. Right click on this rule and add the type “FormStateRule”. On the right pane, set “InvertResult” to True and “State” to Create as we want to hide the delete button before we’re saving a record.

Now when you go back to the contact role entity if the "Professional Only" field is equal to Yes the delete button is hidden.