<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>a!pagingInfo vs topaginginfo</title><link>https://community.appian.com/discussions/f/rules/13969/a-paginginfo-vs-topaginginfo</link><description>Hi All, 
 I saw that Appian has introduced topaginginfo() function. My experience till date tells me that this function does the exact same thing as a!pagingInfo, but slower. Then why did they introduce it? Is there some kind of unique use case for it</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: a!pagingInfo vs topaginginfo</title><link>https://community.appian.com/thread/63386?ContentTypeID=1</link><pubDate>Thu, 13 Dec 2018 05:35:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4364682a-47d4-4c84-863e-77641cca5cdb</guid><dc:creator>sindhug</dc:creator><description>Hi Soumya,&lt;br /&gt;
&lt;br /&gt;
One basic difference  we can sort data  in a!pagingInfo  function and we cannot sort data using topaginginfo function.&lt;br /&gt;
&lt;br /&gt;
a!pagingInfo():function can be used to page and sort the data for a grid component on an interface&lt;br /&gt;
topaginginfo(): Returns a PagingInfo value for use with the todatasubset() function&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
Sindhu&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>