This project is read-only.
1
Vote

Connected list Paging does not work

description

Hi

Thank you so much for the excellent piece of work.

I am using this as farm solution. I get the data from a connected list webpart. When I try to do paging, eventhough the number changes under webpart, list wont move to next page.

Has any one come across this issue?

Thanks

comments

firozozman wrote Dec 12, 2012 at 7:14 PM

_provider.GetTableData((d) =>
                {
                    data = (DataView)d;
                });
This resulst in "Cannot complete this action" error message when you move to next page in the connected list.

Please help.

mazin wrote Dec 13, 2012 at 9:41 PM

Hi firozozman,

thank you. I tried paging and it seems strange. I got no "Cannot complete this action" error but connecting interface method always returns only first page data. I will keep examining this to find some reasonable way how to support paging of connected webpart.

Mazin

wrote Feb 14, 2013 at 8:13 PM

mehtarahulk wrote Feb 24, 2014 at 12:05 PM

Hi Mazin,

Is this issue addressed or still exists in your latest version? I am facing the similar issue as mentioned above. Below is the scenario is:

I have a list view webpart and trying to connect to MapWebpart. It is successfully getting connected, but results are populated only of first page of list view webpart. As soon as I am moving next page of list view web part, the results aren't getting reflected.

Please help!!

Rahul

panoone wrote Aug 11, 2014 at 5:47 AM

I'm having same issues when applying filters to any column headers.

mazin wrote Aug 17, 2014 at 11:05 PM

First page issue in connection mode still remains as it is SharePoint issue and I still haven't found workaround. :(

panoone wrote Aug 25, 2014 at 11:36 PM

Hi mazin,

I would suggest discarding the connected web part interface altogether and using JSOM to manage user filtering on the LVWP. It works with paging because it grabs the full result set of the current view and then applies any user-applied filters by parsing the URL query string.

Just a thought.

Regards,

Paul