topic Re: Using where to get more association types in Alfresco Forum

Using where to get more association types

MartinTichovsky — Tue, 26 May 2020 11:53:27 GMT

Hello, i would like to ask, how can i use WHERE in Alfresco API

GET /nodes/{nodeId}/secondary-children

using WHERE and more than one assocType, for example like

where=(assocType='my:type1') or (assocType='my:type2')

If i use AND or OR in WHERE param, result is the same. I't there some possibility how to get two different associations using WHERE? Thanks

Re: Using where to get more association types

angelborroy — Wed, 27 May 2020 06:58:39 GMT

I don't know if I get you.

AFAIK a secondary child can be only from assoc type cm:contains and primary=false.

Did you define custom secondary associations?

Re: Using where to get more association types

MartinTichovsky — Wed, 27 May 2020 10:02:09 GMT

Thank you for the answer but it's not true. I have custom association in content model like

<child-association name="my:type1">
    <title>My Type</title>
    <source>
        <mandatory>true</mandatory>
        <many>true</many>
    </source>
    <target>
        <class>cm:content</class>
        <mandatory>false</mandatory>
        <many>true</many>
    </target>
</child-association>

I need to get results for two associations, my:type1 or my:type2 in one request using where condition.

Re: Using where to get more association types

angelborroy — Wed, 27 May 2020 10:16:13 GMT

Those are not secondary associations. They are source and target associations.

You need to use these other REST API calls:

GET /nodes/{nodeId}/sources
GET /nodes/{nodeId}/targets

Re: Using where to get more association types

MartinTichovsky — Wed, 27 May 2020 10:59:45 GMT

Are you sure? And what about this https://api-explorer.alfresco.com/api-explorer/#!/nodes/listSecondaryChildren

Re: Using where to get more association types

angelborroy — Wed, 27 May 2020 11:29:30 GMT

As I said before that REST API invocation handles the cm:contains secondary associations.

But if you are not sure, let's wait for someone else that may have deeper knowledge of the API than me.