Quan Mai
Optimizely
Nov 2, 2018
visibility 4503
star star star star star
(4 votes)

New updates to Business Foundation

Business Foundation is one of the oldest parts of Episerver Commerce, and it is the foundation of some of the most important features in Commerce: contact management (along with it, organization management). But it's hard to say it does the job perfectly.

Previously Contact Management in Commerce Manager only shows the first 1000 contacts. To make this grid shows more than 1000 ones, you would need to update the maxListObject to a bigger value, and that comes with a performance consequences: a bigger number means slower load, and higher risk of timed out or out of memory exception. 

In Commerce 12.11, it's changed.

That limitation is now lifted, and you can have a many contacts as you want without changing the value.

Now Business Foundation supports proper paging. Which means you no longer have to use inferior paging, and this actually, truly works.

Without breaking a sweat!

One customer with around 340.000 contacts asked us if there is any way to improve the time for loading their Contact Management views. They had to increase the maxListObject value to show all the contacts, and it takes them around 6 minutes for that views to load. Of course, that is far from perfect. I was able to get access to their database and by upgrading to Commerce 12.11, I could test how much improvement the new change bring.

Now the view is loading within few seconds.

The change is at API level, so if you are using Business Foundation for other purposes, you will still benefit from it. Just make sure to use 

BusinessManager.List(string metaClassName, FilterElement[] filters, SortingElement[] sorting, int? start, int? count);

instead of 

BusinessManager.List(string metaClassName, FilterElement[] filters, SortingElement[] sorting)

which still relies on the value set by maxListObject.

Commerce 12.11 will be availble earlier next week.

Nov 02, 2018

Comments

Johan Book
Johan Book Nov 2, 2018 09:16 PM

A very welcome improvement!

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026