Timeline for Pagination with Wrapper Class and StandardSetController
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2019 at 18:34 | comment | added | cropredy |
imagine a second getter in the controller Boolean getHasAnInterestingWrapper() {iterate over getRecordsFromCurrentPage and return true/false;} will build the wrappers twice in the same transaction initiated by the VF page when needing to display the wrappers and conditionally render a button based on hasAnInterestingWrapper
|
|
| Aug 8, 2019 at 17:14 | comment | added | sfdcfox♦ | @cropredy yes, there was a missing line of code... fixed. getRecordsFromCurrentPage() is meant for display purposes in VF. You'd work with the records directly (from the controller) if you were interested in finding particular records. | |
| Aug 8, 2019 at 17:11 | history | edited | sfdcfox♦ | CC BY-SA 4.0 |
added 25 characters in body
|
| Aug 8, 2019 at 16:48 | comment | added | cropredy |
doesn't the getRecordsFromCurrentPage() need a return results; line? Also, as an aside, if the code wanted to, say, iterate over the wrappers to find all wrapped items meeting some filter, the wrappers get rebuilt
|
|
| Dec 29, 2015 at 1:16 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |