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.

Support for NXQL 'ORDER BY ecm:path' in the CoreSession.queryAndFetch API

rg1_

It seems reasonable that the CoreSession.queryAndFetch API would not support the NXQL 'ORDER BY ecm:path' clause. If this is the intended behavior, then the NXQL documentation should be updated to include this restriction.

Find more posts tagged with

Comments

Florent_Guillau

It's not really a NXQL restriction but a restriction of this particular API

rg1_

I agree. Yet the NXQL Documentation includes numerous references to CoreSession.queryAndFetch API enhancements/restrictions like this one. Would you consider including the following clause in the NXQL ecm

Florent_Guillau

Thanks for the remarks, I updated the doc.