Hi All,
I have been using the Content Manger API for a few releases now, recently tried using the Annotation classes, the code doesn't through any errors, and returns the expected results. But the annotations are not visible in Collective Spaces. I can find, them update them and delete them through the API. What am I missing any guidance would be great.
Hi Akheil,
There is logic inside Draft Space and Review Space to promote orphan topics to the top. However, they still have to be tightly linked to a topic-version within this publication-version and language. That is a first thing to check.
As explained on a different thread, https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/44237/collective-space-api-where-can-i-find-details/143671 , the addressing logic is proprietary and could lead to orphans as well.
If I was you, I would start from the working annotation you retrieved and change the ishfield values one-by-one until you get what you are looking for.
Furthermore, I would advise to not use string concatenation (so the plus operator) for building your xml document. You might have issues if your annotation text contains improper xml/xhtml encoded values (think &, <, > and more).
-Dave
PS: crosslinking to another of your posts... community.rws.com/.../143677
Hi Akheil,
There is logic inside Draft Space and Review Space to promote orphan topics to the top. However, they still have to be tightly linked to a topic-version within this publication-version and language. That is a first thing to check.
As explained on a different thread, https://community.rws.com/product-groups/tridion/tridion-docs/f/forum/44237/collective-space-api-where-can-i-find-details/143671 , the addressing logic is proprietary and could lead to orphans as well.
If I was you, I would start from the working annotation you retrieved and change the ishfield values one-by-one until you get what you are looking for.
Furthermore, I would advise to not use string concatenation (so the plus operator) for building your xml document. You might have issues if your annotation text contains improper xml/xhtml encoded values (think &, <, > and more).
-Dave
PS: crosslinking to another of your posts... community.rws.com/.../143677
Translate
