Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @AEMFrmsDev,
To answer your question, in theory, it is possible, but only if you design the XDP in a way that resets pagination at logical boundaries (template instance + language) instead of relying on the document-wide page counter.
By default:
page n of m on a master page always refers to the entire rendered document and not individual pages.
Repeating a subform or generating multiple instances in one request does not reset page numbering automatically
Master pages cannot “see” template instance boundaries unless you explicitly design for it
So you cannot get this behavior automatically just by repeating the template.
To achieve the use case, you can follow one of the following, and that should help you fix the issue.
1. One Template Instance = One Root Subform (repeatable)
Create a repeatable subform that represents one full template instance:
form
└── TemplateInstance (subform, repeatable)
├── EnglishSection
└── SpanishSection
Set:
2. Use Page Sets (not just Master Pages)
Inside TemplateInstance, define multiple page sets:
TemplateInstance
├── PageSet_English
│ └── MasterPage_English
├── PageSet_Spanish
│ └── MasterPage_Spanish
Then:
Example:
English → break to Spanish Page Set
Spanish → break to next TemplateInstance
This is critical — page sets are the only supported way to isolate pagination scopes.
Thanks
Pranay
Views
Replies
Total Likes
Thank you very much for checking on this issue. Could you please review the attached xdp with page sets, and point where the pagination needs to be placed and how to reset as you mentioned, as i am unable to get that point?, its showing the total counts instead of per each instance/language.
Thank you.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies