NewFeature
- Configuration for replacing characters in the DocumentsCorePack (DCP) subfolder. Now it is possible to change and replace the list of characters shown in the subfolder. (MB)
BugFixes
- SharePoint Metadata Improvements: These improvements implement the URL and OutcomeChoice types and hide Taxonomy and Image Fields. (AF)
- The condition originally failed to evaluate if the data field contains a Quote. This results that the text isn’t shown or hidden when it should be. The condition works now with quotes in the data fields. (AF)
- SharePoint Metadata: Shows available SharePoint Fields in a combobox feature. A combobox with the list of SharePoint Fields is now available instead of the textbox. (AF)
- Word License Check: Check if Word is licensed and then inform the user. This prevents all unclear error messages connected to a missing license. (AF)
- Now PDF Rendering is possible with special characters like Thai. (AF)
- AdobeSign DataMapping is not showing the existing templates: In the advanced template settings is the list of available datamapping empty when a custom entity is used. (AF)
- Word Ribbon Translation Issue: The buttons were visible, only the labels of the buttons showed “XXX” because there was a problem with the translation. This problem has been resolved. (MB)
- Save Template: Fix for deadlock. (AF)
- <<MToM relationship>> When a tree is created in the task pane in your TemplateDesigner, an errormessage occurs because when you copy the FetchXML from CRM, and do not create it in the RelationshipDesigner, the relationshipname = MTOMLink is missing. (OTO)
- <<FieldProperties>> The dialog is shown, if the field type has no PropertiesFeature. (OTO)
- When you insert a <<Prompt>>, the FieldProperties and other buttons are enabled in the MS Word ribbon. (OTO)
- <<Prompt>> Save the changes after a prompt xml was modified in general page. Initialize again the Prompts page if this page was visited before xml was modified in general page. Delete the first line in xml if you had the Add button clicked. (OTO)
- When you add a prompt name validation, please check for already existing digits at the beginning of the name. (OTO)
- In the Prompt lookup edit form a multi line checkbox is disabled. (OTO)
- Section Configuration Automation: Fixed a variety of bugs, including improper deletion and creation of tables, placeholders, edit fixes, and adjusted the text in the form window. (ES)
- Entities without display name can’t be used as main entity. (AF)
- FieldProperties: a dialog is shown if field type has no properties. (OTO)
- Section Configuration: An issue were fixed, where a configured section would not have its document placeholder and table be displayed due to not having access to the base entity. (ES)
- Table and Placeholder Creation (Section Configuration): Configured sections will now have a relation and a document placeholder automatically created for them. (ES)
- Fix for impersonating fetch as other user with AppAccess connection. Impersonation would currently priorize the user claiming the AppAccess connection over user supplied for impersonating the call, causing issues with localized resources in fetch results. (CK)
- An issue, where s2s profiles would try to refresh a non-existing globaldisco profile, were fixed. (CK)
- Added AdobeSignImpersonateEnabled – Setting, Improved ToolTipsFeature (EL).
- There was an issue when inserting a PNG because the opacity was not applied and image had a black background. (MB)
- DateTimeField issue: Input string was not in a correct format. When the attributes value is not in the fetch result, it gets replaced by minimum datetime value, which causes a format issue when converting to DateTimeOffset.
- DateTime Field had an issue with timezone offset. We implemented same logic as we used for standard datetime fields and this solves the issue that the resulted date or time changes because of difference between timezones. (AF)
- In the DCP Web configuration the setting Use DCP Lookup Dialog cannot be changed. (MB/DB)
- Serverside filename for section export is now the same as in client version. (AV)
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.