nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Sort order for custom type

hello_wrold

Hello there,

I'm setting up a small document library with Alfresco; inserting my custom documents into the document library works fine but how would I add a feature to set the sort order according to my custom properties.

OOTB the library allows to set the sort order acc. to the builtin types, but I can't use my custom types for sorting. How would I add that option to Alfresco? At least for types that have a natural order like 'order_number' or 'year_published'?

It's not a show stopper (at least not yet) but it would be neat to have that option. Could anyone give me a pointer where to look for something like that?

Thanks,
hello_wrold

Find more posts tagged with

Comments

lementree

Hi,

To add your custom properties in "Sort" options, add them in sorting tag in share-config-custom.xml. make sure your custom property is index enabled.

<config evaluator="string-compare" condition="DocumentLibrary" >
      <sorting>
       <sort label="custom property">namespace:property</sort>
      </sorting>
</config>
‍‍‍‍‍‍‍

muralidharand

You can find more details from \share\WEB-INF\classes\alfresco\share-documentlibrary-config.xmlfile.

  <!–
         Sorting Options

         The 'sort' config element contains the name of the content model field to sort against and can be of the form:
         - short QName string e.g. "cm:name"
         - any other valid sortable fts-alfresco special field e.g. "TYPE"
         
         The field can be optionally followed by |true or |false to indicate sort direction,
         where true = ascending, false = descending
      –>
‍‍‍‍‍‍‍‍‍‍‍‍

Like Sagar said, you can use,

 <config evaluator="string-compare" condition="DocumentLibrary">
        <sorting>
            <sort label="labelName">Short QName|asecending(or)desecending</sort>
        </sorting>
    </config>
‍‍‍‍‍‍‍

<strong>Example: </strong>

 <config evaluator="string-compare" condition="DocumentLibrary">
        <sorting>
            <sort label="Due Date">MyCompNS:DueDate|true</sort>
        </sorting>
    </config>

‍‍‍‍‍‍‍‍

hello_wrold

Thank you! It worked.

Now I'm missing another thing in tables: the table doesn't show a column for my custom property. What I did was to add a custom view-renderer as a sibling to

<sorting>‍

in my share-config-custom

<config evaluator="string-compare" condition="DocumentLibrary">
      <sorting>
          <sort label="Signature">foo:signature|true</sort>
      </sorting>
      <doclist>
          <data-url-resolver>resolver.doclib.doclistDataUrl</data-url-resolver> 
         <view-renderers>
            <view-renderer id="table" iconClass="table" label="button.view.table" index="50" widget="Alfresco.DocumentListTableViewRenderer">
               <dependencies>
                  <js src="components/documentlibrary/documentlist-view-detailed.js" />
                  <js src="components/documentlibrary/documentlist-view-table.js" />
                  <css src="components/documentlibrary/documentlist-view-table.css" />
               </dependencies>
               <json-config>
                  {
                     "actions": {
                        "show": "true"
                     },
                     "indicators": {
                        "show": "true"
                     },
                     "selector": {
                        "show": "true"
                     },
                     "thumbnail": {
                        "show": "true"
                     },
                     "propertyColumns": [
                        {
                           "property": "name",
                           "label": "label.name",
                           "width": "20"
                        },
                        {
                           "property": "cm:title",
                           "label": "label.title"
                        },
                        {
                           "property": "foo:signature",
                           "label": "label.name"
                        },
                        {
                           "property": "modified",
                           "label": "label.modified"
                        }
                     ]
                  }
               </json-config>
          </view-renderer>
       </view-renderers>
     </doclist> 
 </config>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

However, the table is unchanged; no sign of my foo:signature.
Should I put in my view-renderers into another location?

While I'm at it: how can I use different table view-renderers depending on which (sub)folder I'm in. Only some of my folders include documents with property foo:signature.

Thanks,
hello_wrold

m_cortellino

Hi I have the same problem. I could define a custom table view render, but for the entire share application. I didn't find yet a manner to limit the custom view for a specific folder.