Change records per page in Master Data Services

To change the number of records/rows per page in the Explorer view of Microsoft Master Data Services (MDS), do the following:

• Select an entity
• Click on Settings in the top-right corner
• Set "records per page"

Note:
This has to be done per entity and each time the entity is edited. It is not possible to set the records per page one time for all entities.

To change the number of entries in a dropdown list for all entities:

• Edit table master_data_services.dbo.tblSystemSetting
• Update the SettingValue for SettingName "DBAListRowLimit" to the desired value

Cannot map network drive to Sharepoint library

Example error: "Your client does not support opening this list with Windows Explorer"

Steps to check beforehand:

• Add Sharepoint web address to trusted sites within IE
• Login to Sharepoint with "remember this login" turned on

Solutions:

• Use IE 32-bit instead of the 64-bit version, if on a 64-bit Windows:
  c:\program files (x86)\internet explorer\iexplore.exe
• Install Desktop Experience http://technet.microsoft.com/en-us/library/cc754314.aspx
  It is a feature that can be found in the server manager
• Uninstall IE10 - Windows automatically reverts back to IE 9 - or apply hotfix:
  http://support.microsoft.com/kb/2846960

Unable to read exported Excel workbook because of illegal character

After exporting from reporting services, Excel opens the workbook with one of the following errors:

"Replaced Part: /xl/worksheets/sheet1.xml part with XML error. Illegal xml character. Line 1, column 36242."

"Excel found unreadable content in..."

SOLUTION

1. Rename the Excel workbook from *.xlsx to *.zip
2. Within the zip file, open the folder \xl\worksheets and open file sheet1.xml in a text editor, i.e. Notepad++
3. Use Notepad++'s GOTO feature to go to position 36242 and determine the offending character
4. Replace this character in the report's source, i.e. by using the SQL REPLACE function if the source is a plain SQL query
   Note: this is a reactive measure. Each time the error occurs, the character needs to be determined and replaced

For example, these Unicode characters cannot be part of the value in any field in the report:

code: visual representation
26: [SUB]
191: ¿