New answers tagged

2

I'd recommend you go over this code repository which describes how to change any content or metadata here: https://github.com/TridionPractice/tridion-practice/wiki/ChangeContentOrMetadata. But to give you an idea, you'd do something similar to this: // Read the component you want to add ComponentData componentData = (ComponentData)client.Read("tcm:...


1

Marko is correct about the error and what is causing it, but you can only check for the Publication Target the way he describes if you are on version 2013 SP1 at the latest, or a greater version if you have legacy publishing enabled. If you are on Web 8 and up, you can also publish to: Purpose, which is a string value. To see which Purposes you have open ...


3

Following Marko's example of not giving you the exact code, I can propose a different approach. You could utilize the TaxonomiesOwlFilterData class which returns the entire taxonomy in one response in the OWL format (which is basically an XML). That way you do not need to check keyword by keyword but instead search within the xml to find what you're looking ...


3

Well, without giving too much of a solution, you will need to learn to use Core Service API. For that, hopefully, you already have a link to documentation. But in general, here is the high-level tasks which you need to code: get List of all CCategories in an (i guess) Publication. For this you will need to use Filters, to get them. Then for each category, ...


3

string[] publishTargets = new string[] { "tcm:0-1109-1" }; This is the problem in your code. Id you are sending is definitely TcmId of publication, not publication target. TcmId of Publication Target ends up with 65537, so TcmId looks like this: tcm:0-XXX-65537. This is the issue you observe when you try to send ID of Publication instead of Publishing ...


1

As per your error message "tcm:30-158461-65 - Unexpected item type: 65", it is clear that the Page Id is not correct and it's type should be 64 inplace of 65. Please check from where the page is coming and correct its type by updating the PageId to "tcm:30-158461-64"


3

This is known issue. Please ask support for hotfix ECL_9.1.0.17684


0

string str1= content.Remove(content.IndexOf("<primaryIndustry"), content.IndexOf("</primaryIndustry>") - content.IndexOf("<primaryIndustry") + 18); string str = str1; ComponentContent.Content = str; I tried on my own its working now i could able to remove keyword This might help some one. Thanks


1

Atila already explained the purpose of those JSON files pretty well. Regarding where you find them in the Broker DB: these JSON files are published as Binaries (check your BINARY_VARIANTS table). In the DXA Web Application, such items are called Static Content Items and they are cached on file system to improve performance.


2

The _all.json files hold references to other files, but can have additional data (like in the case of \system\cinfig_all.json) BinaryData/PUBLICATION_ID/??/System/mappings These files contain information which is needed by the framework to perform the semantic mapping when creating viewmodels. BinaryData/PUBLICATION_ID/??/System/resources These files ...


5

If you look at the Core Service API documentation, the MetadataSchema property should be of type LinkToSchemaData. public LinkToSchemaData MetadataSchema { get; set; } The way you'd set this in your code is like this: keyword.MetadataSchema = new LinkToSchemaData() { IdRef = meta.Id.ToString() }; Also, you'd want to set the metadata field values as well. ...


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


1

Looking at the Core Service CHM document, it appears that the GetDefaultData method expects three arguments to be passed in: IdentifiableObjectData GetDefaultData( ItemType itemType, string containerId, ReadOptions readOptions) Therefore, I think that this line: KeywordData keyword = (KeywordData)client.GetDefaultData(ItemType.Keyword, category.Id); ...


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


0

Just adding this answer here since there was no accepted answer and might help people. The namespace URI and the service name used for the QName objects are incorrect for ResolvePurpose, ResolveInstruction and RenderInstruction. To get the publish to work, I had to use the right namespace URIs and the service names. Something like this should work: ...


4

Answer to your question: No Oracle Server 12.1.0.2 (Enterprise Edition) - supported Sites 8.5 Oracle Server 12.2.0.1 (Enterprise Edition) - supported Sites 9.0 Oracle Server 19c (19.3) (Enterprise Edition) - only supported in Sites 9.1 Note: 8.1 already out of support, and 8 and 8.1 already dropped from the sdl documentation portal.


0

The most likely reason for failure in the transport phase is connectivity with the deployer having issues. The Publisher service is responsible for creating the transport package. In your case, the package was created and hitting at an issue with the Transport service. Worth review to try increasing the SendTimeout and Polling Timeout values in ...


2

Answer to your question: Q1: For a Multilanguage website, should I have the RelativeUrl parameter set to "en", "es", "de" for each of the languages. ? A1: Yes Example: Add-TtmMapping -Id MAPPINGID -CmEnvironmentId CMENVIRONMENTID PublicationID "tcm:0-8-1" -WebApplicationId WEBAPPID -RelativeUrl en Add-TtmMapping -Id MAPPINGID -CmEnvironmentId ...


1

ComponentData ComponentContent = null; var ComponentContent = client.Read("tcm:13-7666", new ReadOptions()) as ComponentData; *//to read components* var Keyword = client.Read("tcm:12-6867-10", new ReadOptions()) as KeywordData; *//to read keywords* string keywordTitle = Keyword.Title; *//here u will get the title of the family keyoword* client.Save(...


2

What you are looking for is to have the component tcm:13-149625 updated. Since you want the keyword Aromatics & Fibers inserted into the familyKeyword field, you would have to first read the keyword and update the component by inserting a new node which would insert the keyword title to the field. // Parse the component's content into an XML. var ...


Top 50 recent answers are included