Hi @jddonnell55 

I’ve never seen a limitation. I worked with a company that had 18 once. You obviously would need a larger resource for you instance though. 

Thanks

I have one that has 58 without issue! 

kbeatty21 is right, there is no formal limit, but you may have to add more resources. In addition, you also need to consider the inconvenience of having to search for a specific company/branch.

Benchmarking

We have done some benchmarking which may provide some direction. These benchmarks are specific to our test environment and are not guaranteed to apply to other deployments. For example, we did not implement row-level security restrictions during the test.

Actions Tested: 

• Open company and branch selection menu (top of all screens)
• Open company and branch selector (AR.40.20.00)
• Open invoices and memos list (AR.30.10.PL)
• Load payments and applications (AR.30.20.00) and load 100 open invoices

Branches Tested: 100, 500, 1,000, 5,000 (split in various company/branch configurations)

Environment: 2022 R1, no specific license specified

Results:

Data: for the actions above … 

• going from 100 branches to 5,000 branches increased the response time by about 40%.
• going from 100 companies to 5,000 companies increased the response time by about 5%.

Analysis: the results were inconclusive. We did not observe an inflexion point when the response time started increasing significantly. The response times actually decreased when going from 500 to 1,000 companies and branches. This could have been due to other environmental factors.