This could be done by installing platform hotfix KB 2492490 Build no. 32146 or higher.

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb$EN-US$2492490&wa=wsignin1.0

I just would like to explain how this Hotfix works in short.

In order to bypass the previous hardcoded limit of 5000 Max no. of xml records to send, after installing the aforementioned platform hotfix or higher, you have to set a key like that on every RTC Client machine in the ClientUsersSettings.config file

<add key="MaxNoOfXMLRecordsToSend" value="integerValue" />

(where integerValue is an integer value that represents the max number of xml records to send when using the Export to Microsoft Office feature)

Since the Classic Client handles this value directly from the IDE changing “Max. no. of XML records to send” property from Tools > Options, I have been requested if there is a more flexible way to manage this key in the ClientUsersSettings.config file.

I have then tried, in this blog, to mimic what Classic Client does and developed a simple page and codeunit to let the user change dynamically the value for this key and if the key is not present, by adding it directly to the ClientUsersSettings.config file with the desired value (this would also make the Hotfix deployment faster).

The code in the attached .txt file is quite simple and is based on .NET interoperability using the following:

System.Environment

http://msdn.microsoft.com/en-us/library/system.environment(v=VS.90).aspx

System.IO

http://msdn.microsoft.com/en-us/library/system.io(v=VS.90).aspx

System.XML

http://msdn.microsoft.com/en-us/library/y3y47afh(v=VS.90).aspx

link

http://blogs.msdn.com/b/nav/archive/2011/11/22/manage-max-no-of-xml-records-to-send-option-from-role-tailored-client-with-net-interop.aspx?CommentPosted=true#commentmessage

Duilio Tacconi, Microsoft Dynamics Italy