The pagination exists even without the DisableMapiCaching key and is inconsistent.Ģ. The DisableMapiCaching reg key method is designed for performance reasons to force data retrieval from the server each time a grid view is opened, rather than retrieving from the local SDF cache files, and is not for the purpose of allowing/disallowing pagination. Also, the Export to Excel feature is dependent on correct pagination of the pinned views. If you pin and unpin a few times, you can keep flipping the pagination footer display result and generate log file errors. The pagination isn’t working as designed because I get log file errors when reproducing the issue. if you have 188 records in the tabbed view, and your setting is 100 per page, you’ll see 100 records in Excel). It won’t export more than your set “records per page” in Personal Options (e.g. It only gives the option “Static worksheet with records from this page”. This means the user cannot use the “ Export to Excel” feature from the tabbed views as it’s dependent on correct pagination.Ī.
The tabbed views in CRM for Outlook fail to paginate correctly based on the user “records per page” setting in Set Personal Options.ġ. Hi, does anyone have any ideas or knowledge of future resolutions for this issue?
0 kommentar(er)
