Variants shown as Not published, although dates are OK and IsActive = true in the database

Member since: 2010

Hi, everyone,

We are having a Commerce installation that gets the product info from InRiver. We are not working on the connector or InRiver, a partner company is.

They have set a variant as unpublished and then they tried to publish it, however, in the interface, this is still not displayed as published. When I checked the DB, IsActive is true and dates are correct as well. The partner company says that this happens only for accessories and spareparts, but not for genericvariants, although I can't effectively test this myself.

What could cause this, any ideas on what to check?


#187780 Feb 02, 2018 10:49
  • Member since: 2016

    We've had these issues as well, coming to an unsynchronized state for specifically commerce content. Bitwise adding the SaveAction ForceCurrentVersion to the save method helped us here all though I don't know the underlying cause. :(

    So try (or tell your partner company to try) always saving commerce content with 

    _contentRepository.Save(writeableContent, SaveActions.Publish | SaveActions.ForceCurrentVersion, AccessLevel.NoAccess)

    and see if that helps.

    #187782 Feb 02, 2018 11:10
  • Member since: 2011

    IsActive is overridden by Epi_IsPublished and the status of the version, if any. So they need to make sure the content is properly published, like Joel suggested

    #187785 Feb 02, 2018 11:28
  • Member since: 2010

    Doesn't this mean that ServiceAPI that is in use doesn't use the proper save action?

    // PUT request was used: episerverapi/commerce/entries/1982


    #187789 Edited, Feb 02, 2018 13:18
  • Member since: 2011

    ServiceAPI works on a lower level (CatalogEntryDto/MetaObject), but it should work just fine. Can you look into ecfVersion to see which versions are there for that entry? 

    #187790 Feb 02, 2018 13:32
  • Member since: 2010

    Yes, I can see that now, I've been browsing through the code and couldn't spot an error. It's version of Service API.

    These are the relevant fields when executing:

    SELECT TOP 1000 [WorkId]
      FROM [dbTestCommerce].[dbo].[ecfVersion]
      where name = 'xx' and languagename='en'

    Thx in advance!


    #187795 Feb 02, 2018 14:07
  • Member since: 2011

    They have one published version, and one checked out one. How do they know the content is not "published"? They might be looking at the checked out version. 

    #187801 Feb 02, 2018 14:48
  • Member since: 2010

    The interface suggests it (and restarting the app doesn't change this, so it's no caching):


    #187802 Feb 02, 2018 14:58
  • Member since: 2010

    Could this be just a UI bug?

    This is how it looks like in Manager:


    #187803 Feb 02, 2018 15:05
  • Member since: 2011

    You have two versions, and for some reasons which I'm not sure (it should logically be otherwise, but the code might work otherwise), the catalog UI is picking up the wrong, older version. Can you open the version gadget and delete the "unpublished" version to see how does it behave?

    #187808 Feb 02, 2018 15:45
  • Member since: 2010

    I cannot delete versions from the Version gadget...

    #187810 Feb 02, 2018 15:49
First   1 2   Last