Hot answers tagged

7

The GraphQL result sorting currently supported the following fields only, It's possible to extend GraphQL extension in sites 9.1. CREATION_DATE INITIAL_PUBLISH_DATE ITEM_ID ITEM_TYPE LAST_PUBLISH_DATE NAMESPACE_ID OWNING_PUBLICATION_ID PUBLICATION_ID TITLE UPDATED_DATE Example: { items( filter: { customMeta: {scope: Item, key: "mykey",...


7

To get the Component Presentations on a Page, There are two different types of component presentations, dynamic and embedded. Embedded templates are used when a component is added to a page and published only in the context of that page. Dynamic means that the component can be published out to the broker, in your case I would assume it's an embedded CP, then ...


6

To fetch the As-is data template less publishing, called “untyped content” from GraphQL: { page(namespaceId: 1, publicationId: 5, pageId: 730) { itemId title url content { ... on UntypedContent { data } } } } Updated: In Sites 9.5 Templates Data-only publishing, and semantic content models (custom ...


5

Try adding a customMeta under the filter section: customMeta: { key: "ishtype.object.value", value: "ISHIllustration" } You may also be able to do this in code, using the Public Content API (PCA) client. Something like this: var client = ApiClientFactory.Instance.CreateClient(); InputComponentPresentationFilter inputFilter = new ...


4

Hotfix CD_11.0.0.13730.zip is now available for this issue (via FTP or it can be requested from Support as well).


4

Rick already answered to clarified. Indeed!, there is no OOTB way to retrieve individual components fields values of published DCP and page JSON outputs, but It's possible to do a Graph-QL extension using the ‘CDGraphQLSchemaExtension’ extension point. This is available in Sites 9.0 but with limited support as it is currently not documented. It will fully ...


4

GraphiQL comes "out of the box" with Tridion. If you can locate your api endpoint, just add /graphiql and you should find that it works. So for example, on my local test setup, the API is at http://cd.local:8081/cd/api and graphiql is at http://cd.local:8081/cd/api/graphiql You can use GraphiQL straight from the browser but you'll need to arrange for OAuth ...


4

So assuming your publishing your Structure Group information then this should be stored in the TAXFACETS table alongside other taxonomy information (categories and keywords). The following works: var filter = new InputItemFilter(); filter.ItemTypes = new List<FilterItemType>() { FilterItemType.PAGE }; filter.PublicationIds = new List<int?>() { 5 }...


4

Not sure if this is helpful, but one way I've retrieved binaries is by first retrieving an "untyped" component (i.e. templateless publishing), and then using the result to find and retrieve any binaries. The second query for binary(ies) should give a URL where the image can be retrieved: query GetUntypedContent { component(namespaceId: 1, ...


3

Well, I did some PoC in the past on this topic, you can read more about this, and to answer your question YES, you can have PCA api working with WEB 8.5. You need to follow below steps. Create new Broker and state_store DB with Tridion Sites 9 DB scripts. Install Sites 9 Discovery,Deployer and Content service. Create new Topology Type and mappings and map ...


3

added InputSortParam inputSortParam = new InputSortParam(); inputSortParam.setOrder(SortOrderType.Ascending); inputSortParam.setSortBy(SortFieldType.LAST_PUBLISH_DATE); this fixed the problem. based on error i figured out both fields order and sortBy on are required InputSortParam.


3

Unfortunately, the DD4T JSON (or DXA R2 JSON for that matter) is basically just a blob of text for the Content Service. Indeed, the GraphQL Content Service provides a feature to return JSON content as JSON within the GraohQL result (rather than an escaped JSON string), but that is as far as it goes; it is not really structured data which can be filtered or ...


3

I get similar results in my Sites 9 setup. It could be a bug because I also cannot filter on keyword title, only on keyword key. However you can request the Keyword key to be part of the response: { categories(namespaceId: 1, publicationId: 5) { edges { cursor, node { itemId, title, itemType, children { edges { cursor, ...


2

It works for me, I'm able to reproduce this issue my side. if the graphql query used variables in parameters then always expected to send the value of the query variables to be {}. if we pass query variables value to be null then this issue occurs. Expected Request: {"query":"query myquery($uri: String = \"tcm:5-394-64\") \n{ \n page (cmUri:$uri) {\...


2

Saurabh - I believe you can filter on schema ID or Title too? schema: { title: SCHEMA_TITLE }


2

Per the error and this example in the documentation, the argument contextData.type probably isn't a valid ClaimValueType. Perhaps you meant type: STRING instead of type:"STRING"?


2

AFAIK - and I can say officially it is not supported and tested, but I can’t think of anything which would break it. this is all unofficial Note: As long as you don’t have SmartTarget in there, as in 8.5 SmartTarget was the Fredhopper version. From Sites 9.0 - officially we support CM's first upgrades. On the positive side, the java version on 8.5 and 11.0 ...


2

The error shown in the logs says 'could not locate the root of the configuration'. Could this have anything to do with this (I know it's a different version, but the issue might still apply to 9.1) https://gateway.sdl.com/CommunityKnowledge?articleName=000005260


2

As Alvin correctly points out, there is not currently a componentPresentation root query that takes a page parameter. The nearest would be the items query, which when returning pages, can include the componentPresentations contained within that page, and they will have the associated page context in those results. E.g. { items(filter: {itemTypes: [PAGE], ...


2

Your data looks a lot like DXA R2 JSON, so I assume you’re using DXA (TBBs at least)? It also looks like the Categories are marked as publishable, in which case the TBBs will only include the Keyword IDs; the DXA Model Extension should take care of dynamically retrieving and expanding the Keyword Data.


2

Welcome to StackExchange. It would be great if you can provide information on what you have tried and specific implementation questions, if any. There is no cookie-cutter solution for data-only publishing. You will find a lot of useful information in this link. From the content manager side, the schema design is completely open to the developer / content ...


2

You can use the Public Content API available through GraphQL and query pages based on metadata in the Content Data Store. The documentation for the Public Content API is available here. Just tag the page with keywords through a page metadata schema and use a GraphQL query to fetch pages that have specific keywords. For instance, say you want to fetch page ...


2

As suggested, Support ticket is indeed required to correct this feature/issue. A possible workaround could be to resolve component links yourself in your application code. This can done as Alvin mentioned, using separate GraphQL queries (instead of relying on DXA Model Extension/Service). This would roughly translate to following steps for a DXA-based ...


2

This is a defect. R&D are working on a fix, at this point I'm waiting for confirmation on what timeline I have and will update the note here with the hotfix number. The only alternative I see at the moment is to iterate through the items returned and make an individual request for each binary item download URL. At up to 1000 a page that's not going to be ...


1

Take a look at the Building a website with semantic content models: a development experience from TXS NASA 2021. I should give you a useful start. https://www.youtube.com/watch?v=ojPPsrnbQOo


1

Running the risk of over-simplifying... Define your content models (on paper, not in Tridion). Translate that to a set of Tridion Schemas that allow for the content to be captured. Work on your semantic content models as mentioned by others, to further refine the mapping between your Content creation models and your Content Delivery models (i.e., how ...


1

Ended up going a different way. Instead of trying to get the labels/configuration externally, now I'm pushing them from DXA to the consuming applications. Way to obtain the settings within DXA: string websiteConfiguration = SiteConfiguration.ContentProvider. GetStaticContentItem("/system/config/myModule.json",WebRequestContext.Localization)....


1

AFAIK - you could use downloadUrl to download the binary from the content service. Alternatively, you can use the item filter query to get all the binaries in that publication which will give you all the binaries. { items(filter: {itemTypes: [COMPONENT], publicationIds: 16225}) { edges { node { itemId publicationId ... on ...


1

As mentioned, do follow up with Support. For a little more context here is the GraphQL requests to render links documentation that describes how you can also use the contextData argument to control how links resolve. If you're managing or resolving the links yourself (e.g. in DXA or other application), the GraphQL requests to resolve links documentation ...


1

you can try to delete all configuration without parent item, Only the DefaultEnvironment should have no parent. Query for the same would be like this. ""delete from CONFIGURATION_VALUE where ITEM_ID in (select ID from CONFIGURATION_ITEM where ID not in (select LINKED_ITEM_ID from CONFIGURATION_ITEMS_LINKS) and ID != 'DefaultEnvironment') delete from ...


Only top voted, non community-wiki answers of a minimum length are eligible