This is controlled by MetaObjectOptions

The default value is 1000.  I will register bug though as it should show the correct total number is a the api returns the total count.

We already have a bug that was tested and in testing. which should solve this problem 

OK thanks, it works by updating the MetaObjectOptions but to be honest there is something rotten over this. Or rather the usage of getting organizations in the UI.

1. Just because we have 3634 organizations we don't want to load them all at once in the UI. Which is what happens
2. When opening a contact, the UI will make a call to get ALL organizations and then filter. Look at these requests: Commerce is requesting 3.0 MB of organizations only to
   set the contacts Primary Organization.
   
3. Since the contact view has this behaviour of loading all organizations - which in turn is set by the MetaObjectOptions... we will only really see the Primary Organization if that organization is WITHIN
   the max allowed. Meaning, if we have it set to 1000 max... and a contacts organization happens to be the 1001th... the field will be empty.
4. The same behaviour is used for the Organizations view. Commerce requests ALL organizations in one request. The result looks nice and paginated though, even if the pagination is actually done on the client. Same for the search. You are basically dumping every single organization into the browser memory just to do pagination and search?
   

Is there a way to pull Organizations beyond 1000 without setting the MetaObjectOptions. We have almost 100k orgs and when I set that property my application crashes from memory and CPU overutilization. I did see the GetOrganizationsByPattern(), but I think that method is still restricted by the first 1000.

Loading the contacts/organizations, the right way – Quan Mai's blog (vimvq1987.com) finally got around to write this. Hope it helps