Even if it appears to upload correctly, it may not open properly and display something like this:

Consider the following scenario. Suppose you have attached a document in SharePoint and want to save it in Notes.

1. Let’s say you have uploaded this PDF document to Notes and now you want to upload it to SharePoint.
2. I have a flow that sends this document to SharePoint that runs when I create a note in the Dataverse (Dynamics 365 CRM).”
3. Now the “Create File” action in SharePoint looks like this:
   This allows the SharePoint file creation action to add the document to the file context. Hovering the mouse over this will result in triggerOutputs()?[`body/documentbody`].
4. Running this flow creates a document in SharePoint. However, when I open the file, I get an error message that the file cannot be read, even though the file appears to upload correctly.Please click on the link to find correct way to
   

   Create a file from a Dynamics365 CRM record attachment notes and move to SharePoint documents. without corrupted file.
   

Use base64ToBinary conversion

Here’s a step to create a File in SharePoint in your mentioned SharePoint library –

1. In order to correctly pass this through, use the base64ToBinary expression in the Create file’s File Content field.
   
2. And in base64ToBinary, put the Document so that it looks like this – “base64ToBinary(triggerOutputs()?[‘body/documentbody’])“
   
3. And when you re-run the test, the document will be created in the same way.
   And now when you open it, it’ll open properly.
   

The post SharePoint file created from power automate flow doesn’t show open correctly or corrupted. appeared first on Microsoft Dynamics 365 Blog.

In this blog, we have explained how to send these cards to the Microsoft Teams channel using Power Automate Flow. We have taken an example where we automate the process of sending an employee information Card when a custom entity employee record gets created.

Microsoft introduced new connector in the power automate flow named as Cards for Power Apps.

This connector is used to create or get card instances with the input variables, and it will return the dynamic content of the card instance.

• Create card instance (preview): This will help us to create a card instance of a specific card that we have created in our solution. We can also send input parameter values through this card instance. This card instance will return the dynamic content of the card.
• Get the card description (preview): This will help us get information about the card like ID, name, description, author, etc.

You can follow the below steps to create Power Automate Flow to send cards to the Microsoft Teams channel.

Step 1: Sign in to PowerAutomate using your credentials and select your environment.

Step 2: Click on My Flows >> New Flow >> Automated Cloud Flow.

Step 3: Give the name and choose the flow’s trigger.

Step 4: Set the trigger. In the example screenshot below, the trigger is when a new custom employee record is created.

Step 5: In new step, search for Cards for Power Apps, then click on Expand button.

Step 6: Select Cards for Power Apps.

Step 7:  Select Create Card Instance (preview).

Step 8: Select the card that you want to send. Set the body input variable. In this example, we set the Account Name value of the newly created account record.

Step 9: In the next step, search for Microsoft Teams connector and select the action as Post Card as a chat or channel.

Step 10: Set the Power Apps (Preview) in Post as field, and set Channel in Post in field. You can select your team and channel from the dropdown. After that, set the card instance that we created in the earlier step.

After this power automation flow gets created, it will be triggered when the new employee record gets created, and the card will be sent to the Microsoft Teams channel as shown in the below screenshot.

Conclusion

Thus, in the above blog, we learned how to send Cards to Microsoft Teams channel by using Power Automate Flow.

The post Automatically sending Power Apps cards to Microsoft Teams channels using Power Automate Flow first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Go to Source and hit them a thumps up

The post Automatically sending Power Apps cards to Microsoft Teams channels using Power Automate Flow appeared first on Microsoft Dynamics 365 Blog.

The main purpose of this feature is as follows-

Whenever we delete any user it remains in the environment as a disabled user which may take some space. After deleting the unwanted (disabled) user some storage will free up and you will be able to use the license for other users within the environment.

Let’s see how it works, first, we see how to create new users from Microsoft 365 admin center and add them to the power platform environment.

Login into Microsoft 365 admin center -> Users -> Add a User -> Create a User

Now Login into https://admin.powerplatform.microsoft.com/  -> Select the Environment -> Settings -> Users + Permissions -> Users -> Add User

Once a user is added to the power platform then the same will get added to Azure Portal

Now we will see how to delete the user from Microsoft 365 admin center and see the status in the power platform and Azure Portal.

Login into Microsoft 365 admin center -> Users -> Active Users -> Select User -> Click on Delete User

When you delete the user from the admin center it will be soft-deleted and you can restore the user within 30 days after the deletion. Once you click on Delete User you will get confirmation as shown below.

Once a user is deleted from the admin center check the status in the power platform

