Mixing
Lightning component limitaion
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
6
down vote
favorite
Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?
lightning-components governorlimits
asked Aug 29 at 10:42
Vee_force
335
add a comment |Â
up vote
6
down vote
favorite
Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?
lightning-components governorlimits
asked Aug 29 at 10:42
Vee_force
335
add a comment |Â
up vote
6
down vote
favorite
up vote
6
down vote
favorite
Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?
lightning-components governorlimits
asked Aug 29 at 10:42
Vee_force
335
Just wondering -- How many records can be shown on a lightning component without doing the pagination. Do Components have the limitaions just like that of VF pages?
lightning-components governorlimits
asked Aug 29 at 10:42
Vee_force
335
asked Aug 29 at 10:42
Vee_force
335
asked Aug 29 at 10:42
Vee_force
335
asked Aug 29 at 10:42
Vee_force
335
335
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
7
down vote
accepted
There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.
At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.
Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.
answered Aug 29 at 11:01
sfdcfox
226k10171385
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.
At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.
Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.
answered Aug 29 at 11:01
sfdcfox
226k10171385
add a comment |Â
up vote
7
down vote
accepted
There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.
At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.
Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.
answered Aug 29 at 11:01
sfdcfox
226k10171385
add a comment |Â
up vote
7
down vote
accepted
up vote
7
down vote
accepted
There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.
At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.
Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.
answered Aug 29 at 11:01
sfdcfox
226k10171385
There's no hard limit built in to aura:iteration, as there was with the Visualforce iterators. The actual limits will be based on exactly what you're trying to do. For example, SOQL from the server-side is limited to 50,000 rows, so that might be practical limitation in the sense that you'll have to at least paginate the queries.
At some point, rendering will take so long that your browser will crash from lack of memory, scripts taking too long to run, etc. On my computer, a single column table was able to support about 50,000 rows before the rendering time started affecting my system.
Should you decide to do this, remember to test your code on mobile devices to make sure it can actually render the page. Infinite scrolling and pagination are recommended for client-performance reasons, which you should take in to consideration.
answered Aug 29 at 11:01
sfdcfox
226k10171385
answered Aug 29 at 11:01
sfdcfox
226k10171385
answered Aug 29 at 11:01
sfdcfox
226k10171385
answered Aug 29 at 11:01
sfdcfox
226k10171385
226k10171385
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f230486%2flightning-component-limitaion%23new-answer', 'question_page');
);
Post as a guest
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
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
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