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 ...


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"?


1

You want to change your setup to a content mashup (that is, an integration with SDL Tridion Docs), and you don't want to use the new Add-on service, then get your new resources from the following • Content Delivery\roles\deployer\deployer-dx-combined\ for the combined Content Deployer upgrade If you just want to perform a minimal upgrade, without changing ...


1

The error is caused by the fact that customMeta/valueType = null


1

The issue was that the NPM dependencies were not resolved correctly. The documentation is misleading online. I was able to manually resolve the dependencies and packages. I will add a comment to update SDL documentation and Velu's blog as well.


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