cancel
Showing results for 
Search instead for 
Did you mean: 

[hybrisHTTP39] [ListViewCollectionBrowserMoldStrategy] Missing Column Configuration for type:

Former Member
0 Kudos

I'm following the [advanced widget search guide][1], in the back office dashboard where the widgets is, i get this message "No type selected". And these warnings appear in console log:

WARN [hybrisHTTP39] [DefaultAbstractCollectorChartHandler] Could not find series values

WARN [hybrisHTTP39] [ListViewCollectionBrowserMoldStrategy] Missing Column Configuration for type:

But no errors, what i could be missing? [1]: https://help.hybris.com/6.5.0/hcd/058fa02799b4474d9adf96d564a19839.html

Edited: I tried to change the condition of search in the MultiConditionSearchController.java class, instead of this

 final List<SearchConditionData> searchConditions = Lists.newArrayList();
         searchConditions
                 .add(new SearchConditionData(approvalStatus, ArticleApprovalStatus.APPROVED, ValueComparisonOperator.EQUALS));
         searchConditions.add(new SearchConditionData(approvalStatus, ArticleApprovalStatus.CHECK, ValueComparisonOperator.EQUALS));
         final SearchConditionDataList innerConditionList = SearchConditionDataList.or(searchConditions);
         final SearchConditionData startsWithCondition = new SearchConditionData(code, "302", ValueComparisonOperator.STARTS_WITH);
         searchData.addConditionList(ValueComparisonOperator.AND, Lists.newArrayList(innerConditionList, startsWithCondition));

  

i have a simpler condition of search:

     private static final String SYNC_FLAG = "syncReplicar"; // flag for replicated items
 
 
 @Override
     public void addSearchDataConditions(final AdvancedSearchData searchData)
     {
         
         final FieldType syncFlag = new FieldType();
         syncFlag.setDisabled(true);
         syncFlag.setSelected(true);
         syncFlag.setName(SYNC_FLAG);
 
         searchData.addCondition(syncFlag, ValueComparisonOperator.EQUALS, Boolean.FALSE);
     }

 







Accepted Solutions (0)

Answers (1)

Answers (1)

former_member632755
Active Contributor
0 Kudos

Hi,

maybe this is a stupid question, but did you initialize the system before entering the backoffice? I remember the log related to first entry to non-initialized system. IF you initialized it please re0start the server and try once again.

We have a bug reported that relates exactly to the problem I described. Edge case, but possible 😉

Cheers, Wojtek

Former Member
0 Kudos

Not really i just tried ant clean all, then ant initialize. I updated the question, before of the change i made it worked, but then i modified for my condition and now doesn't work as expected.