dir-paginate in table with nested ng-repeat
I'm using dir-paginate in a table which is a populated from nested ng-repeat data.
Tables are correctly populated but sorting and pagination when done in one table is resulting all remaining tables also. I used track by $index also, but not working.
<div ng-repeat= "pData in parentData">
PData.item
<table>
<thead>
</thead>
<tbody>
<tr dir-paginate="item in pData.appraisals|orderBy:sortKey:reverse|filter:GenericSearch|itemsPerPage
:10" pagination-id="policyHolderAppraisals"
<td>item.b</td>
<td>item.a</td>
</tbody>
</table>
</div>
angularjs angularjs-ng-repeat
add a comment |
I'm using dir-paginate in a table which is a populated from nested ng-repeat data.
Tables are correctly populated but sorting and pagination when done in one table is resulting all remaining tables also. I used track by $index also, but not working.
<div ng-repeat= "pData in parentData">
PData.item
<table>
<thead>
</thead>
<tbody>
<tr dir-paginate="item in pData.appraisals|orderBy:sortKey:reverse|filter:GenericSearch|itemsPerPage
:10" pagination-id="policyHolderAppraisals"
<td>item.b</td>
<td>item.a</td>
</tbody>
</table>
</div>
angularjs angularjs-ng-repeat
add a comment |
I'm using dir-paginate in a table which is a populated from nested ng-repeat data.
Tables are correctly populated but sorting and pagination when done in one table is resulting all remaining tables also. I used track by $index also, but not working.
<div ng-repeat= "pData in parentData">
PData.item
<table>
<thead>
</thead>
<tbody>
<tr dir-paginate="item in pData.appraisals|orderBy:sortKey:reverse|filter:GenericSearch|itemsPerPage
:10" pagination-id="policyHolderAppraisals"
<td>item.b</td>
<td>item.a</td>
</tbody>
</table>
</div>
angularjs angularjs-ng-repeat
I'm using dir-paginate in a table which is a populated from nested ng-repeat data.
Tables are correctly populated but sorting and pagination when done in one table is resulting all remaining tables also. I used track by $index also, but not working.
<div ng-repeat= "pData in parentData">
PData.item
<table>
<thead>
</thead>
<tbody>
<tr dir-paginate="item in pData.appraisals|orderBy:sortKey:reverse|filter:GenericSearch|itemsPerPage
:10" pagination-id="policyHolderAppraisals"
<td>item.b</td>
<td>item.a</td>
</tbody>
</table>
</div>
angularjs angularjs-ng-repeat
angularjs angularjs-ng-repeat
asked Nov 13 '18 at 11:00
NikileshNikilesh
35
35
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Yes this can be done by using the pagination-id to uniquely identify and group each pagination control for sorting, filtering etc.
e.g.
<ul>
<li dir-paginate="customer in customers | itemsPerPage: 10" pagination-id="cust"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="cust"></dir-pagination-controls>
<ul>
<li dir-paginate="branch in branches | itemsPerPage: 10" pagination-id="branch"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="branch"></dir-pagination-controls>
More information can be found here
https://github.com/michaelbromley/angularUtils/tree/master/src/directives/pagination#multiple-pagination-instances-on-one-page
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53279538%2fdir-paginate-in-table-with-nested-ng-repeat%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes this can be done by using the pagination-id to uniquely identify and group each pagination control for sorting, filtering etc.
e.g.
<ul>
<li dir-paginate="customer in customers | itemsPerPage: 10" pagination-id="cust"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="cust"></dir-pagination-controls>
<ul>
<li dir-paginate="branch in branches | itemsPerPage: 10" pagination-id="branch"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="branch"></dir-pagination-controls>
More information can be found here
https://github.com/michaelbromley/angularUtils/tree/master/src/directives/pagination#multiple-pagination-instances-on-one-page
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
add a comment |
Yes this can be done by using the pagination-id to uniquely identify and group each pagination control for sorting, filtering etc.
e.g.
<ul>
<li dir-paginate="customer in customers | itemsPerPage: 10" pagination-id="cust"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="cust"></dir-pagination-controls>
<ul>
<li dir-paginate="branch in branches | itemsPerPage: 10" pagination-id="branch"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="branch"></dir-pagination-controls>
More information can be found here
https://github.com/michaelbromley/angularUtils/tree/master/src/directives/pagination#multiple-pagination-instances-on-one-page
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
add a comment |
Yes this can be done by using the pagination-id to uniquely identify and group each pagination control for sorting, filtering etc.
e.g.
<ul>
<li dir-paginate="customer in customers | itemsPerPage: 10" pagination-id="cust"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="cust"></dir-pagination-controls>
<ul>
<li dir-paginate="branch in branches | itemsPerPage: 10" pagination-id="branch"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="branch"></dir-pagination-controls>
More information can be found here
https://github.com/michaelbromley/angularUtils/tree/master/src/directives/pagination#multiple-pagination-instances-on-one-page
Yes this can be done by using the pagination-id to uniquely identify and group each pagination control for sorting, filtering etc.
e.g.
<ul>
<li dir-paginate="customer in customers | itemsPerPage: 10" pagination-id="cust"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="cust"></dir-pagination-controls>
<ul>
<li dir-paginate="branch in branches | itemsPerPage: 10" pagination-id="branch"> customer.name </li>
</ul>
<dir-pagination-controls pagination-id="branch"></dir-pagination-controls>
More information can be found here
https://github.com/michaelbromley/angularUtils/tree/master/src/directives/pagination#multiple-pagination-instances-on-one-page
answered Nov 13 '18 at 12:29
tfatfa
373310
373310
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
add a comment |
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
I will not have any control over pagination-id, since this is a nested ng-repeat as u can see in parent div, entire div will be replicated as well as table in that div
– Nikilesh
Nov 14 '18 at 4:48
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
can you put back in track by $index - ng-repeat= "pData in parentData track by $index" and then update pagination-id="'policyHolderAppraisals' + $index"
– tfa
Nov 14 '18 at 11:37
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53279538%2fdir-paginate-in-table-with-nested-ng-repeat%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown