ListViewWebPart query issue while paging

简介: If we change a ListView WebPart's query to implement search while paging, we may get the wrong result.

If we change a ListView WebPart's query to implement search while paging, we may get the wrong result.

Use javascript function like this when execute query can solve the problem.

function FilteResult() {
        var filterFrame = document.getElementById('FilterIframe' + ctx.ctxId);
        if (typeof (filterFrame) == 'undefined' || filterFrame == null) {
            document.forms[0].submit();
            return;
        }
        var postUrl = filterFrame.getAttribute('FilterLink');
        var postUrl = postUrl.replace('Filter=1&', '');
        SubmitFormPost(postUrl);
    }

But I still not quite understand about this.

According to jianyi, it was not written by him so he also doesn't know what it is. But it really works.

 

Get some info from internet:

 

Something else to try if you are still having this problem: I had 2 XSLT DataView WebParts on a WebPart page in SharePoint. Each was looking at a different document library. Links for each document would work fine, but when I would hover over a document and click "View Properties" in one of the webparts, it tried to redirect me to a list item in the other list! What gives?!?! After hours of painstakingly comparing the two webparts and trying to find out the common thread, I stumbled on this nondescript call: ctx.ctxId = In both webparts, this value was the same. When you look at the javascript and ID nomenclature of the HTML contained within, this value is used to differentiate Javascript objects from one webpart to another. So for example: One of the objects is an IFrame. Its name is not "FilterIframe". It is "FilterIframe<somenumber>". When SharePoint's javascript calls are made, this number is used to find the IFrame of the webpart for which the call was intended. So, when I found out 2 of these webparts had the same ctxId, I just took the XSLT of one, pasted it into Notepad, and replaced with a . Pasted the webpart back in and all is well! Cheers, Jeremy http://www.budnack.net/Lists/Posts/Post.aspx?ID=22
According to this, each webpart on a page has a iframe container called FilterIframe<number> to find a webpart's iframe.
And most important, thanks Yunliang!
相关文章
|
前端开发 5G
Search space set group switching(一)
根据R17 38.300的描述,UE可以通过PDCCH monitoring adaptation机制实现power saving的目的,这其中就包括PDCCH monitoring skipping和search space set group (SSSG) switching两种机制。PDCCH monitoring skipping是R17才提出的机制,就是UE 可以在PDCCH skipping的时间内不监视 PDCCH的功能;search space set group (SSSG) switching R16提出,R17进行了部分增强。
使用parted创建大分区时 mkpart Warning: The resulting partition is not properly aligned for best performance.
fdisk不能创建大于2T的分区,创建大分区得用parted,我在用parted创建分区时遇到下面的警告提示
279 0
|
SQL 关系型数据库 MySQL
this is incompatible with sql_mode=only_full_group_by、错误解决方案(亲测可用)
this is incompatible with sql_mode=only_full_group_by、错误解决方案(亲测可用)
4266 0
this is incompatible with sql_mode=only_full_group_by、错误解决方案(亲测可用)
PAT (Advanced Level) Practice - 1119 Pre- and Post-order Traversals(30 分)
PAT (Advanced Level) Practice - 1119 Pre- and Post-order Traversals(30 分)
139 0
PAT (Advanced Level) Practice - 1119 Pre- and Post-order Traversals(30 分)
|
算法
On the Correct and Complete Enumeration of the Core Search Space
在之前的文章中我们讨论了基于graph的DP-based算法,来解决join ordering的枚举问题。 这些DP算法通过join predicate描述的连通性,解决了枚举可能的表组合问题,但join graph本身(即使hypergraph)是无法完整的描述join语义的,因为连通边本身无法描述不同类型的join语义,例如left outer join/semi join/anti join...,因此即使找到了所谓的csg-cmp-pair,也不一定是有效的plan。 这篇paper讨论的就是这个问题,当枚举出一个csg-cmp-pair (S1 o S2),如何判断这是有效的join
498 0
On the Correct and Complete Enumeration of the Core Search Space
|
Android开发
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
510 0
【错误记录】Tinker 热修复示例运行报错 ( patch receive fail: /storage/emulated/0/patch_signed_7zip.apk, code: -2)
|
前端开发 开发工具 git

热门文章

最新文章