01 - General Discussion Forum - Recent Threads

Require Reports option to list Where Used at the folder level

Priyanka Singh — Mon, 20 Apr 2026 06:14:08 GMT

It would be helpful to have a Reports option at the Graphics folder level to view Where Used details and determine whether files/objects are used. Currently, this information is available only at the individual file level, requiring manual checks for each file/object. A folder-level report would make it much easier to identify usage of Graphics folder files/objects, including whether they are used or not.

Due to procedural constraints, sometimes not all illustrations can be accommodated, and some files may remain unused. With a Reports option, it would be easy to identify whether a graphic file is used or not. This visibility would support better planning and coordination between writers and illustrators and help reduce unnecessary effort by avoiding the creation of unused files in an ongoing release or in the next project.

Deleting released objects

Ragnar Branæs — Mon, 16 Feb 2026 09:16:57 GMT

I know that the whole purpose of releasing objects in the database is to keep them safe and prevent changes. However, we have an issue that requires deleting released publications and maps from the database.

Can anyone please provide a method to do this?

I have administrative rights, but in this case that is not enough - or so it seems.

We are presently on Tridion Docs 15.1.6

RE: Deleting released objects

Ragnar Branæs — Wed, 15 Apr 2026 05:23:05 GMT

I am aware of the issues related to released objects. The database is after all designed to keep released objects "safe". In our case, we are going through a large reorganization, and our database has been duplicated into "ours" and "theirs" repository. We need to delete a few publications and bookmaps from "their" repository. In my experience, if you start by deleting the publication (all versions!) you can continue with the next level objects - bookmaps - and so forth. I appreciate all help here, and I am sure that we are not the only Tridion Docs customer with such needs.

Mark Novembrino , I saw your input on the use of an API, thanks! I will dig into that, as I do not know how to access the database with an API.

RE: Deleting released objects

Mark Novembrino — Tue, 14 Apr 2026 17:10:52 GMT

It is possible to revert the publication output status from released back to draft using the PublicationOutput 2.5 SetMetadata web service API. Using this API, you can set <ishfield name='FISHPUBSTATUS' level='lng'>Draft</ishfield>. Once all the publication outputs are back in draft state, you can delete the publication. More info about the API here: docs.rws.com/.../publicationoutput-2-5-setmetadata-70082

RE: Deleting released objects

Ragnar Branæs — Tue, 14 Apr 2026 08:16:04 GMT

Hello everybody!

I see from many replies here that as an administrator I am supposed to be able to release objects. What I need to do is to release certain publications and bookmaps, nothing else. I have moved to Tridion Docs 15.2, I am an administrator, but I am still not able to delete released publications. It is imperative that I can do so after a major reorganization in our company.

Please advice.

regards Ragnar

Capability to log ClientConifig access for troubleshooting and audit

Masayuki Yamane — Fri, 03 Apr 2026 02:12:01 GMT

I think logging capability is very essential for all network access, and that should be the same with ClientConfig files sync'ed by Publication Manager and Authoring Bridge. However, according to both clients (i.e. Publication Manager and Authoring Bridge) and Tridion Docs servers don't have capability to extend logging level for ClientConfig sync. Is that true?

That is actually a problem when I troubleshoot ClientConfig sync issue with RWS Support. RWS hosts six production servers for us, and those are workload balanced. With that condition, unnecessary ClientConfig file sync happens when the timestamp would mismatch than previous file sync. Even worse, each of users seem to be experiencing the unnecessary file sync issue differently, possibly due to workload balancer. So, even though redeployment of ClientConfig files by RWS Support improved the consistency across six production servers for some users, I am hearing from some other users, hey, still experiencing that issue. Although RWS Support have ever tried to make the folder content consistent again and again, that won't be suppressed fully. We can't identify which production server the issue is remaining.

I don't know what the challenge is with RWS to implement that logging capability. But, if that logging capability wasn't possible for RWS, can RWS take different approach to identify required ClientConfig file sync?

Content Importer general access for authors

Stacey Meggs — Fri, 20 Mar 2026 14:17:30 GMT

Our team is responsible for our company's Tridion Docs instance (v15.2). We've been using TD for 10 years. We find that Content Importer works great for translated content. However, it is more error-prone for English content. In fact, when we outsource conversion to DITA, the vendor always chooses to avoid Content Importer, instead opting for their custom methods instead. Aside from migrations, English imports are rarely requested by our authors. When they are needed, our support team does them for the authors who request them. However, the use cases are growing and there is more of a demand for English content imports.

Do you generally allow access to Content Importer for your authors?
If so, what risks has that presented?
What are your general best practices for authors using Content Importer?
Or do you generally limit it only to support roles?

