STEP 1: Enable SharePoint integration:

1. Go to Apps.
2. Select your portal –> Click on more commands(…) –> Click on Settings

3. Click on “Administration“

4. Go to Setup SharePoint Integration and click on “Enable SharePoint Integration“

5. Click on Enable button it will then ask you to sign in again.

6. Click on Accept to grant the required permissions.

7.  You will get the below message.

STEP 2: Enable document management for table(entity)

NOTE: If document management is not enabled already then follow below steps.

1. Go to Settings –> Document Management –> Document Management Settings

2. Select table

2. Click on Next
3. Click on OK

4. Click on Finish.

STEP 3: Customizing Form

1. Add Document Location subgrid in the form .(The form which you are using in the PowerApps portal)

2. Save and Publish your customization.

STEP 4: Creating and Assigning Table(Entity) Permissions.

1. I am enabling SharePoint Documents for the “Project” table so I have to create two table(entity) permission records one for Project and one for Document Location.

a. Table permission for the Project table. (Don’t forget to add web roles to the table permission)

b. Table permission for Document Location.

Table Name: Document Location

Scope: Parent (This will make sure the user can only see documents that are related to the record)

Parent Table Permission: Select table permission of project from lookup.

Privileges: Read,Create,Write,Append,Append To

Go to Portal, You should able to upload files now.

1. Open any Project record in Portal.
2. You should see the Document Section below from where you can “Add files” or Create “New folder” in SharePoint.

3. Click on the “Add files” button you are shown a pop-up window from where you can choose the files to upload.

4. You can see the New Folder is created in SharePoint for that Particular Project and file is also uploaded inside the respective folder.

5. Click on “New Folder” to create new folder this will get created inside the parent folder in SharePoint.

6. From the portal, you can go inside the folder and then upload files that get uploaded inside the respective folder in SharePoint.

• “Add Files” in newly created folder.

• New Folder and Files in SharePoint.

The post Enable SharePoint integration in PowerApps Portal ( Dynamics 365 Portal ), SharePoint Document in Microsoft power pages appeared first on Microsoft Dynamics 365 Blog.

You need a quick and easy way to store and access files related to opportunities, accounts, quotes, contacts, and more. This includes contracts, quotes, offers, images, etc.  then you should be looking for is Dynamics 365 integration with SharePoint.

Click here for blog : Enable SharePoint for Power pages | Power portals | Dynamics 365 Portals

1 – clock on setting and then Advanced Settings. If you can’t find this, make sure you are logged in as a user with administrator privileges.

2 – Open Settings and choose System – Document Management

3 – Choose the option Configure Server-Based SharePoint Integration

4 – On the wizard that will open, indicate if your SharePoint is Online or On-Premises. The SharePoint integration can connect to both. It can even connect to multiple SharePoint sites, but they all have to be either online or On-Premises.

5 – Assuming you chose Online on the previous step, now you one need to enter the URL of the SharePoint site you want to use.

You can simply copy the URL from when you are on the SharePoint site main page and the wizard will validate it when you click Next.

6 – Assuming the validation succeeds, the final step to enable your Server-Based SharePoint Integration is clicking the Finish button.

You can now go back to your Document Management screen and select which entities should be enabled for SharePoint folders.

Click on Document Management Settings.

In the pop-up window, you check the entities under which you anticipate storing documents and click Next.

You can then define the folder structure. Here are your options:

• Not check the Based on entity checkbox – Folders will not be automatically created
• Check the Based on entity checkbox and choose Account – the structure will have account as the primary folder, and sub-folders based on the actual account names will be created under it
• Check the Based on entity checkbox and choose Contact – the structure will start with the contact primary folder, and sub-folders based on the actual contact names will be created under it

Make your selection and click Next. We might have to wait a little at this point as the document libraries will be created. Once you’ve done that, you can click Finish.

The integration is now live! On the Dynamics 365 side you will now see a document option under the entities you enabled. On the screenshot below you can see the document that we created for an Account. Notice that its storage is on SharePoint.

How to use it for document management

• Edit this using the Opportunity record. Let’s say you have a prospective customer named Wonderful World who is working on a grand opening order. They go through your sales cycle and develop documents such as NDAs, specifications, offers, quotes and images. You need a place to store this data securely and easily access, edit, and share it within your organization.

• Notice the File tab circled in blue. When you click on this little guy, two beautiful things happen to him in the background.
  • A new folder is created in SharePoint. This folder is where we store all the files related to the deal.
  • Your Opportunity folder will be nested in your new Wonderful World account folder.
• A new, empty Opportunity folder looks like this: Here you can choose to create a new document, upload a file from your device, or change the SharePoint location. Easily upload 3 documents (image, PDF, Word document) from your laptop.

Click on Upload, and you’ll see an Upload Document dialog box.

Choose the files from your PC (or OneDrive even).

Now you have access to SharePoint. You should see three files inside the Opportunity folder. You will also see a nested Opportunity folder within your Wonderful World account folder. piece of cake. Another nice thing is that SharePoint users can access these files. No need to own a Dynamics 365 license. This means that other members of your organization can contribute to these documents as needed.

The post How to Enable Dynamics 365 CRM and SharePoint Integration Step by Step appeared first on Microsoft Dynamics 365 Blog.

Click here if your file in SharePoint doesn’t load or corrupted.

Click here for How to Enable Dynamics 365 CRM and SharePoint Integration Step by Step

This question has been going around on the power users community forums and I thought it would be nice to blog it because it is always gets tricky trying to save files from different data sources , so for this we have a single source the outlook connector and there is two destination.

1. Sharepoint File
2. Dataverse Email Attachment

Lets Get Started!

So the starting point is the Flow Trigger which is “When a new email arrives (v3)”

Then the next step is to get the Attachments from the Email by using the below steps:

1. Loop on the attachments from the triggerOutputs
2. Use Get Attachment (v2) to get each attachment

Then to save to sharepoint that was pretty easy .. Just using the outputs of the Get Attachments (V2) has worked from the first Go!

Name and Content Bytes!

What about dataverse?

So for DataVerse we are creating a new email activity and adding the attachments to it as below but it wasn’t straight forward adding the attachment.

Step 1: Easy : Create the Email Activity

Step2: Add the Attachment and here is a couple of tricks

1. when you select the table name attachments there is 2 tables , make sure you select first one.
2. Attachment(Attachments) just pass null from the Expressions Pane … Weird but how this is working.
3. Entity: Do not select one of the available Options , just use enter a custom value and type email otherwise you will get an error.

The entity with a name = ‘4200’ with namemapping = ‘Logical’ was not found in the MetadataCache. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=3040485, MinActiveRowVersion=3040485, MetadataInstanceId=51707140, LastUpdated=2021-08-04 11:35:57.770

And when it came to setting the body ; it wasn’t as easy as passing the content bytes directly as with sharepoint ..

Attempt 1: Pass Content Bytes directly .. Error Received

The attachment body should be a valid Base 64 string

Attempt 2: Convert Content Bytes to base 64, No error received, file was attached but corrupted

Attempt 3: Binary ???!!! .. Weird but this is what worked for me run successfully and file was not corrupted.

Hope this is useful!

The post Move Attachments Note or email to SharePoint using Power automate flow Dataverse Microsoft Dynamics CE | CRM appeared first on Microsoft Dynamics 365 Blog.

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.