Skip to main content

Sitecore Commerce ProductList getting variant prices for a product

Hello Sitecore Lovers !!!!

Today i will talk little about sitecore commerce OOTB component "Product List", if you have used existing storefront site and observe the list, it looks something like below



So far so good, now i will talk about the actual issue we run into

Problem
Most of the storefront OOTB component works on a product level, but in our case we needed prices from a variant and not from a product, Sitecore commerce has a pricing manager but it was always returning NULL for variant prices and was only returning prices for a product and not variant underneath it.

Details
Now because we knew that this component is using ProductListRepository.cs and if we override it, we could see what pricing logic is written and we can tweak it to get the variant price, but before that we wanted to find why it is not considering variants and only considering a product, Logically it should also fetch its variant prices too

So i started digging by looking into ProductListRepository.cs and found below code which actually is responsible to get prices on a product and a variant level.

if you observe below code in ProductListRepository.cs



 

There is one thing to note here
When ProductEntity is initialized using mode.Initialize method, VariantEntity list is passed null, now because it is passed as null, Variant list will always be empty from the model initialize method, see below



Setting up VariantEntityList is important because other wise no OOTB methods will fill out variant prices.

Now it was time to modify, ProductListRepository to have VariantList to fill and use existing pricing manager to fill variant prices like following


  protected override ICollection<ProductEntity> AdjustProductPriceAndStockStatus(
      IVisitorContext visitorContext,
      SearchResults searchResult,
      Item currentCategory,
      StringPropertyCollection propertyBag = null)
        {
            CommerceStorefront currentStorefront = this.StorefrontContext.CurrentStorefront;
            List<ProductEntity> productEntityList = new List<ProductEntity>();
            string str = "Category/" + currentCategory.Name;
            if (this.SiteContext.Items[(object)str] != null)
                return (List<ProductEntity>)this.SiteContext.Items[(object)str];
            if (searchResult.SearchResultItems != null && searchResult.SearchResultItems.Count > 0)
            {
                foreach (Item searchResultItem in searchResult.SearchResultItems)
                {
                    List<VariantEntity> variantEntityList = new List<VariantEntity>();
                    if (searchResultItem != null && searchResultItem.HasChildren)
                    {

                        foreach (Item child in searchResultItem.Children)
                        {
                            VariantEntity variantModel = this.ModelProvider.GetModel<VariantEntity>();
                            variantModel.Initialize(child);
                            variantEntityList.Add(variantModel);
                        }
                    }
                    ProductEntity model = this.ModelProvider.GetModel<ProductEntity>();
                    model.Initialize(currentStorefront, searchResultItem, variantEntityList);
                    productEntityList.Add(model);
                }
                this.CatalogManager.GetProductBulkPrices(currentStorefront, visitorContext, productEntityList);
                this.InventoryManager.GetProductsStockStatus(currentStorefront, productEntityList, currentStorefront.UseIndexFileForProductStatusInLists);
                using (List<ProductEntity>.Enumerator enumerator = productEntityList.GetEnumerator())
                {
                    while (enumerator.MoveNext())
                    {
                        ProductEntity productEntity = enumerator.Current;
                        Item obj = searchResult.SearchResultItems.FirstOrDefault<Item>((Func<Item, bool>)(item =>
                        {
                            if (item.Name == productEntity.ProductId)
                                return item.Language == Sitecore.Context.Language;
                            return false;
                        }));
                        //if (obj != null)
                        // productEntity.set_CustomerAverageRating(this.CatalogManager.GetProductRating(obj));
                    }
                }
                this.BulkManager.GetProductPricesAndStockInformation(currentStorefront, (IEnumerable<ProductEntity>)productEntityList, false, propertyBag, (string[])null);
            }
            this.SiteContext.Items[(object)str] = (object)productEntityList;
            return (ICollection<ProductEntity>)productEntityList;
        }
 
As you see now, We have initialized VariantEntityList and also we are now calling OOTB method to fill variant prices which is

 this.CatalogManager.GetProductBulkPrices(currentStorefront, visitorContext, productEntityList);

 
We used this method initially and found out that, until this productEntityList does not have the variant list initialized, it will not will not fill any prices for variant and hence VariantEntityList code is introduced  

It took some time to figure out this but DotPeek is your best friend while working with sitecore commerce, Specially when you want to do customization   

Happy troubleshootings !!!

Comments

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!