So busy with year ending and 2020 plans. Since I said two months, I have to release the pro version. Really sorry for the Poor CSS am actually bad at styling stuff. But you can always improve the style and features in the Github, any updates are welcomed. Here is the github repo link.
Create a view with the required filters. If you do not require the control to consider certain activity types, you can exclude them in your view filter. The control will consider only the records returned by the view selected.
Add sub-grid to the form with the view we created.
Add Activity Summary control to the sub-grid.
Note: If you need to exclude certain activity types, apply the same logic in the view filter.
Today i am going to share quick tip of how to add an entity and filter views on Dynamics 365 App for Outlook.
You know what i am referring to, ok you got it ? if not see below screen shot..
So there might be requirement to only show certain entities and view and hide unnecessary entities to the Dynamics 365 App for Outlook users.
In that situation we can modify the site map of the “Dynamics 365 App for Outlook”.
Go to the Settings > Customizations > Customize the system > Model driven Apps > Double click on the Dynamics 365 App for Outlook..
Refer to the below screen shot.
Once you double click on the Dynamics 365 App for Outlook.. Sitemap will be opened and click add(+) then select the entity you want to add,
for instance i will add “Quote” and check box ” add all assets” and click on the Views you want to show on the Dynamics 365 App for Outlook..
Refer to the below screen shot..
Select the “Quote” entity and check the ” Add All Assets”.
Now you can change the views as well see below screen shot.
Registration of the #PowerPlatform application in #Azure is becoming inevitable in most projects. The most basic requirement is to expose the #PowerPlatform services to outside world. When you provision a #powerplatform subscription, Microsoft by default associates an #AzureAD to your subscription. This #AzureAD is only a directory without #Azure subscription linked with it. For using #Azure services, you will need to have #Azure subscription. You may have an existing #Azure subscription with lots of services in it and most often you wish to link the existing #Azure subscription with the new #AzureAD provisioned for the #PowerPlatform subscription. In this post, I list down the steps you will need to associate your existing #Azure subscription with newly provisioned #AzureAD linked with your #PowerPlatform.
Go to your newly created #AzureAD by browsing: https://portal.azure.com.
Sign in with your #PowerPlatform Credentials.
You will have no subscriptions as per the below picture (You can see your subscriptions by searching Subscription in the search textbox).Go to Azure Active Directory. You will find the Azure Active Directory link on the left panel.
Go to Azure Active Directory. You will find the Azure Active Directory link on the left panel.
Go to Users and Click on the New User.
Click on the INVITE User. Fill the form and invite the user associated with the #Azure subscription.
Give the Administrator access to the invited user so the user can create applications and register endpoints.
The contact associated with the #Azure subscription will receive an email to access accept the invitation.
The next step is to login to the #Azure account with the subscription and access the subscription (by searching the word subscription on the search box).
Click on the subscription to see the subscription details.
From the command bar click on the “Change Directory”. You will see the #AzureAD which invited you to be move your subscription to it.
For all of those aspiring MVP’s out there, now available in the Power Platform Bank a set of files including a solution for the entities required in CDS, an excel spreadsheet for the contribution type data and a Canvas App to manage your contributions.
Problem : within Embedded Canvas app we know how to get text field values but how to retrieve the (polymorphic) Lookup values.
Before me jotting down the solution, I would like to elaborate what is Polymorphic lookup?
Polymorphic Lookups are the lookups which can refer to a record from any entity in a set. Owner field in any entity is a classic example which refers to both User and Teams entities.
Why is it important to know if it is polymorphic lookup or not to retrieve the lookup value in embedded canvas app?
Well, because if the lookup refers to more than one entity then the name (schema) of the fields which we want to retrieve varies by entity. In above mentioned Owner example, if we want to retrieve name value from the Owner field. In Teams entity Name field is called as Team Name, whereas in User entity Name field is called as Full Name.
Powerapp doesn’t know which entity Name value we want to retrieve, so we have to be specific in this case.
In Contact entity if we want to retrieve Company Name field value and display in a canvas app. Company name refers to both Contacts and Accounts entity. So in our formulae we have to be specific about which entity values are we interested in.
Following formulae retrieves Name field from Company Name Lookup by checking the condition.
If Entity type is Accounts then it retrieves Account Name, if Entity type is Contacts then it retrieves Full Name field.
Reflowing to either card or list form is another way to control how we want to present information in Unified Interface. To read more about reflowing, please click this link.
This property applies to read-only list views and sub-grids.
So, a list form in Unified Interface looks like this:
And a grid looks like this:
In Unified Interface, a reflow concept was introduced. It is where the information will be displayed as a “card form” when the space available is not enough to display the columns of the sub-grid. For example:
Below on my Account Form, you can see that my related contacts sub-grid is displayed in the card form.
Now if I go to see the settings in my form designer, you can see that the width of the third column where the contact sub-grid is displayed is set to occupy 25% of the whole space.
If I increase the space occupied by the 33% or 1/3 of the whole space, let’s see what happens:
When I hit publish and refresh my UCI form, the sub-grid automatically “reflows” to the grid form.
So it seems like it the grid would reflow to card form once space occupied is not enough for the whole information on the grid to be displayed.
But if you wish to have more control in the reflow behaviour of your app, you can go to the controls settings and specify how you want the information to be displayed.
In your grid editor, select the Controls tab and then select Add Control
Select Read Only Grid
Select which client you’d want this control to be applied to, then select the pencil icon to control the behaviour.
You can define how you want your data to be displayed, you can choose from 3 choices
Reflow – the grid will “reflow” to card form once there is not enough space
Grid only – data will be displayed in grid form only.
List only – data will be displayed in card form only.
If you’re selecting reflow or list only, you can define which card form you’d like to use.
You can customize how you want the information to be displayed in your card form by creating a form with type “card”.
The data will be displayed like this:
Once it is published, you can now control how you want your lists to be displayed in Dynamics 365. I use it often on Classic Dashboards and sub-grids within forms. Here are some examples 🙂
If you are using an iPad and Safari to open Microsoft Dynamics 365 CE environments you may know, that in classic web UI, the settings tab has not been shown and also in the new UI the option to open the advanced settings window is not shown. Trying to open a copied link to the advanced settings is showing an error.
But – if you are browsing to make.powerapps.com on your iPad, you can select your Dynamics 365 CE environment and all supported customization options of the PowerPlatform are available.
Editing views, forms and dashboards in CE and model-driven apps and also building canvas apps and flows is working.
you are already working with several O365 / D365 tenants or,
you need to log-in with different user profiles simultaneously in MSDyn365CE or PowerPlatform to customize and test.
In many cases the private browser / guest user is used or the current user will be logged out, the browser will be closed or the cache will be cleared. But there is an easy way to use several logins, when you can use Google Chrome. In this case you can use different chrome persons (profiles).
To create a new person, click on the person icon in the top right corner and then select “Manage people” and then “Add person”. In the following step you can select an avatar and give the chrome person a specific name e.g. the name of the tenant or the username /role you want to use in this chrome browser.
To switch between the chrome browser instances, you need to click on the person icon in the top right corner and then select the one you want to use. The new person will start in a separate window.
Each chrome person starts a separate browser instance with its own cache, bookmarks, history and extensions.
Some time ago, I thought about creating a Canvas app with the Microsoft Power Apps platform, something which can be useful in the company and also use Microsoft Azure cognitive services.
Finally, I decided to use Face API of cognitive services to make some fun with face recognition to detect my colleague’s faces and information from the photos. most of the companies have yearly events and lots of photos from employees. search within thousands of photos to find only a specific person wouldn’t be easy. with the use of Microsoft cognitive services together with the help of Office 365 API it would be easy.
First of all, we need to have at least one photo of each colleague and it’s available already in the Office 365 profile picture. So we can use Office 365 API user search to find all the employee list from active directory and recognize the face from the profile picture and register the user as a person in cognitive service. also, each office 365 user profile information can be stored as a person meta data in cognitive service and detected face from the profile photo with a unique face Id will be assigned to that person object.
from now on we can just take a photo of a colleague using a smartphone camera or just an existing image to recognize the persons in the photo.
I dig a little bit deeper into the implementation of the solution. To simplify the maintenance of the entire workflow and process, I’ve created most of the business logic and services in a REST API using Function Apps, and then made a Custom connector from it in Power App in order to call these endpoints directly from my canvas app or also from a custom Flow. Therefore, I should not update the Canvas app at all after a few minor changes in API.
by capturing photo with camera, the photo will be send to the API in order to be analysed and find the person face. it detect also all the faces in a photo and find the persons base on the faces.
Integration with SharePoint
It is also possible to find similar faces in a bunch of event’s photos. the only thing that should be done is analyzing each photo content during storing the photo and identifying all faces. If the photo gallery already exists, then we need to execute the process one time for all pictures.
imagine that there is a photo gallery in SharePoint and we want to find all photos of person A. after identifying the faces in the photo, we need to store all the face Ids in a Large list of all faces in the cognitive resource database. Also, we can store the photo metadata, like SharePoint Item Id or Picture URL, as user data per each face. for instance the location of the face in the photo, so if there is more than one face in a photo we can find the location of the person later on. This process can be done also by using Microsoft flow.
After we identified and stored all the faces from Photo Gallery into a Large Face List, we can start taking a photo or just using the person office 365 profile picture to find all other similar faces in the face list. The result of the process can be a list of face Ids with user metadata (the picture URLs). so we can show all the photos using the URLs.
of course, it makes sense to integrate this feature as a plugin or a work flow in SharePoint. Imagine that during uploading photos to the SharePoint, this service can find and recognize the faces in the picture and add some tags (person’s name) to the item.