GraphQL requests using the items() field

SDL Tridion Sites 9

GraphQL requests using the componentPresentations() field

Use the componentPresentations() field to query Component Presentations specifically. This type of query is similar to the items() query. This sample query fetches Component Presentations from the Publication with ID 16 in SDL Tridion Sites. The Component Presentations must additionally meet the following requirements: They must have a metadata key name set to the value Sitemap. They must be the result of rendering Components based on a Schema with ID 815. They must have been rendered using a Component Template with ID 825. They must have been most recently published between 25 May 2018 at 10:07 AM, Central European Time, and 28 July 2018 at 7:48 AM, Central European Time. The following fields should be returned for each Component Presentation: The cursor (used for fetching the next batch of results) The item type (should always be 2048, that is, Component Presentation) The ID of the Component rendered as this Component Presentation The title of the Component The date and time at which

SDL Tridion Sites 9

GraphQL requests involving custom metadata filtering

This series of samples demonstrates the use of scope while filtering on custom metadata. The following basic query gets a number of properties for all items that have the custom metadata Keyword "mykey" set to the value 42: { items( filter: { customMeta: {scope: Item, key: "mykey", value: "42"} } ) { edges { node { id publicationId namespaceId itemId itemType title customMetas { edges { node { key value } } } } } }} Now we explore how changing the filter affects the results of the query. To limit your query within the scope of one or more Publications, change the filter: part of the query, changing scope: Item into scope:Publication: filter: { customMeta: {scope: Publication, key: "mykey", value: "42"} } To further specify that the returned items should only be Publications, add itemTypes to your filter: filter: { itemTypes: [PUBLICATION], customMeta: {scope: Publication, key: "mykey", value: "42"}} By setting itemTypes to [Publication], the scope property in customMeta becomes irrelev

SDL Tridion Sites 9

GraphQL request for getting Publications containing topics tagged with a specific Keyword

To find out which Publication or Publications contain the content that is tagged with a specific Keyword, execute a specific items() query. This type of query can be useful in, say, a mashup scenario, where you want to identify the context in which your "mashable" content resides. In this example, you query for all Publications containing content tagged with all three specified custom metadata key-value pairs: { items( filter: { itemTypes: [PUBLICATION], and: [ # Items in the Publication that are tagged with a Taxonomy Keyword with ID 9006 { customMeta: {scope: ItemInPublication, key: "FMBCONTENTREFTYPE.logical.element", value: "9006"} }, # Items in English { customMeta: {scope: ItemInPublication, key: "DOC-LANGUAGE.lng.value", value: "en"} }, # Publications matching a given product release name { customMeta: {key: "FMBCONTENTRELEASENAME.version.element", value: "9019"} } ] } ) { edges { node { id publicationId namespaceId itemId itemType title customMetas { edges { node { key value }

SDL Tridion Sites 9

GraphQL request for getting all Pages with a specific Keyword

You can filtering on key-value pairs, combining them in AND or OR expressions as needed. The following query fetches the ID, title and URL of all Pages (which by definition means only SDL Tridion Sites content) with a Keyword "010 News" or "000 Home" set in the "Sitemap [Navigation]" Category: { items( filter: { itemTypes: [PAGE], or: [ {keyword: { categoryName: "Sitemap [Navigation]", key: "010 News"}}, {keyword: { categoryName: "Sitemap [Navigation]", key: "000 Home"}} ] } ) { edges { node { itemId title ... on Page { url } } } }} The response might look something like this: { "data": { "items": { "edges": [ { "node": { "itemId": 262, "title": "000 Home", "url": "/index.html" } }, { "node": { "itemId": 331, "title": "000 News Index", "url": "/articles/news/index.html" } }, { "node": { "itemId": 332, "title": "Example News 2", "url": "/articles/news/news2.html" } }, { "node": { "itemId": 334, "title": "Example News 3", "url": "/articles/news/news3.html" } }, { "node": { "itemId": 335,

Tridion Docs main documentation

GraphQL requests using the items() field

This section contains a number of sample items() calls to demonstrate how to query content from Tridion Docs. GraphQL request for getting all Components of a certain content type If your authors give each Component a value for a custom metadata key you created called contentType, you can use a GraphQL request to filter by content type. This lets you create, say, a dynamic webpage showing all content of that type. GraphQL request for getting all pages tagged with a specific Taxonomy Keyword This sample imagines that you have created a Category called "City" and have created a Taxonomy of Keywords in this Category, representing various cities. GraphQL request for fetching results in batches (paginated) You can set a maximum number of results to return for your query, and if you request the cursor property back, you can use the cursor to fetch another batch of results, starting from where you left off last time. GraphQL request for getting Publications containing topics tagged with a spec

SDL Tridion Sites 9

GraphQL samples

This section contains a large collection of GraphQL request samples, to illustrate a variety of common query scenarios. GraphQL request for getting a Publication mapping from its URL If you know the URL of a published Publication, you can retrieve its Publication mapping (which includes the ID of the Publication). GraphQL request to get the Component Presentations on a Page Use the containerItems field in your Public Content API call to fetch all the Component Presentations on a specific Page. GraphQL requests related to linking The sample requests in this section are related to resolving, getting and rendering links. GraphQL request to apply merged conditions Use the contextData parameter in a query to pass conditions. In a content query, add this parameter to a componentPresentation() or page() query; in a Taxonomy query, add this parameter to a keyword() or categories() call. GraphQL requests using the items() field This section contains a number of sample items() calls to demonstra

GraphQL requests using the `items()` field

Recommendations

GraphQL requests using the componentPresentations() field

GraphQL requests involving custom metadata filtering

GraphQL request for getting Publications containing topics tagged with a specific Keyword

GraphQL request for getting all Pages with a specific Keyword

GraphQL requests using the items() field

GraphQL samples

GraphQL requests using the `items()` field

GraphQL requests using the componentPresentations() field

GraphQL requests involving custom metadata filtering

GraphQL request for getting Publications containing topics tagged with a specific Keyword

GraphQL request for getting all Pages with a specific Keyword

GraphQL requests using the items() field

GraphQL samples