Select deleted user -> Run Diagnostics

Here, you can see the status of the user shown as Disabled, which means the user is still in the power platform and not deleted yet, and also the user will get deleted from Azure Active Directory.

When the user is deleted from the admin center then the user remains active and shown in the power platform i.e. environment only the status is shown as disabled.

Now we will see how to delete users from the power platform by using the “Disable Deleted User” preview feature.

Before enabling the “Disable Deleted User” preview feature, you can see the following filters under users.

Select the Environment -> Settings -> Product -> Features -> Enable Delete disabled users (preview) -> Save

Now we need to delete the user permanently which is created in the admin center by connection to the Azure Active Directory admin center. Login into Azure Active Directory admin center

Users -> Deleted Users -> Select user -> Delete Permanently

Now user gets deleted permanently from Azure Active Directory but it will be still present in the power platform but in a disabled state.

Once the user enabled the feature, you will be able to see more filters as shown. Click on “Users, not in AAD but exist in the environment” here you will be able to see the user which is deleted from AAD select the same user, and click on Delete User.

Conclusion

This feature allows us to delete the user with a disabled status in the environment thus freeing-up storage from the environment.

The post How to permanently delete Disabled Users from the Power Platform first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please visit the Source and support them

The post How to permanently delete Disabled Users from the Power Platform appeared first on Microsoft Dynamics 365 Blog.

In this blog, we will see how to enable Administration Mode from Power Platform Admin Center. Enabling the Administration Mode comes in handy while performing operational changes to the environment like copying a sandbox instance to the production. Previously, this setting was available from the Office 365 portal for sandbox instances. For more details, you can refer to this blog.

Administration Mode can be enabled for Sandbox, Production, and Trial (Subscription-based) instances. So once enabled, only the users with the security role of System Administrator and System Customizer can access the environment. Enabling the Administration Mode ensures that neither non-administrators nor administrators affect each other’s work.

Let’s see how to configure ‘Administration Mode’:

1. Navigate to Power Platform Admin Center Login with Environment Admin or System Administrator -> Navigate to Environment from the left-side menu.

2. Select the Environment and Click on Open.

3. In Details, select Edit.

4. Enable the Administration Mode.

5. Post enabling the Administration mode, you will get the option to disable or enable the Background Operation. By default, this option is enabled.

If you disable the Background Operation, it will disable all asynchronous operations like workflow, and synchronization with Exchange.

6. Now the Custom Message field is no more editable as it is being removed -> Click on Save.
7. After saving, the environment gets updated.

Once it is completed, you can see a notification on the Environment page stating that ‘This environment is currently in administration mode, so only admins can sign in to it. You can turn off administration mode in settings’.

Now, only users with System Administrator or System Customizer security role can successfully access the environment.

Whereas, other end users i.e. non-admin users will not be able to access the environment.

Conclusion:

In this way, administrators can manage and maintain the environment by setting it in the ‘Administration Mode’ from Power Platform Admin Center.

Please visit the Source and support them

The post Enable Administration Mode from Power Platform Admin Center appeared first on Microsoft Dynamics 365 Blog.

Microsoft recently introduced Microsoft Power Platform Command Line Interface to perform various operations on Microsoft Dataverse environments, Power Apps Portal, PCF, Plugin, Solution, Admin, and Canvas by using Visual Studio Code.

In this blog, we will be focusing on Power Apps Portal and will see how we can connect Portal using Microsoft Power Platform CLI and perform various operation on the same.

To be precise, we will create a new web page using CLI and check it on the portal.

However, there are some prerequisites that we need to configure before start working on Power Apps Portal.

First, we need to configure the Power Apps Portal for our CRM.

Login to https://make.powerapps.com/ and click Portal from Blank.

After clicking the button, a popup will appear where we need to provide a suitable name for the portal and address.

Then click on the Create button and wait for the portal to become ready to use.

While the portal is being configured, we need to install the Power Platform VS Code Extension in our Visual Studio Code.

Open the Visual Studio, click the extension button and search for the Power Platform VS Code Extension. Once it is visible, click the install button.

Here we are done with prerequisites and ready to connect the Power Apps Portal.

Now create new folder and open that into Visual Studio Code. The Power Apps Portal data will be downloaded in this newly created folder.

Open the Terminal in VS Code.

Now we need to authenticate it in order to connect Power Apps Portal. To authenticate we will use below command:

Command: pac auth create –url <Dynamics CRM Url> –un <User ID> -p <Password>

For example: pac auth create –url https://orgname.crm.dynamics.com –un admin@orgname.onmicrosoft.com -p pass@123

