Don't use the query inside any for loops. Instead, query the list of all records and store it in a list or set,  and loop through that list to do the set of logic you wanted to do. No queries inside a for loop is the ground rule for apex programming. Google examples for this approach, there are plenty of examples you can find. Happy coding.

Remove the transient keyword for List and you must be good to go. If you are hitting view state error. Try using maps instead of lists.

Yes You can... As long as it is a custom controller. Ref this link - https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_controller_extension.htm

Can you check if the record type is allowed in your profile? That also could be an issue.  Goto the profile and check if the record type is enabled for that profile under that object.

Use JavaScript Remoting in Vf page.

Ref: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_js_remoting_example.htm

But ideally showing 10000 records in a single page is not a best practice in Salesforce.

Use JavaScript Remoting in Vf page.

Ref: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_js_remoting_example.htm

 

But ideally showing 10000 records in a single page is not a best practice in Salesforce.

Check this out:

https://help.salesforce.com/articleView?id=replacing_online_help.htm&type=0

I think your question is a bigger ask.

Check this post this is the same use case as yours.

https://developer.salesforce.com/forums/?id=906F0000000AVR0IAO

Very simple - Add this below attribute to your VF tags.

<apex:pageBlockSection collapsible=”true” >

Yes - Rollup summary field will fire the trigger. Rollup summary field update happens via a DML operation internally, so it does fire Workflow, Process Builder, and triggers associated to that object.

To avoid this,  exclude this rollup field in your trigger exclusively so that the trigger is not fired when it hits the field update.

Try to initialize the list or object.

For example:

Public List<Account> acc {get;set;}

acc = new List<Account>(); 

Likewise whenever you use this list variable "acc". Try to check size before you do an update or iteration.

Example:

if(!accList.isEmpty()) {

//Your code logic for accList.

}

Ref:… Read more

Try to initialize the list or object.

For example:

Public List<Account> acc {get;set;}

acc = new List<Account>(); 

 

Likewise whenever you use this list variable "acc". Try to check size before you do an update or iteration.

Example:

if(!accList.isEmpty()) {

//Your code logic for accList.

}

 

Ref:… Read more