Setting “File size limit for attachments” stops solution import

There is a situation that some users might face when the option in the System Settings “Set file size limit” is changed, and they aren’t able to import a solution is receiving a message that “Webresource content size is too big”.

When you change this option, for example to 500, the files like webresources are influenced by this value so it wouldn’t create a webresource with a size higher than 500kb. It will also influence the import of a solution since the internal process will check the size of the web resource.

The maximum size of files that can be uploaded is determined by the Organization.MaxUploadFileSize property. This property is set in the E-mail tab of the System Settings in the application. This setting limits the size of files that can be attached to e-mail messages, notes, and and unfortunately web resources. The default setting is 5MB.

Hope this helps.

 

Advertisements

Import managed solution with BPF prefix new_

There are some issues when you upgrade the Dev environment and you have custom Business Process Flows (BPF) and when you export the solution with that BPF as manage and import in the Test/Prod environment but it is giving an error. This is because the prefix of the BPF is with “new_” instead of the prefix of the solution.

 
There is a known article that explains how to solve the issue:

https://support.microsoft.com/en-us/help/4020021/after-updating-to-dynamics-365-mismatched-business-process-flow-entity

Following the steps will help you to overcome this issue without having to open a support ticket or running scripts directly in the DB.

Have in mind that these steps are to be performed in the sandbox that there isn’t any problem deleting the BPF so the records related to that are all deleted.

Hope this helps.