The Condition field functionality property allows you to define dynamic content
that is either displayed or removed from the final document based on a certain condition.
This webinar also covers this topic in detail.
A condition block is represented by a  placeholder in the template and is also called content control (1).
The following step by step description will show you how to insert a condition field
with the DocumentsCorePack Client in your template.

The example below shows a template that contains two conditions fields (if else)
and the result with the one remaining field.

Figure 1: Example of an if else statement

 

If you are not sure how to get to the insert fields option, please take a look at this article first.

1. Use the Condition field option
   

   

   Figure 2: Insert Condition field

1. Give your condition a descriptive name.
   A descriptive name makes it easy to re-use existing conditions in a template.
   

   

   Figure 3: Condition field dialog

    

2. Configure the setup of your condition fields
   Enable or disable the automatic creation of an else block (1).
   If an else block is created you can define the layout of the
   inserted condition fields (2)(3).
   

   
   

   Figure 4: Condition field layout options
   

    

   Below you can see an example of the two formatting options when using an else block. 
   The else block is inserted next to each other (1) and below each other (2).
   

   

   Figure 5: Appearance of the fields in a template when using below each other

    

   PLEASE NOTE: A else block is always the negated version of your real condition.
   You always can identify such an element by the prefix "<!>" before the actual name.
   
   

Related Topics:
Insert a Hyperlink

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

The Condition Designer (1) has a similar look and feel as the standard "Advanced Find" Dialog in Dynamics365.
Also, the available options are similar. 

The Condition Designer (1) is part of the Condition Field functionality of DocumentsCorePack. Details
about this functionality can be found here.


Figure 1: The condition designer within the condition field dialog

This step by step description will show you how to the condition designer to create your condition. 

1. Select a field from the drop-down
   
   Figure 2: field selector
   
   
2. Select an operator
   Depending on the field type you will see different available operators.
   ​
   Figure 3: Operator selection
   
   
3. Select or enter a compare value
   Depending on the data type of the field you either have an additional control
   (1) that opens a new dialog (2) to select the
   compare value. Or you can enter the value directly by typing.
   
   Figure 4: Selection dialog for picklist elements
   
   Below you can see examples of other data types. 
   
   
   Figure 5: Example of a date field
   
   
   Figure 6: Example of a string fiedl
   
   
4. Repeat steps 1 to 3 to add other lines to setup more complex condtitions
   PLEASE NOTE: All single lines are brought together to one single condition.
   
   
5. Group your lines [optional]
   Select the required rows by using the menu that opens when you hit the arrow button.
   
   Figure 7: 
   
   The selected rows will stay highlighted (1). Select the required grouping option (2).
   
   Figure 8: Two highlighted rows
   
   After you selected the grouping a box will visually show the grouping
   
   Figure 9: Result ofter grouping

 PLEASE NOTE: A few fields like owner or customer (special look up fields) are not available on the actual parent level, but can be always reached by selecting the next level drop down for this element. 

This blog article outlines how to trigger subworkflows from an AutoMergeWorkingItem workflow.  

❶ The main workflow needs to be based on “AutoMergeWorkingItem”.

❷ Add a Wait Step that waits until the AutoMergeWorkingItem is inactive.

❸ Add another Step called “DCPWorkflowSandbox: TriggerSubWorkflow”.

Figure 1: Subworkflow from AutoMergeWorkingItem workflow

In the step displayed below,  select the Primary Record URL of the AutoMergeWorkingItem and the Subworkflow you want to execute. The entity type needs to match! 

​That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

If you are manually updating the latest versions of the AutomergeOnPremise Solution for Dynamics CRM 365 or installing a servicebased DocumentsCorePack for an IFD environment based on Dynamics CRM 365,  your server is required to have .net Framework version 4.6.2 installed.

(Using any of our installers will prompt you for the .net framework requirement, if not found on the target machine.)

If you only have .net 4.5.2 your workflows will terminate with the following error :

Unhandled Exception: System.MissingMethodException: Method not found: '!!0[] System.Array.Empty()'. 

Due to microsofts mandatory TLS 1.2 communication starting  July 2017 for 3rd party applications, all of our products have been moved to use .net 4.6.2

SharePoint paths limitations are hard coded. The maximum path length is 260 characters. If that limit is exceeded, you get the SharePoint error 414. This article outlines how to avoid this error. 

Minimum requirements: DocumentsCorePack v.167or higher 

mscrm-addons products offer several default ways to shorten SharePoint paths:

1) We provide you with a default shortening to a maximum of 30 characters + GUID for each folder name. 

SharePoint folder maximum length:

This setting cuts SharePoint folder names that are longer than a certain amount of characters. 

2) We provide you with a default shortening to a maximum of 128 characters for each file name. 

3) ShortIDs: We create a 6-characters ID alternatively to the well-known 36 GUIDs of Microsoft Dynamics 365.  

It is recommended to activate ShortId to avoid the SharePoint error 414 you get because of the path limitations of 260 characters. With ShortId we create a 6-characters ID instead of the 36 GUID like you can see in the example below. 

​

How to activate a ShortID for DocumentsCorePack

To create a ShortID for DocumenstCorePack simply navigate to Settings > DocumentsCorePack in your Microsoft Dynamics 365  application.

Here, please add/enable the following options: 

Use short Documentation Logic

The setting in the figure below cuts SharePoint path automatically. 

Figure 2: DocumentsCorePack settings

 

4) Use an alternative field for the generation of paths (e.g. instead of account name we can use a unique account number field)

For the SharePoint folder name attribute:

SPFolderNameAttribute: enittyschemaname;attributename|

e.g.: Account:ptm_name

Please note: Even though the creation of short paths is a very valuable feature, existing paths cannot be shortened anymore, unless very specific criteria are met. Manual interaction is always required.

