Quan Mai
Jul 23, 2020
visibility 2246
star star star star star
(4 votes)

New ReferenceConverter method in Commerce 13.21

As you might have heard - ReferenceConverter is your friend. It is very lightweight way to map between the ContentReference and code of catalog content, instead of having to load the content - which is both slow and expensive. Whenever you have chance, ReferenceConverter should be used.

But it is now even better. In Commerce 13.21, ReferenceConverter has a new method to get multiple codes at once. It looks like this

public virtual IDictionary<ContentReference, string> GetCodes(IEnumerable<ContentReference> contentLinks, CatalogContentType catalogContentType)

A common scenario for this new method is when you need to get all variants of a product (by using IRelationRepository), then get all prices or inventories for those variants. Instead of

var allVariantCodes = allVariantLinks.Select(x => _referenceConverter.GetCode(x));

You can now call

var allVariantCodes = _referenceConverter.GetCodes(allVariantLinks, CatalogContentType.CatalogEntry).Values;

The former can result in multiple database roundtrips - depending on how many variants you have. The latter always results in at most 1 database roundtrip. As we all know each roundtrip adds overhead, so there will be a performance improvement.

Jul 23, 2020

Comments

Stefan Holm Olsen
Stefan Holm Olsen Jul 23, 2020 10:43 AM

This is great news, Quan.

I have been wishing for this for some time.

Aria Zanganeh
Aria Zanganeh Jul 30, 2020 12:31 AM

woohoo .. now my schedule jobs that import catalog can run faster!

Mari Jørgensen
Mari Jørgensen Aug 4, 2020 11:05 AM

Great! Keep em coming! ;)

Stefan Holm Olsen
Stefan Holm Olsen Aug 15, 2020 05:03 PM

@Quan Mai: I have a similar optimization wish for batch loading CMS content without first loading core data.

I once raised this thread related to ContentAreaItem batch loading, which resulted in many roundtrips even when I called IContentLoader.GetItems on the content area items.

Do you know whether the CMS team has something planned for this?

error Please login to comment.
Latest blogs
Finding Thomas Part 4 - The Intelligence Layer

I've been finding Thomas for four weeks now. Bear with me — we're almost at the full picture. Quick catch-up : Thomas is the returning visitor who...

Ritu Madan | Jul 14, 2026

The Silent Success: When Your Optimizely SaaS CMS Config Push Succeeds with "0" Changes

  Picture this frustratingly common scenario in headless, code-first development with Optimizely SaaS CMS: You’ve defined a brilliant new element,...

Vipin Banka | Jul 13, 2026

Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026