PCMBackoffice: No attribute with qualifier categoryPk found

[pratik_a_soni]

I want to configure PCMBackoffice without SOLR. I've made the advanced search configuration to go to flexible search and that reflects on the Simple Search and Advanced Search section.

Whereas when I try to change the catalog from the catalog tree it gives me below error. If I switch to SOLR based search then it works okay but I want it to work with flexible search condfiguration.

Any help will be highly appreciated.

 ERROR [hybrisHTTP16] [AbstractBackofficeWidgetController] No attribute with qualifier catalogVersionPk found.
  de.hybris.platform.servicelayer.exceptions.UnknownIdentifierException: No attribute with qualifier catalogVersionPk found.
     at de.hybris.platform.servicelayer.type.impl.DefaultTypeService.getAttributeDescriptor(DefaultTypeService.java:201) ~[coreserver.jar:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.adjustCondition(DefaultPlatformFieldSearchFacadeStrategy.java:222) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.adjustConditionRecursively(DefaultPlatformFieldSearchFacadeStrategy.java:212) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.adjustConditionRecursively(DefaultPlatformFieldSearchFacadeStrategy.java:204) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.parseSearchQueryAttributes(DefaultPlatformFieldSearchFacadeStrategy.java:189) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.createSearchQueryDataBuilderWithAttributes(DefaultPlatformFieldSearchFacadeStrategy.java:179) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.adjustSearchQuery(DefaultPlatformFieldSearchFacadeStrategy.java:167) ~[classes/:?]
     at com.hybris.backoffice.cockpitng.dataaccess.facades.search.DefaultPlatformFieldSearchFacadeStrategy.searchInternal(DefaultPlatformFieldSearchFacadeStrategy.java:111) ~[classes/:?]

[former_member793780]

Hi Pratik,

Do you have got any solution on getting error on clicking category in PCM backoffice. We are having the same issue on our end.

ThanksSrinivas

[Former Member]

Hi Prathik,

Do you have got any solution on getting error on clicking category in PCM backoffice. We are having the same issue on our end.

Thanks Raghavendra

[pratik_a_soni]

Hi Raghavendra,

OOTB PCMBackoffice works with SOLR, so if you run SOLR index it will create this property in SOLR. And then everything will work good.

Look for productSolr.impex in backofficesolrsearch extension.

I raised this post as I wanted a fallback on Flexible Search instead of SOLR. I don't have a solution for that yet.

Thanks Pratik

[former_member793780]

Hi Raghavendra,

Do you got any solution for above error

Thanks

Srinivas Dontula

[Former Member]

Just a guess based on the stacktrace from the description.

It is possible that you have catalogVersionPk configured as a filter attribute either in simple-search or advanced-search for the type Product (or your custom Product type). Check your *backoffice-backoffice-config.xml if you do have "catalogVersionPk" configured as an attribute by mistake. The right attribute name should be "catalogVersion"

[pratik_a_soni]

Hi Siva,

Actually the catalogVersionPk comes from the Catalog Selector, which is at the left hand side of the PCM Backoffice. I've currently stopped looking into this as we've to first fix the Classification Attribute tab taking huge time.

I'll update here if I get any solution.

Thanks Pratik

[former_member625836]

Hi ,

All I can suggest is standard debugging session. I would start with setting a breakpoint in any of classes in stack-trace and finding out where is this attribute coming from - why is the system even looking for it.

Cheers, Jacek

[pratik_a_soni]

hi Jacek, thanks for the suggestion. I actually did the debug but went to certain extent to see, and later I found certain classes were not decompilable. But I will have to debug more on this.

Also, in the assortment view the same catalog selection works good with Flexible search, so I might have to check what is the difference in both.

Also, compared to Product Cockpit the normal searches in PCM Backoffice are way too slow even though they are both searching on code in simple search or to a specific attribute via advanced search. This is really frustrating. The classification attributes tab takes forever as well.

Lot of performance issues in general.

[former_member625836]

Hi Pratik,

I did some profiling once on this classification tab and the main pain there is an amount of localized editors that are rendered. It may be "easily" fixed with changing the way they are rendered to "lazy-rendering", meaning - all editors for locales different then session lang are rendered after requested rather then right away. You can give it a try: see com.hybris.cockpitng.editor.localized.LocalizedEditor#render.

Cheers, Jacek

[pratik_a_soni]

Thanks Jacek, that's a very good hint. I'll take a look at it. Do you've any other Backoffice related general performance hacks. It would be really helpful.

[pratik_a_soni]

Hi Jacek,

I tried by providing only one locale access to the user but it still takes good amount of time.

I've created a post for this specific issue, if you've any insight you can provide there. https://answers.sap.com/questions/12771752/backoffice-classification-attributes-tab-performan.html

Thanks Pratik

[former_member625836]

Hi ,

I think 's response sounds reasonable. I would in this direction!

Cheers, Jacek