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.

EntityCollection nonMandatoryProcessRule = FetchAllProcessRules(organizationService, serviceTypeGUID, categoryTypeGUID, departmentTypeGUID, CustomerTypeBOOL, false , 0);
          
            List<Entity> nonMandatoryProcessRuleLIST = new List<Entity>(nonMandatoryProcessRule.Entities);
          
            foreach (Entity processRuleRecordET in nonMandatoryProcessRuleLIST)
            {
                if (!ValidateProcessRuleConditions.ValidateProcessRuleCondition(processRuleRecordET, currentEntityET , organizationService))
                {
                    try
                    {
                        nonMandatoryProcessRuleLIST.Remove(processRuleRecordET);
                    }
                    catch (Exception ex)
                    {
                        throw new Exception("Error in removing " + processRuleRecordET+"  check  " + ex.Message);
                    }
                }
            }

The post ERROR : Collection was modified; enumeration operation may not execute – While converting Entity Collection To List<Entity> appeared first on Microsoft Dynamics 365 Blog.

ISSUES:

Not able to login Plugin registration tool (Keep popping up for Credentials)

Resolution:

1. Update latest SDK from the Download tools from NuGet or Quick start Plugin Registration Tool V9.0.0.7

For downloading the latest PRT from VS Nuget packages – this link might be useful

2. Modify using TSL to 1.2 through Fiddler .

Step 1 Open Fiddler and navigate to Tools – Options – HTTPS Tab

Step 2 Under HTTPS tab click on to Protocols link – a Popup will come change the TLS vesion from 1.0 / 1.1 to tls 1.2.  i.e. “ <client>;ssl3;tls1.2 ” and press on ok

Now you will be able to connect to your CRM v9 Organisation with PRT

Happy CRMing

SOURCE : mscrm.com

The post Unable to Connect Plugin Registration tool with MS CRM v9 / D365 SDK appeared first on Microsoft Dynamics 365 Blog.

Error 

Reason

Then press on accept

Hope It helps

Happy Coding

SOURCE : mscrm.com

The post Could not load file or assembly ‘Microsoft.Bot.Connector, Version=3.12.2.4, Culture=neutral, PublicKeyToken=##’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) appeared first on Microsoft Dynamics 365 Blog.

1. Navigate to Microsoft Dynamics CRM > Settings > Administration > Privacy Preferences On the Privacy Preferences Tab

2. select the option “ Specify the Web Application Error Notification preferences on behalf of users” Select the “Never send error report to Microsoft”

Some time this doesnt solve the problem in IE10, IE11.

Click on ‘Compatibility View Settings’ on IE and add the CRM url to the compatibility view settings

The post How to disable Send Report to Microsoft error popup in Microsoft dynamics CRM appeared first on Microsoft Dynamics 365 Blog.

Hi , I got an error will executing a PLUGIN in ISOLATION mode ,

ERROR :   The plug-in execution failed because no Sandbox Hosts are currently available. Please check that you have a Sandbox server configured and that it is running. System.ServiceModel.EndpointNotFoundException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #357E9BEE

There are several cause for this error but most commom is : CRM Sandbox service is not running



OTHER RESOLUTION : Start / Restart the Sandbox services 

Right click ans start the services

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post ERROR : the plugin execution failed because no sandbox hosts are currently available please check that you have a sandbox server configrated ( System.ServiceModel.EndpointNotFoundException) In MSCRM 2011 , MSCRM 2013 , MSCRM 2015 , MS CRM appeared first on Microsoft Dynamics 365 Blog.

The post Convert Image file to stream / base64Image using javascript / jquery . appeared first on Microsoft Dynamics 365 Blog.

Reason 

• Organization “A” conatined attribute ‘new_mscrm’ that was of type “single line” ,Later  We changed that the field  to be an currency Type.
• But in Organization “B” was containg same field ‘new_mscrm’ of type “Single line”.
• When we tried to import back the new solution to test environment we got this Import failure message as the solution we were importing was having a field ‘new_mscrm’ of type Currency

Solution

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post Fields that are not valid were specified for the entity – Importing Solution Error mscrm 2011 , mscrm 2013 , mscrm 2015 appeared first on Microsoft Dynamics 365 Blog.