Workflow Process Corruption

When you have a workflow that is calling in a step a Custom Workflow Activity and you putting a workflow in draft, the Condition Expressions show as “Invalid Condition expression”. When you try to re-activate the workflow it isn’t possible because of the conditions.

This issue might appear if you changed the internal name of the input/output parameter and published the plugin. It will make the condition invalid because, the parameter that was used in the create/update step that is inside the condition is invalid, it is not recognizing the parameter. You need to remove the step and add it again.

Doing the deletion of the step and was able to change the condition branch and redo the Invalid condition expressions and after that, it was able to publish the workflow. Then added the step again. That way it was using the correct output parameter schema name.

Hope this helps.

Advertisements

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.

 

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.

Sitemap editor throws error

When you edit your Sitemap with Sitemap Editor or doing from the Xml, you need to keep an eye for duplicate Subareas in the same Area of the Xml.

If you have two of the same it will give you an error saying that there are duplicate ID’s in the sitemap, so you’ll need to find and remove one.

After that, the Sitemap will be good to be uploaded.

Hope this helps.

Settings submenu not showing

Sometimes I’ve seen some problems when the instance of Dynamics updated to the Dynamics 365 and the Settings group doesn’t show all the options available, at least I’ve seen when was an update.

If this happens you can check if the option Show Group in the Settings area is checked. You can do this by using the XrmToolBox application, with the SiteMap Editor plug-in, or you can download a solution that contains the Sitemap and check if that property is in the Settings area.

Then you just need to upload your Sitemap and the groups will show up again.

Hope this helps.

Business flows not switching by Workflow/Plugin

The problem is when you want to have a Business Process Flow (BPF) that changes automatically when a user changes a field, but that process flow is only changing to that user and not to the others.

For example:

When user1 changes the field, he can see the BPF changing after the reload of the form. When user2 looks at the same record, he can’t see the BPF changed.

This happens because the BPF’s in Dynamics 365  allows multiple processes to run concurrently against the same record and the process that is running for a user might not be the same to the other user.

To have a workaround that works, it is necessary to implement a JScript OnLoad calling that will set the active process in the record to the one that the user wants, for that it can be used Xrm.Page.data.process.setActiveProcess/setActiveProcessInstance.

If you want to know more about the new BPF and how it works, take a look at this post.

Hope this helps.

Alternate Key (Keys) failed to reactivate

There have been some issues when you try to activate an Alternate key but it stays in the state of failed, this might be because the internal process has created the index for the key but it didn’t stay as active in the UI and in the table that saves that information.

If you are OnPrem, what you will need to do is to go to the table of that entity and then on the index folder delete the index that was created. Then you go to CRM and just need to re-activate the alternate key.

If you are Online you will need to submit a Service Request, saying that the Alternate Key isn’t being activated and you want that the support engineer have a look into it.

Hope this helps