Thanks for your perspective.

RE: Content Importer general access for authors

Elizabeth Gschwind — Mon, 23 Mar 2026 16:36:41 GMT

Hi Stacey - a couple of things. At FICO, only our administrators perform imports. We always import into an "Import" folder (with subfolders for each project) so the writers can check the imported files before moving them into the main repo. (If you are importing updated versions of topics that are already in the repo, this won't work because the object will be overwritten at its current location.) I hope this helps.

RE: How to switch from old DTD-based XML to DITA in Tridion Docs?

Frank Ralf — Tue, 10 Mar 2026 10:35:01 GMT

Many thanks for all your pointers. And sorry for not replying earlier. The project had been delayed and will only start later this year.

Best regards,

Frank

How to switch from old DTD-based XML to DITA in Tridion Docs?

Frank Ralf — Tue, 11 Feb 2025 10:30:10 GMT

Hi,

A customer has a Tridion Docs installation that uses DTD-based XML from pre-DITA times. What is the best way to switch to DITA in the Tridion Docs environment?

Best regards,

Frank

Setting multiple values for a metadata field using DocumentObj25.Create shows invalid entries

Mark Novembrino — Tue, 03 Mar 2026 23:50:11 GMT

Some weird behavior here that is vexing me...

I making a web API call -- DocumentObj25.Create -- to create a topic in a Tridion Docs 14 environment.

For one of the metadata fields I am setting, there are multiple taxonomy values.

When I look at the created object in Publication Manager, two of the three values are listed as invalid.

I performed the same operation manually in Publication Manager and looked at the log to see how Publication Manager was passing the metadata via the same API call. The metadata structure looks exactly like the one I am passing with my API call, but the result is correct. The values are not listed as invalid.

Here is what my metadata looks like:

<ishfields>
<ishfield name="FTITLE" level="logical" xml:space="preserve">Name of my topic</ishfield>
<ishfield name="FCUSTOMFIELD1" level="version" xml:space="preserve" ishvaluetype="id">17573177, 17574057</ishfield>
<ishfield name="DOC-LANGUAGE" level="lng" xml:space="preserve">en-US</ishfield>
<ishfield name="VERSION" level="version" xml:space="preserve">1</ishfield>
<ishfield name="FCUSTOMFIELD2" level="version" xml:space="preserve" ishvaluetype="element">86301381, 86301382, 87394644</ishfield>
</ishfields>

FCUSTOMFIELD1 is set correctly from the API call.

FCUSTOMFIELD2 is not set correctly. One value is set, but the other two are marked as invalid.

When I look at the logs in Publication Manager, when I create an object manually, I see the same exact metdata structure for FCUSTOMFIELD2 as what my API call is passing. But Publication Manager sets it correctly, and my API call does not.

Also note that if I limit the FCUSTOMFIELD2 to one value in my API call, it works without a problem.

RE: Setting multiple values for a metadata field using DocumentObj25.Create shows invalid entries

Mark Novembrino — Wed, 04 Mar 2026 17:54:24 GMT

Hi, Dave. I figured out the problem. My application is dependent on an another application that forwards the metadata to my application already configured as ishfields. There were non-breaking spaces between the commas in the field values and I didn't see them. After running out of ideas, I just guessed that maybe there was something unusual like that. When the non-breaking spaces were replaced with regular spaces, the metadata was set in TD properly. Problem solved.

RE: Setting multiple values for a metadata field using DocumentObj25.Create shows invalid entries

Mark Novembrino — Wed, 04 Mar 2026 14:17:42 GMT

Thanks for the quick response, Dave. The msiamtch of "id" and "element" is because I was trying both. Typically I'm using "id" for everything, but I tried using "element" to see if that fixed the problem. It did not.I'll have a look at the logging as you recommended and dig further.

RE: Setting multiple values for a metadata field using DocumentObj25.Create shows invalid entries

Dave De Meyer — Wed, 04 Mar 2026 07:34:08 GMT

Hi Mark,

If we have two behaviors something is different. What caught my eyes first is that you pass FCUSTOMFIELD1 using ishvaluetype="id" and that you pass FCUSTOMFIELD2 over ishvaluetype="element". Is that intentional, from a product perspective I would have expected both to be aligned, or is this yours?

Furthermore, from a CMS perspective we are just saving the value that came in. It is however your (custom) IMetadataBinding implementation that validated the incoming values in the first place upon save. And your (custom) IMetadataBinding implementation decides why it is not returning labels. So looking at the logging of that implementation on how it acts would be my next step.

Best wishes,
Dave

RE: Is there a way to cancel translation jobs that use the File Export template in Tridion?

Eva Nauerth — Mon, 02 Mar 2026 06:13:27 GMT

Thank you, Andriy!

Is there a way to cancel translation jobs that use the File Export template in Tridion?

Cobina Price-Jones — Wed, 10 Dec 2025 21:45:48 GMT

In Tridion 14, we were able to translation cancel jobs with the status "Export completed" if, for example, we found that we did not have sufficient budget. In Tridion 15, it is no longer possible to cancel a job with this status. Is there another way to revert the statuses of all of the files in a translation job to "To be translated"? We could manually update the files for each publication in the job, for each language, but this would take a long time, and we might update files that were sent in another job (thus preventing those files from being imported). Thanks!

RE: Release notice for TD15.2.1

Naoki Hirai — Sat, 28 Feb 2026 01:23:17 GMT

Hi Andriy Zhidko ,

I read through the blog post and release notices. I realized that many issues have been solved, so I feel it is worth applying the update as soon as possible.

Thanks a lot!!

Best regards,
Naoki

Release notice for TD15.2.1

Naoki Hirai — Thu, 26 Feb 2026 22:29:21 GMT

This is a question regarding the release of Tridion Docs 15.2.1. Version 15.2.1 was released at the beginning of February, and the installer was made available on the FTP site. After downloading the installer and checking its contents, I confirmed that it included a ReadMe.md describing the update procedure. However, I could not find the complete release notes for 15.2.1. Are release notes not provided for update releases?

I would like to know the following points:

The defects that were fixed by the update
Client program compatibility (if the update is applied to the server, is it mandatory to update the client programs as well?)

I would greatly appreciate it if you could publish the release notes for version 15.2.1.

Best regards,

Naoki

RE: Is there a way to cancel translation jobs that use the File Export template in Tridion?

Andriy Zhidko — Fri, 27 Feb 2026 19:07:33 GMT

Hi Eva,

The Tridion Docs 15.2.1 release announcement was published on the community today.
Please see Tridion Docs February Update is Out! (version 15.2.1)

You can find release notes by following the links below:

New and changed in version 15.2.1

Fixed issues in version 15.2.1

RE: Release notice for TD15.2.1

Andriy Zhidko — Fri, 27 Feb 2026 19:03:36 GMT

Hi Naoki Hirai ,

The Tridion Docs 15.2.1 release announcement was published on the community.
Please see Tridion Docs February Update is Out! (version 15.2.1)
Links to release notes are mentioned there.
I will include them here as well:

New and changed in version 15.2.1

Fixed issues in version 15.2.1

Has anyone developed a plugin for Markdown output?

Elizabeth Gschwind — Wed, 25 Feb 2026 19:14:29 GMT

We are investigating outputting our DITA content to (GitHub/GFM-flavored) Markdown format. Has anyone done this already, and do you have any suggestions?

We are on-prem, TDX 15.1.2. DITA-OT 3.5.4.

RE: Is there a way to cancel translation jobs that use the File Export template in Tridion?

Eva Nauerth — Wed, 25 Feb 2026 14:47:28 GMT

Thanks, Nigel! I was checking the product announcement blog and the release info knowledge base, but it wasn't mentioned there, so I thought it was not released yet.

Is there a release note information somewhere? Looking forward to cancelling translation jobs ;) but I would love to know what else will change before diving into upgrading. :)

RE: Is there a way to cancel translation jobs that use the File Export template in Tridion?

Nigel Lock — Wed, 25 Feb 2026 14:44:41 GMT

Hi Eva, the Tridion Docs 15.2.1 release occured a few weeks ago during the first week of February so it is already available through the usual channels. You may contact your RWS account manager or Support for more information on getting access to that for your deployment, thanks!

RE: Is there a way to cancel translation jobs that use the File Export template in Tridion?

Eva Nauerth — Wed, 25 Feb 2026 12:20:17 GMT

Hi Dave, can you give us more info on the release date of 15.2.1? Thanks in advance!

Unrelease a publication output via UI (Organize Space and/or Publication Manager)

Akheil Jain — Mon, 23 Feb 2026 22:49:22 GMT

We have a few post publish plugins that we run when a user marks a publication output as release. Once a publication output is released it can no longer be published. We have had instances where the publish process fails and now we have to version up the publication and release it again. We would like to take advantage of the "unrelease" user privilege, and have been successful unreleasing a publication via API. We are wondering if there is a way anyone has implemented to allow a user with this privilege to trigger the unrelease through Publication Manager or Organize Space. We are on Tridion Docs 15.2 Patch 1, TIA.