You can check if you have successfully connected to your environment by running the command.

Command: pac org who

This will show you the organization details.

Once successfully authenticated now we need to download the portal data into our system so that we can work offline into our portal and then upload it back to cloud.

To download the Power Apps portal data we need to run the below commands.

Command: pac paportal list

This will show you the listing of portal websites and website ids into your connected environment. The WebsiteId will be used in the command to download the Portal data.

Command: pac paportal download –path “<Directory Path>” –webSiteId <Portal WebsiteId>

For Example:

pac paportal download –path “E:\Sam\PowerAppsCLI” –webSiteId d78574f9-20c3-4dcc-8d8d-85cf5b7ac141

Once it is downloaded, all portal data can be seen in the folder and since we have already opened the folder in our VS Code we just need to refresh it.

Now to create new custom webpage we need to know things we required to update.

• YML extension files: – yml is serialized human readable text document file, which is actually not a Markup Language. Using this we will be setting our web page properties.
  • How we can set property? It will be like key value pair and the key will be logical name of the property and the value for the key needs to specify after the colon (:).

Our custom page should be having the below properties and its values.

• Parent Page(adx_parentpageid) : Home Page
• Page Template(adx_pagetemplateid): Full Page without Child Links
• Publishing State(adx_publishingstateid) : Published

As can be seen above, we will be using the “Home Page” as the value of the adx_parentpageid, “Full Page without Child Links” as the adx_pagetemplateid and “Published” as the adx_publishingstateid.

Moreover, to set the above properties we first need to get unique ids for each of these properties. As each of them are attributes of type lookup in Dynamics 365 CRM and to map respective records in the lookup fields we require their respective Ids.

To get the unique id of the Home Page, expand the Web Pages folder and find home. Then expand it and open the Home.webpage.yml. After that copy the value of adx_webpageid. This is the value we shall use for the adx_parentpageid attribute of our custom page.

To get the unique id of Page Template, expand the page-templates folder from main folder, look for the Full-Page-without-Child-Links.pagetemplate.yml page template file and copy the value of adx_webtemplateid. This is the value we shall use for the adx_pagetemplateid attribute of our custom page.

Similarly, we need to find the id of Publishing State. In the main folder search publishingstate.yml file and copy the value of adx_publishingstateid. This is the value we shall use for the adx_publishingstateid attribute of our custom page.

Now we have all values for our required properties.

To create new custom web page, we will expand the Web Pages folder and within it copy & paste any Web Page. For instance, we copied category page as shown below:

After pasting all required things now we will update folder and files as per our requirement.

We changed the web page name to custom-page and also renamed all files inside the folder. After updating the name, we need to set/update the properties inside the “Custom-Page.webpage.yml” file.

You can check the changes we did in below screenshot:

Now in the “Custom-Page.en-US.webpage.yml” we will be adding the same values as we have set in the above step except for the adx_rootwebpageid. In the adx_rootwebpageid we will set the value of adx_webpageid from the “Custom-Page.webpage.yml” file.

After updating the yml files, we can now update the html files and that will be shown in our portal.

Once changes are done, save the changes. And now we are ready to upload our portal data into cloud.

For uploading the changes, we will use below command:

Command: pac paportal upload –path “<Directory Path>“

For Example: pac paportal upload –path “ E:\Sam\PowerAppsCLI“

Result:

We completed our changes and uploaded those changes on cloud. Now we will check if the changes are reflected in our Portal or not.

Open the portal home page and since parent page of our custom page is home then after the portal url we will add “/<partial name of the page>/” to access our page.

For example: <portal url>/custom-page/

Conclusion:

Using Microsoft Power Platform CLI, we are able to work on the portal in offline mode and after doing the changes, we are able to upload them in one go. In addition, it will help developers to migrate portal data from one environment to other environment with very less effort.

Please visit the Source and support them

The post Perform changes in Power Apps Portal with newly introduced Microsoft Power Platform CLI appeared first on Microsoft Dynamics 365 Blog.

In this AI Builder three-part blog series, first blog was about how to use AI Builder to extract Form document data and second blog highlighted the use of AI Builder Text classification model.

Now in the third and final blog we will see how to build an AI Object Detector using Power Platform.

Object detection refers to the capability of computer and software systems to detect images, locate objects in an image and identify each object. Object detection can be used to expedite or automate business processes in multiple industries.

AI Object detection is a new feature in Power Platform which can be accomplished using AI Builder. AI Builder allows you to add artificial intelligence to your apps even if you have no coding or data science skills.

