V5.5.1 Release Notes

Platform

Browser Support

Content Governance for SharePoint (PH) in SharePoint Online

Supported browsers for SharePoint Online

Content Governance for SharePoint (FA/PH) In SharePoint 2013

Supported browsers for SharePoint 2013

Content Governance for SharePoint (FA/PH) In SharePoint 2016

Supported browsers for SharePoint 2016

ID

Title

Description

Decommissioning (FA and PH)

18487 (Zendesk)

Issue when moving Decommissioning or deleting the Decommissioning Site Collection.

If you move the Decommissioning feature to a new site from where it was previously installed, ensure that you deactivate the Decommissioning feature before you delete the site it is installed on. Not deactivating the feature before deleting the site may result in an error when attempting to activate Decommissioning on the new site ("Checking prerequisites for Decommissioning failed. Decommissioning is already installed and configured at "https://<oldSIteURL> (based on its settings in Governance Hub). Decommissioning can only be installed in one site.

"If this error occurs, check the Decommissioning admin URL in the Governance Hub dashboard, and replace the old site collection URL (of the deleted site) with the new site URL, and then republish the Decommissioning Governance Hub settings.  Activation on the new site should now be successful.

23228

The Set all to default button and the "Requested list changes" section are not properly disabled when transfers are not configured.

If you choose not to transfer any lists or libraries when creating a Decommissioning definition, or if you transfer to a default location, when you click the View Exceptions link located above the search bar, the "Requested list changes" section is enabled even though no list transfers were requested. The Set all to default button is also incorrectly enabled. This error is benign and can be ignored.

Document Center (PH)

14151

Settings incorrectly marked as being mandatory.

If you remove a document library using the Remove option from its context menu in Site Contents, when you a view a page that contains the Library Tile webparts, you may see an error similar to: "Error retrieving statue for library <library name>." To prevent this from happening, delete libraries using the Delete this document library link on the library's setting page.

17572

Document Center unable to remove content types from existing libraries.

Document Center cannot remove a content type from an existing library if that content type originated in the Content Type Hub. This is a SharePoint limitation.

Drop Zone (FA and PH)

490

Contents in the Drop Zone are not getting loaded when the user visits the first time.

In certain circumstances, the user may be prompted with a "page has expired" message. This behavior only occurs in Office 365, on the first login attempt after the browser cache is cleared, and only if the target site has Drop Zone installed. The page prompts the user to refresh the browser, but that does not resolve the issue. Re-enter the target URL in the browser to navigate to the intended target.

519

Button on file upload summary dialog is displaced

When the user resizes the browser window, the file upload summary screen buttons are displaced under the upload screen window. Maximizing the window before the upload avoids this issue.

544

Issue when configuring a Drop Zone profile.

Error received when making unique columns hidden. Gimmal recommends that you do not use columns that enforce unique values as hidden in the Drop Zone profile.

11273

There is a limitation when configuring Drop Zones with a Drop Off Library.

If you configure the target folder to be a Drop Off Library, the Content Organizer Processing timer job must be run. On-premises, you can control how often the timer job is run, but in SharePoint Online, it is run nightly and this cannot be changed.

11517

When you upload a file through Drop Zone, two versions are created: one for the upload and one when setting the properties.

This is a known limitation in SharePoint. There is no workaround for this issue.

13464

"Exclude Blanks" functionality is not working for "Title" column.

If you select Exclude Blanks for a content type title, the SharePoint document parser promotes the properties in a Microsoft Office document to SharePoint. Since you are not setting the property with anything afterwards, the promoted property stays, whereas before (i.e., without the Exclude Blanks option) it would have been replaced with an empty string.

A workaround is available for SharePoint 2013 on-premises only. You cannot disable this on a SharePoint Online environment. See the following information from Microsoft.

13545

Unsupported columns display as a part of Drop Zone profile.

Although computed fields show up on the Drop Zone Profile page, you will not be able to enter values for these fields.

17557

Issue with Drop Zone settings page.

If you right-click on a tab in the Drop Zone settings and opt to Open in a new window or Open in a new tab, the Drop Zone settings window opens in a new tab and displays in the non-working state.

18153

Folders are not supported in Drop Zone.

In certain situations, when a folder or invalid file is dropped on a Drop Zone web Part, the file or folder is not uploaded, but no error message displays. Nothing is uploaded, as folders are not supported.

28875

Issue when selecting Destination Location using Microsoft Edge browser.

The user is not able to select a destination location for the Drop Zone web part when using Microsoft Edge. Suggested workaround is to use another browser to configure the Drop Zone. (Microsoft Edge users can still use Drop Zone, they just cannot configure it.)

19990

jQuery Conflict when using Drop Zone configured on a site using Records Center with Compliance Suite 4.13.2

When the user attempts to use the Drop Zone they are shown the spinning "processing" icon and processing does not proceed. This can be worked around by configuring and using Drop Zones on a sub-site that does not have Records Center activated.

Enhanced Search (FA and PH)

21598

Enhanced Search (FA only) upgrade issue.

When you upgrade the Feature-Activated version of Enhanced Search, the List Item IDs for artifacts in the Master Page Gallery are changed when new versions of the files are replaced. When this occurs, it means that the selected drop-downs will lose the values they held before the upgrade took place, and will require the user to reselect them.

24880

The total page count display is recalculated dynamically on every page load for performance, and for any given page, the "count" is an estimation.

This is an issue with out-of-the-box SharePoint. When calculating page counts, SharePoint attempts a "best guess" estimate at the page count. This count is always recalculated on every page load, as gathering an accurate page count is an enormous performance issue (if the page count is large). 

SharePoint does an approximation of the search results count and Enhanced Search reflects this approximation.

25153
25017

Search results do not display properly if you use special characters by themselves when searching/filtering.

When searching or filtering with a special character by itself (i.e., "@"), SharePoint replaces the character with a blank space, thus preventing you from receiving any search results. If you perform a search or filter and add a special character at the front or at the back of your key word(s), you will be able to receive your search results.

Exception: The exception to this issue is that the wild-card character can be used (i.e., .) and extended characters can be used (à' é, ï, ë, etc.).

The suggested workaround is to not use other special characters by themselves to do a search or filter. The characters must be used in conjunction with other alphanumeric characters.

25181

On the Enhanced Search configuration page in the Governance Hub, when you select Open (...) > Edit Managed Properties for a given Global Configuration Group, the Managed Property Configuration drop-down may not display properly when you create a new entry or edit an entry in the 'ES Managed Properties' list.

When creating a new entry or editing an entry in the 'ES Managed Properties' list, the Configuration drop-down list should display the following drop-down values: Type, Queryable, Searchable, Sortable, and a Crawled Properties box. If the Configuration entry only displays a single description box, this is due to the "Minimal Download Strategy" Site Feature being enabled. Disable the feature, create or edit the Managed Property, and then re-activate the site feature. 

Creating/modifying a managed property from this list is not a common occurrence.

25336
25300

A blank window displays when you click the Cancel and Submit buttons after selecting a Filing location. Although a blank window displays, the selected record is properly copied to the selected Filing location.

When you perform the Compliance Suite Move, Copy, or File Record to a New Location from the action menu on a Record that is returned from the search results, you may experience the following:  

• If you opt to cancel the operation from the resultant screen, a blank window displays. The suggested workaround is to close the tab to return to the search results.
• If you opt to complete the action (Move, Copy, or File to a New Location) after you select the Filing location and you click Submit, the dialog does not close nor does it give a message that the operation was successful. 

Gimmal is looking into this issue for a corrective action in a future release.

26512

Issue with search results displaying in grid view.

When viewing search results in grid view, it may take time for search results to display or the page may be blank. If this happens, refresh the page.

26459

The Search Box Web Part drop-down list (on the Search Experience Profile settings page) displays irrelevant entries.

When selecting a Search Box Web Part from the Search Experience Profile settings page, Enhanced Search retrieves all web parts from the web part gallery under the 'Search' grouping. 

Workaround: Ensure that you select the "Search Box" entry.

26422

Daylight savings time issue.

When selecting a Search Box Web Part from the Search Experience Profile settings page, Enhanced Search retrieves all web parts from the web part gallery under the 'Search' grouping.

Workaround: Ensure that you select the "Search Box" entry.

For example, if you have save a document at 11:55pm, on March 12, it could be saved under March 13 due to the hour difference in daylight saving time. This can impact documents that have a time stamp of approximately 11:00pm/12:00 midnight/1:00am. 

Workaround: Search for documents using a wider time or date range to include the possibility of daylight saving time issues.

26303

A Saved Search link will not execute properly without running a search first.

A Saved Search link will not execute properly without running a search first.

26272

Date fields (i.e., Export Date, Created Date) do not display properly in the exported .CSV file when you export search results using the Microsoft Edge browser.

The Enhanced Search Export to .CSV feature is not supported using the Microsoft Edge browser.

25639

Time searches not permitted in Enhanced Search.

When executing queries against date and time fields, Enhanced Search only permits queries against dates. You cannot search by time in Enhanced Search.

25640

Properties with multiple values may experience inconsistent filter results.

In the "Author" search result column, if you have more than one value (i.e., Jane Smith;System Account), there is no space between these values. Consequently, SharePoint (and Enhanced Search) read this as one value. If you do an Exact Phrase filter, you do not get any matches on values that are concatenated like the previous example. You must filter using a single value, not multiple values, to get consistent filter results.
This is intended behavior, as this is a SharePoint function for a property that has multiple values mapped to it.

19614

Blank CSV when exporting search results with a special character in Chrome.

When exporting search results that contain special characters from the Chrome browser, no results are exported. (CSV file is blank) Work-around is to use IE for exporting search results.

Enhanced Template Manager (FA and PH)

20401

Selecting a subsite location from the asset picker creates an incorrect Templates Library value.

If you open the asset picker, navigate to a subsite, and select the Templates Library, the Templates Library field is populated with a relative reference to the subsite.  
Workaround: Ensure that the Template Host Site URL field contains the full URL to the site that contains the templates library and that the Templates Library field contains only the name of the library itself.

Governance Hub (FA and PH)

23373
24614

Error message received when creating Secure Store entry in Governance Hub.

If the "Minimal Download Strategy" feature is active on the Governance Hub site, you may see an error message similar to 'Web Service Error: Type Error: Unable to set property '5' of undefined or null reference' while editing the password field on a list item in the Governance Hub Secure Store list. If this occurs, refresh the page and try again.

3858

App instance displays in Governance Hub after app is removed from SharePoint Online

When an app instance is removed from a SharePoint Online site, the instance still displays in the Governance Hub as being installed in that site. To resolve this issue, delete the app from the SharePoint Online site's recycle bin. This issue does not affects apps installed and removed from SharePoint 2013 sites.

Metadata Inheritance Rules (PH)

2695

Rule applying blank value to a field does not work.

MIR does not support applying a blank value to a document.

2735

Rule does not work on a List.

Metadata Inheritance Rules are triggered on document libraries and records libraries only.

2739
2811
3158
3530

Rule defined for a Lookup or User/Group field does not work.

MIR only supports Lookup and User/Group fields in rules that are created in the local site. A rule that specifies a Lookup or User/Group field created for a Global Configuration group is not supported.

3005

Rule specifying content type does not work in different farm.

MIR supports rules containing content type references in a cross-farm environment (i.e., two different SharePoint 2013 farms or SharePoint 2013 to Office 365) only if the Content Type ID is identical in both environments.

3478

Transferred rules that contain special characters display unexpectedly.

Transferred rules that contain special characters may display in an HTML-encoded form in the MIR rules list (i.e., a " character may display as &quot). The original, unencoded form of the character is applied to the document.

3691

New Global Configuration Group is not showing as configured.

After you transfer rules to the MIR app for a newly-created Global Configuration Group, the group's Configured column is not marked as configured.Refresh the page to see the checkmark in the Configured column for the Global Configuration Group.

13455

MIR rules are not triggering when you move documents using Explorer View.

MIR rules are not triggering when using Explorer View and Microsoft Office 2003 file formats.
If you encounter this issue, perform one of the following workarounds:

• Convert to modern file formats (e.g., Office 2013).Move documents over using the standard SharePoint UI.
• Turn off the parser functionality on the target site.
  For more information, see: https://blogs.msdn.microsoft.com/josrod/2009/05/11/how-to-disable-property-promotion-in-wss/

13979

Column name not displaying correctly.

If you change the name of a column, the new name does not display in the MIR AutoNumbering (ANR) rule. The old name still persists.

14119

If user performs MRA Send To actions on a document that has an ANR rule, then new auto-number is not generated upon moved document.

When using MRA to move documents with ANR values, if MIR is installed on the destination site, the ANR field must be part of the destination library's default content type in order to generate a new ANR value.  If the ANR field is not part of the default content type, the source document's ANR value will be kept in the destination library.

14372

Issue when using Move functionality with an AutoNumbering rule.

See next section, MIR AutoNumbering Rules and Copying/Moving Documents, for a description and workaround.

15233

Rule Type fields will not display for the local rules created before an upgrade.

When upgrading to MIR 5.2, the Rule Type column will not display its field for local rules that were created before the upgrade.Rule Type is a new column added to MIR 5.2, and it is informational only. It displays the type of rule: "MIR" or "ANR".  You can set the Rule Type manually by editing the rule and adding it.

18051

Issue with MIR Rule when Force Value = None (Applies to FA and PH versions)

When Force Value is set to None, if the target field contains data, then the value specified in the rule should not be applied. However, MIR is incorrectly applying the rule value.

N/A

N/A

In the event where overlapping inherited rules exist (several rules that specify setting the same column value), it is recommended that you create the more specific rules first and then create the less specific rules last. This assures that the more specific rule takes precedence. Gimmal is investigating this issue.

Metadata Rule Actions (PH)

1253

Rule does not work when using Modified By, Document Created By, and Modified columns.

SharePoint stores a text value in the Modified By and Created By columns. The value it stores is the claims string. Therefore, in order for a comparison to evaluate accurately against either of these fields, we recommend that you use the Contains operator and either the user's login name or email address, depending on which of those your system uses for the claims string.

For the Modified column (or any other Date Only column), we recommend that you do not use the Equals operator. This is because SharePoint stores Date Only information with precision to the second, and it is unlikely that your comparison criteria will be accurate to the second.

1261

Rule using 'Starts with' on a People and Group column is not working.

The People column works by using the login name for comparison. Comparisons using the Equal to operator should work as expected, but Starts with, Ends with, and Contains comparisons must be built to accommodate the login name value as SharePoint stores it.

The Group column compares against the group name and should work as expected with all four operators.

3158

"The specified user cannot be found" error displays when editing a rule.

A rule that references a User column will work only in an environment (SharePoint 2013 or Office 365) if that environment shares the same domain as the environment in which the rule was created.

3821

The Modified By name is not reflecting the correct name when record is moved.

After you publish a rule and a record is moved to its Send To Location, the Modified By name changes from the current user's name to "SharePoint App".

3834

MRA app still displays on the Governance Hub Dashboard after uninstallation.

The MRA app still displays on the Governance Hub Dashboard after MRA has been deactivated from the Site Collection Features page and removed from the Site Contents page.

14844

Created "Send To" Action does not display when creating an MRA rule.

The MRA app needs to be added to the site where the Governance Hub resides.

15057

User needs to run the "Content Organizer Processing" timer job to trigger the document to be moved using MRA rule.

The target destination for an MRA "Send To" Location can be a Drop Off Library. If the target location is a Drop Off Library in a Records Center, documents will only be moved to their intended location following the Content Organizer rule when the "Content Organizer processing" timer job is run. For an on-premise installation, this job can be scheduled to minimize the delay, but for a SharePoint Online installation this job runs nightly and documents will not be routed beforehand. This is caused by document parsing being disabled on the record library.

19587

Sending Content fails between site collections when a property contains the ampersand '&' character.

There is a known issue in MRA where, if a document has any property whose value contains an '&' (such as "Dave & Busters"), when MRA is used to send content across site collections (such as from a Team Site to a Record Center site for retention storage), the MRA action fails.  MRA will work when sending content between libraries and/or folders within the same site collection.  The workaround for now is to replace any '&' characters with the word 'and'.

Provisioning (PH)

16086

Provisioning request failed for site template '"Business Intelligence Center."

When requesting a site, the request would fail if a definition was created for a 'Business Intelligence Center' template, and the following error message displays:

"The web template BICenterSite#0 is not available for sites on this tenant."

18171

Issue with definition data not displaying on several wizard tabs.

When creating/editing a Provisioning definition, you may experience an issue where data on some of the definition tabs (i.e., Views, Pages, Web Parts) does not display. This is most likely due to changing tabs too quickly, before data has had time to populate the tab.

Workaround: Press F5 on your keyboard, navigate to another tab, and then return to the current tab. The data should then display properly.

22931

Error message received when adding apps to a site.

When adding more than one app to a site at a time, you may see the following errors in the app's error log:

• "App Provisioning was provisioned with some errors. See log for more details."
• "You must fill out all required properties before checking in this document." 

This error is benign and can be ignored.

4138

If you add the Community Site Feature to the "Features to be Activated" box when creating a request in a SharePoint Online environment, an error message displays.

When you create a site or site collection request and try to add the Community Site Feature to the "Features to be Activated" box, the request fails and displays the following error message: "The user does not exist or is not unique.

"To resolve this issue, you can add the Community Site Feature manually.

4163

When user creates a request and tries to add Access App list to the request, an error message displays.

When you create a site or site collection request and try to add Access App on the Libraries & Lists page of the request wizard, the request fails and displays the following error message, "The file name you specified could not be used. It may be the name of an existing file or directory, or you may not have permission to access the file."To resolve this issue, you must configure the Access App service.

4180

When user creates a site request in SharePoint Online and adds the "BICenter Data Connections Feature" to the "Features to be activated" section, an error message displays.

The system now logs a warning in the Provisioning log that the feature could not be activated, but the Provisioning engine continues with the rest of the process.BICenter Data Connections Feature is not available in SharePoint Online, but is available on-premises.

4181

If user creates a definition using a "My Site Host" template in SharePoint Online (SharePoint Online), an error message displays.

The "My Site Host" template is not available when you create a definition for new site collections in SharePoint Online.

4846

If you create a definition using the following templates, an error message displays:

• Business Intelligence Center
• Academic Library
• Visio Process Repository
• eDiscovery Center

If you receive this error message, you may not be licensed for the features required by that template (i.e., you may need the SharePoint Server Enterprise license), or the template is not available farm-wide.

4851

Missing icon for "Product Catalog" template.

When user creates a definition and uses the "Product Catalog" template, the icon for this template does not display. This is a SharePoint issue.

4859

When user creates a definition using the "Product Catalog" template, an error message displays.

If you receive this error message, you may not be licensed for the features required by that template (i.e., you may need the SharePoint Server Enterprise license), or the template is not available farm-wide.

4970

If user creates a site/site collection request and the title includes a special characters (i.e., @, #, %), an error message displays and user cannot access the site.

If a site/site collection title includes a special character, SharePoint adds a dash at the end of the URL field. SharePoint may not render the hyperlink correctly, resulting in an error.

To avoid this error, you can copy the full text of the URL field and paste it into the address bar.

7670

An internal server error occurs when provisioning sites.

When remote webs are hosted on the "Azure Web Apps" platform, post-provisioning service calls are prematurely disconnected by Azure, resulting in a warning in Provisioning request logs with the following message:

"The remote server returned an error: (500) Internal Server Error.

"Despite the warning, the post-provisioning endpoints should continue processing.

7887

Requested site is not getting provisioned when "Academic Library" template is selected.

Provisioning does not currently support this scenario.