Quantcast
Channel: Microsoft Dynamics CRM Forum - Recent Threads
Viewing all articles
Browse latest Browse all 82002

Tabbed views fail to paginate correctly based on user records per page setting

$
0
0

Hi, does anyone have any ideas or knowledge of future resolutions for this issue?

Issue:

 

The tabbed views in CRM for Outlook fail to paginate correctly based on the user “records per page” setting in Set Personal Options.

 

Impacts:

1.       This means the user cannot use the “Export to Excel” feature from the tabbed views as it’s dependent on correct pagination.

a.       It only gives the option “Static worksheet with records from this page”. It won’t export more than your set “records per page” in Personal Options (e.g. if you have 188 records in the tabbed view, and your setting is 100 per page, you’ll see 100 records in Excel). 

 

The pagination isn’t working as designed because I get log file errors when reproducing the issue. If you pin and unpin a few times, you can keep flipping the pagination footer display result and generate log file errors. Also, the Export to Excel feature is dependent on correct pagination of the pinned views. 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.  The pagination exists even without the DisableMapiCaching key and is inconsistent.

 

 

2.       This affects SQL server performance. The end-user’s pagination issue causes them to query and display every row and column of the full e.g. 88,000 records in their view. This impacts their Outlook client performance too and can cause freezes/delays.

 Desired Result:

1.       The grid view footer should show the correct “Records per page” based on user settings and they should only see 25-250 records at a time.

2.       When you click Export to Excel, it should give “Static worksheet with records from all pages in the current view” as an option (see below), and when you get to Excel it should display the full number of results.

 

Repro steps:

 

 

1.       Set up the CRM for Outlook client.

2.       Set your Personal Options “Records Per Page” to 250.

3.       Open an entity, such as Accounts or Contacts, that contain 251 or more records.

4.       Create a pinned view that displays 251 or more records for the entity.

5.       Pin the view.

6.       Verify that the grid view footer shows the pagination incorrectly (i.e. the # exceeds your records per page setting, such as showing 251 records). This may be intermittent by environment, and you may need to look for an environment that is failing to paginate correctly. If you pin and unpin a few times, you can keep flipping the pagination footer display result and generate log file errors.

7.       Click Export to Excel.

8.       In Excel, you’ll notice the max record rows is 250.

 

 

Workarounds:

1)      Add a registry key to the MSCRMClient folder called DisableMapiCaching and set it to 1.

 

Steps:

1.       Log on to the Microsoft Dynamics CRM 2011 Outlook client computers as a user who has installed the Microsoft Dynamics CRM 2011 Outlook client.

2.       Click Start, click Run, type regedit, and then click OK.

3.       Locate and then click the following registry subkey:

HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient

4.       On the Edit menu, point to New, and then click DWORD (32-bit) Value.

5.       Type DisableMapiCaching, and then press ENTER.

6.       Right-click DisableMapiCaching, point to New, and then click DWORD Value.

7.       Right-click DisableMapiCaching, and then click Modify.

8.       In the Value data box, type 1, and then click OK.

9.       On the File menu, click Exit to exit Registry Editor.

 

2)      Use the IE client or advanced find directly, then click Export to Excel. This works because local caching isn’t involved.

Please let me know if you can or cannot repro the issue, or if you know of any current or upcoming resolutions for this behavior.

 

Thanks!

Allan

 


Viewing all articles
Browse latest Browse all 82002

Trending Articles