cancel
Showing results for 
Search instead for 
Did you mean: 

ClassificationPropertyValueProvider in v5.4

Eddy_
Explorer
0 Kudos
683

Hi,

after migrating from 4.8 to 5.4 I experience some problems with the ClassificationPropertyValueProvider which does not provide any values for configured classification features anymore.

It seems that this Provider fetches the feaures by loading the FeatureContainer:

 FeatureContainer cont = FeatureContainer.load((Product) this.modelService.getSource((ProductModel) model));

After debugging into that I found out that the container is only loading the obsolete "Untyped Features". All correct "Typed Features" are missing. Then I tested the following method which is used inside of FeatureContainer#load

 CatalogManager.getInstance().getClassificationClasses(product);

And I saw that the result is always empty. I assume that this could be the problem of the incorrectly loaded features, but I do not know why the classification classes could not be retrieved?

Is there any kind of "extra/new configuration" related to classifications in hybris 5.4?

UPDATE

So, I think I am a little bit closer to the problem now. By digging deeper in to the method

 CatalogManager#getSupercategories

I could see that the method

 Category#getSupercategories()

does no provide ClassificationClasses here, although these classes are referenced correctly as supercategories - which can be checked in the hmc as well.

Maybe anyone had similar problems when migrating hybris to 5.x?

Accepted Solutions (1)

Accepted Solutions (1)

Eddy_
Explorer
0 Kudos

After talking to the hybris support about this issues, they have (more or less;-) confirmed that this is a bug. The only workaround is to use the CommerceClassificationPropertyValueProvider as it is or overwrite it.

We ended up in overriding the CommerceClassificationPropertyValueProvider to our needs.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

I'm experiencing the same issue and use the CommerceClassificationPropertyValueProvider as a workaround. This provider uses another load()-Method, which seems to be unaffected by this issue. It expects a class attribute assignment and returns the corresponding feature values.

Eddy_
Explorer
0 Kudos

Thanks for your reply Felix. Sadly our indexed properties have no setup for class attribute assignments - thats why we were using the "normal" classificationpropertyvalueprovider.