Manonmani V S
XRMToolBox – Bulk Security Patcher to assign users to Teams or Business Units in bulk
Category: #D365,Bulk Security Patcher,Dynamic Mano,Dynamics 365,XrmToolBox Author: Manonmani V S Date: 4 months ago Comments: 0

XRMToolBox plugins are a great way to make your admin work easier and it saves a lot of time and effort – Thanks to our MVP Tanguy Touzard for XRMToolBox framework(http://mscrmtools.blogspot.com/). Bulk Security Patcher is an XRMToolBox Plugin – a tool developed by the Dynamisity team(www.dynamisity.com) to bulk assign D365 Users to a Team or […]
Source: Mano


AI Builder – Form Processing
Category: AI Builder,Power Platform Author: Manonmani V S Date: 5 months ago Comments: 0

 

AI Builder brings in the below capabilities which would have taken more time and effort without the good news that the AI Modeling is now available in a no-code/low-code PowerPlatform that is gaining more traction:

  1. Binary Classification
  2. Form Processing
  3. Object Detection
  4. Text Classification

Want to know more about AI Builder? You may read here…

In this blog, I will show you the Form Processing feature. Let me explain quickly on how to read invoice data on a Canvas App using trained models in AI Builder.

First, let us create a model using AI builder and train it with sample invoices. Next, we will be using this model in a Canvas App to process the images.

Create a Model in AI Builder

  1. Select Form Processing – Log-in at https://make.powerapps.com and navigate to AI Builder > Build and select “Form Processing”. In the next screen, name your model and click “Create”.

2. Add documents – you will be given an option to upload documents. Select min 5 invoice images to train the model. The more images the better the results.

3. Analyse documents – Below screen shows the list of document for the model to Analyse. In this step the model will identify the data fields available on the document.

4. Select form fields – This step allows you to make a decision on what fields will be captured from the invoice to be processed in your system later. Click on the Image to select the fields.

On the right hand side, you will be able to see “All fields” as analysed by the model in the previous step. You may wish to select the fields that is required for your App and click “Next”.

5. Train your model

6. Quick Test your model – Navigate to Models>select your model and do a “Quick Test” by selecting a new invoice.

Yay! the model is trained to read the key-value pairs. The model has identified the below fields as highlighted in green. Mouse over to see the attribute key and value.

7. Publish – Now Publish it to make it available for Canvas App.

Create a Canvas App for Form Processing

  1. Create App – click on “Create app” and choose “Canvas App”. Give your App a name and save it.

2. Navigate to Insert>AI Builder>FormProcessor

3. Select the model that you have trained earlier.

4. You will see the Form Processor AI Component. Run the preview F5

5. Click “Analyse” to add a new invoice that you wish to process. The app will identify the fields that we have trained the model for.

6. How to Extract invoice data to the Canvas App form? It is pretty simple as using the below formula.

FormProcessor.FormContent.Fields.<Yourfieldname>

You may now save this data to trigger flows.

Further reading…†

https://docs.microsoft.com/en-us/ai-builder/form-processor-component-in-powerapps

 

 

Source: Mano


Dynamics 365 view – Edit Filter Criteria: “There was an error in showing this condition”
Category: Dynamics 365 CE Author: Manonmani V S Date: 5 months ago Comments: 0
“There was an error in showing this condition”

When you see the above error on a view criteria, you might be puzzled what went wrong with the condition. It is because, the searchable property of an attribute used on the filter condition is set is “no” which was earlier set to “yes”.

If you want to know what the filter condition is, just hover on the information icon to find the attribute name.

Revert the searchable property of the attribute to “yes” and publish your customization. Once done, open the “Edit Filter Criteria” on your view to see the filter condition appear now 🙂

Tip: If you have a requirement to make an attribute non-searchable, then find the dependencies especially those on view’s filter criteria and resolve it before you make them non-searchable.

Source: Mano


Power Platform: Secure your organization’s data with “Data loss prevention (DLP)” policy
Category: Data Loss Prevention,Data Loss Prevention Policy,DLP,Power Platform,PowerApps Author: Manonmani V S Date: 7 months ago Comments: 0

Is your data secured?

Power Platform comes with the capability to build Applications that connect across multiple data sources and services which include external third party services and even social networks. Is your data secured? Well, I think it is, and I think I am doing what I am allowed to do with my organization’s data.

With the increase in number of connectors, there comes the risk in data leakage.

Currently, with over 230 connectors in PowerApps, there are chances that users might unintentionally expose your organization’s data while connecting to social media connectors or any external 3rd party services that might be a security concern. Is your data secured? Well, I think it is, and I think I am doing what I am allowed to do with my organization’s data. It’s time to secure your organization’s data.

How to prevent this unintentional data leakage?

Secure your organization's data with Data loss prevention policy

PowerApps Administrators can set up and enforce Data loss prevention (DLP) policies in the PowerApps environment to safeguard the data from being exposed to unintended audience. DLP is a rule that while setting up, classifies your data sources(technically the connectors in PowerApps) into two repelling groups as below. Yes! these groups doesn’t talk to each other.

  1. Business data only group
  2. No business data allowed group

By default, all connectors are in No business data allowed group and none are added to the Business data only group. Environment admins or Tenant admins can add connectors to the Business data only group while setting up DLP policy which will isolate the critical business data from non business data connectors.

How does this classification help?

Let’s consider that Dynamics 365 connector is added to the Business data only group and Bing Maps connector is by default in the No business data allowed group. A user have created an App in the environment where the DLP policy is enforced by the administrator and successfully connected to the Dynamics 365 data source which is part of Business data only group. The user now tries to connect to the Bing maps data source, which according to the environment’s DLP policy is not allowed as it is part of No business data allowed group, hence, the user will encounter an error that says, “Using these connections together conflicts with the company data loss prevention policies”.

Error while connecting to a data source

As I mentioned earlier, they are in repelling groups that doesn’t talk to each other to share data which is what you need to secure your data. Let’s see how to set up DLP policies in an environment.

Creating a DLP policy:

To create a DLP Policy, you must be an Environment Admin or a Tenant Admin or an Office 365 Global Admin.

Sign in to the Admin center at https://admin.powerapps.com and you will see Data policies on the left navigation pane.

Click “New policy” on the top right corner.

Create New Policy

 You will see the new Data Policy name auto-populated. I am renaming it to “Safeguard D365 Data”. Choose an environment from the drop-down.

Environment selection

Note: If you are an Environment Admin, you will choose your environment as shown in the above screen. If you are a Tenant Admin, you will be able to

  • Apply to ALL environments
  • Apply to ONLY selected environments
  • Apply to ALL environments EXCEPT

Click “Continue” to proceed with Data groups set up. You will see the empty Business data group and the default No business data allowed group with all available connectors in it.

Data can be shared among data sources within the group itself but not between two groups.

Click “Add” to add connectors to the Business data only group.

“Business data only” and “No business data allowed” – Data Groups

Select the connectors and click “Add connectors”.

Select connectors for Business Data only group

You will see that the selected connectors are added to the Business data only group. At any point in time, a connector can reside in either of the groups and NOT in both groups.

Click “Save Policy”.

You may manage your DLP policy by clicking the “Edit” or “Delete” icon on the right side.

Now that the DLP policy is set up, as a best practice, Administrators may share the policy details with the organization so that users can make decision prior to designing the Apps.

Further reading…

https://docs.microsoft.com/en-us/power-platform/admin/create-dlp-policy

https://docs.microsoft.com/en-us/power-platform/admin/prevent-data-loss

https://docs.microsoft.com/en-us/power-platform/admin/introduction-to-data-groups

Source: Mano