Let’s see how an AI object detection model is built using AI builder. On the other hand, Object detection App is built using PowerApps and data is transferred from PowerApps to Dynamics 365 CRM using Microsoft Flow in Power Platform.

1. Build Object Detection Model using AI Builder

a. To build a model using AI Builder, sign in to PowerApps and, in the left navigation pane, select AI Builder > Build. Then select the Object Detection model type.

b. Name your model and Create

c. Select object names – Select the object names by selecting an entity from Common Data Service. Here, we have selected a custom entity with name ‘Electronic Item’ and Field ‘Name’. This entity has records with name of electronic items like Monitor, Keyboard, Mobile and Mouse.

d. Add images – Click on ‘+Add Images’ button to upload images of objects that you want to detect and identify. Upload 15+ images of each object.

e. Tag images– Teach the model to identify objects by tagging and labeling them. For each image, draw a rectangle around the object which you want to identify and tag it with correct name. Go through all the images to tag the objects. Once all the images have been tagged, click on Done tagging.

f. Train Model – Click on Next >Train. It will take several minutes to train the model. Use Quick Test to test the model’s accuracy and then Publish the model to consume it in the app.

Once the model is published its status changes to Live from Draft.

2. Build Object Detector App using PowerApps

a. Click on Create app button shown in previous step. You can create a Canvas App or Model-driven App or Portal from blank depending upon your choice. In our example, we are creating a Mobile Canvas App.

b. Insert Object Detector by navigating to Insert > AI Builder > Object detector. Drag the Object detector to your screen and select the existing object detector AI model.

The object detector control looks like below:

c. Insert a Gallery Control with Title and subtitle layout.

Set the properties of Gallery and its Title and SubTitle as follows:-

Gallery Items  = ObjectDetector1.VisionObjects

Title Text = ThisItem.displayName

Subtitle Text = ThisItem.count

d. Insert some label controls for storing the values of Count for each individual item i.e. Monitor, Keyboard, Mobile and Mouse Counts and set their text properties.

For Example: –

lblKeyboard.Text =First(ObjectDetector1.VisionObjects).count

lblMobile.Text= First(Filter(ObjectDetector1.VisionObjects,StartsWith(displayName,”Mobile”))).count

lblMonitor.Text= First(Filter(ObjectDetector1.VisionObjects,StartsWith(displayName,”Monitor”))).count

lblMouse.Text= Last(ObjectDetector1.VisionObjects).count

You can make your own formula by utilizing the Gallery or Object Detector controls

e. Insert a Create button. Click on Create button, navigate to Action > Flows > Select the existing flow or Create a new Flow as described in 3^rd point. It will start processing and add the selected flow to PowerApp.

Modify the function of Onselect as shown below by passing the parameters to the flow. Here, CreateElectronicEntry is the name of flow.

OnSelect =CreateElectronicEntry.Run(Concat(Gallery1.AllItems,displayName & “-” & count & “,”),lblMobile.Text,lblKeyboard.Text,lblMonitor.Text,lblMouse.Text)

f. Save and Publish the App.

3. Pass data from PowerApps to Dynamics 365 CRM using Microsoft Flow

You can pass data to Dynamics 365 CRM using the Patch statement on click button in PowerApps itself but here we are showing it using a flow because Microsoft flow has many capabilities and you can perform so many tasks by connecting your app to different connectors depending on your business requirements.

a. Create a new instant Flow with trigger of PowerApps.

b. Add New Step >> Search for an Action ‘Common Data Service’ >> Create a New record.

c. Select your ‘Environment’ and ‘Entity Name’. We have created another custom entity ‘Electronic Entry’ which has the fields Monitor, Keyboard, Mobile and Mouse which shows the count of these devices.

d. Map the fields by clicking on ‘Ask in PowerApps’. It will automatically map relevant PowerApps fields with the CRM fields.

e. Save the flow.

4. Run the App

You can capture an image from your mobile camera or select an existing image from Gallery. Click on the Detect button. The objects will be identified if it matches with trained objects and the list would show count of each object detected in the image.

When Create button is clicked it triggers the flow which creates a record in CRM as shown below: –

Conclusion

In this way, you can build AI Object detection App which is an easy to use tool, just point and click, to tailor AI in your business as per your requirements. Object Detection lets you to count, locate and identify selected objects within any image. You can use this model in PowerApps to extract information from pictures you take with the camera.

Please visit the Source and support them

The post Power Platform: How to Build AI Object Detector using Power Platform appeared first on Microsoft Dynamics 365 Blog.