For further information on how to correct SharePoint paths exceeding the limitations, please have a look at this blog article. 

That's it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com!

There are no strangers here; only friends you haven’t met yet.

- William Butler Yeats

 Thank you for joining us at the eXtreme365 in Long Beach! It was a pleasure for us to be part of such a great experience and to meet new business partners. 

Figure 1: eXtreme365 in Long Beach

 

​This year’s eXtreme365 did not only impress with an amazing location, it was full of surprises! Indeed it was a high-energy event where we could gain a deep-dive understanding of Microsoft´s roadmap, expert community insight on overcoming real-world challenges, and exceptional relationship building.  

 Also, we had the chance to present our solutions and ideas in front of a responsive audience. Michael Dohr outlined excellently why working with partners it the key to success. He highlighted the values and benefits of our partner network, as well as the main advantages of our solutions for Microsoft Dynamics 365. 

Figure 2: Beautiful Long Beach

All in all, the event was a complete success for partners and customers. We want to thank the organizers of that outstanding event for their commitment! 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

 

If you execute your workflow but it does not work correctly, there are several ways to troubleshoot your workflow. In most cases these problems are caused by the user itself, having forgotten to fill fields or having picked the wrong values.

 Here are a few things that you can check if your workflow fails: 

Process Session
Open your process and navigate to the process sessions, like you can see highlighted in yellow below. These are logged sessions of every time our process was executed. 

Figure 1: Process Sessions

Open the regarding process session and check at which step your workflow has failed, and investigate further into this particular step. Please also take a look at the details mentioned there: 

Figure 2: Process session details 


AutoMergeWorkingItem
Check the created AutoMergeWorkingItem to see what went wrong. Do this especially if the workflow fails at the Create: AutoMergeWorkingItem step. 

Next, open the advanced find in Dynamics 365 and search for the entity MSCRM-ADDONS.COM AUTOMERGEWORKINGITEMS and look after the one that fits your workflow session (sort by created on, for example). It will also have the name you gave it in the workflow. 

• Is the Primary Record URL filled and pointing to a Record in your Dynamics 365 that can be merged with the template?
• Is the Template to Execute and the SaveAs Value filled?
• Is the CreatedDocument filled (In our case it is not and therefore the document generation itself has failed) If this is not filled, check if the Template works with the Primary Record or not?

• Check the Return Value, if it has an Error Message like you can see in the figure below:

If you are attaching to e-Mail, open the e-Mail record and check if sender and recipient are filled, if the document is attached and in which state the email remains (Draft, Pending Send): 

Check your Dynamics 365 permissions if you are allowed to send e-Mails and if you are allowed to send e-Mails on behalf of this user. Check if the recipient is allowed to receive e-Mails. 

With these hints and a little Dynamics 365 knowledge, you will be able to find the cause and resolve it.

 Should nothing of this work, send us an e-Mail to  support@mscrm-addons.com and include a proper description of the issue, screenshots and your findings and analysis so far.

​

​

​

​

Following the european unions GDPR requirements, AttachmentExtractor version 2017.5 and later are introducing a new plugin/workflow tracing note and email deletion, allowing for removal of the files moved to sharepoint with AttachmentExtractor, when the note or email containting the link file in CRM is being deleted.

 Please note, that the deletion tracking is disabled per default.

How to enable the deletion of Sharepoint items:

 Download and import AttachmentExtractorCore solution version 2017.5 or later ( Download AttachmentExtractorCore 2017.5)

Create two settings as described in this article : Link

"EnableCascadeDelete"

A value of "true" enables the plugin/workflow in general.

A value of "false" will not remove any file on sharepoint.​

  ​

"ThrowOnCascadeDeleteFailure" 

Value of "true" means, that you will not be able to delete the item in CRM, if the plugin fails to remove the linked file(s) on Sharepoint

Value of "false" means, that the item in CRM will be deleted, regardless if the plugin fails to remove the linked file(s) on Sharepoint​. 

​ 

​

 ​

There are no strangers here; only friends you haven’t met yet.

- William Butler Yeats

 Thank you for joining us at the CRMUG Summit in Nashville! It was a pleasure for us to be part of such a great experience and to meet new business partners. 

​The atmosphere at CRMUG Summit was perfect, which was not only due to the well-selected location but also to the excellent speakers and truly informative sessions. The event was amazing and full of great people. From the very first moment, we knew that being a Gold Sponsor for this event had been a great decision. 

Figure 1: Nashville - 10 years of CRMUG Summit photo gallery  

During the – nearly familiar atmosphere – we managed to talk to a lot of great people and we also had the opportunity to listen to the outstanding sessions held by MVPs on a personal basis. Amazing keynote speakers, small group sessions, gripping speeches and lots of networking opportunities converted this event into a Microsoft Dynamics 365 festival. 

All in all, the event was a complete success for partners and customers. Being part of this event was a great and really very special experience! We want to thank the organizers of that outstanding event for their commitment! 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

This article outlines how you can activate extended features of SmartBar for Dynamics 365.
Steps described here can be necessary after installing SmartBar from Microsoft AppSource or after a manual solution import.


Warning messages or notifications

If you get one of the underneath warning messages or notifications it is an indicator that the “SmartBarServerExtension” solution is not installed.

 


Please follow these steps to install it:
  • Download the SmartBarServerExtension.zip file (Download Link):
     

  • Open Dynamics 365 -> Settings -> Solutions -> hit “Import”
  • In the popping up dialog select the “SmartBarServerExtension.zip” and follow the wizard.

After refreshing the Dynamics 365 page the functionality should be available.


Support
In case of any questions or problems please do not hesitate to contact our support: Support Link