Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection size XXXX exceeds maximum size of 1,000. #14

Closed
msreekm opened this issue May 8, 2014 · 10 comments
Closed

Collection size XXXX exceeds maximum size of 1,000. #14

msreekm opened this issue May 8, 2014 · 10 comments
Assignees
Milestone

Comments

@msreekm
Copy link

msreekm commented May 8, 2014

My org has more that 1000 classes and the tool failed to start!
Visualforce Error
Help for this Page

Collection size 1,276 exceeds maximum size of 1,000.

@ImJohnMDaniel
Copy link
Collaborator

@msreekm - How many of the Apex classes are in the default namespace (i.e. not an Apex Class that is part of a managed package)?

@msreekm
Copy link
Author

msreekm commented May 8, 2014

ah ,so even though salesforce removed the 1000 limit for collections , it still applies for Apex:repeat!

@ImJohnMDaniel
Copy link
Collaborator

Yes. That is correct.

Your issue here is a duplicate of issue #8. It has been corrected (for the immediate issue at least) and will be going out on the next release. I expect the next release will be soon (~7-10 days; maybe less).

Thanks for reporting it!!! Very much appreciated.

Cheers!

@ImJohnMDaniel ImJohnMDaniel added this to the 1.6 milestone May 8, 2014
@ImJohnMDaniel ImJohnMDaniel self-assigned this May 8, 2014
@msreekm
Copy link
Author

msreekm commented May 8, 2014

more than 1000 classes in default namespace as well .

great, thanks for the response. waiting for the fix. :)

@ImJohnMDaniel
Copy link
Collaborator

Oh, you do have more than 1000 classes in the default namespace. I see.

In that case, the next release may not help. We still have the underlying issue that an apex:repeat cannot have a result size greater than 1000. Depending on priorities, we will be working be working on that issue using issue #12. I would recommend that you follow that issue for the resolution.

@Condimenting
Copy link

@afawcett This is the issue that I was explaining over Twitter.

I don't think it'd be wise for me to move forward using your project. One of the SFDC managers at my company graciously gave me a sandbox to play around with in my current role ( in an unrelated department), and an old install was left on the sandbox. When I asked some of the devs I'd be working with about the install, they said they weren't pleased with the code coverage and I got an odd look when I asked about forking the project.

However, I do appreciate your prompt reply!

@afawcett
Copy link
Owner

afawcett commented Dec 4, 2016

@Condimenting thats no problem at all. Though btw, the code coverage of this tool has no implication on your sandbox code when you install through the managed package.

@afawcett
Copy link
Owner

Yes, the issue is here...

https://github.com/afawcett/apex-umlcanvas/blob/master/src/classes/ApexClassesSelector.cls#L53

If you have the skills to do so, add a WHERE clause to perhaps reduce the class list by those updated in the last year or with a certain name or prefix?

@afawcett
Copy link
Owner

This has been included in v1.7. @msreekm if you are able to retry please give it a go. Having reviewed John's change it will for sure have resolved this error. If there is another issue we can open a new issue.

@msreekm
Copy link
Author

msreekm commented Jan 21, 2019

@afawcett , I do not have access to that org anymore since I changed job . thanks for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants