1

For SDL Tridion Docs 13 SP2, is the taxonomy connector compatible with older versions than Sites 9 (i.e SDL Web 8.5, SDL Web 8.1, etc.)?

As far as I can tell, there is no mention of version compatibility, although it says say "SDL Tridion Sites," which may imply Sites 9. I did a quick test with Web 8.5 and it seems to be working (although my test was not all that thorough - I just made sure I could get basic keywords from Sites displayed in the Docs properties metadata fields). I need to know if this is going to work with Web 8.1 and if it has any known issues or other quirks.

Improve this question
1
  • I just ran another test with Web 8.1 and it seems there is an incompatibility caused by Web 8.1 only having CoreService201501.svc, but the Taxonomy Connector expecting a CoreService201603.svc endpoint. Is there any workaround for this?
    – Damian Jewett
    Commented Jun 12, 2019 at 2:25

1 Answer 1

Reset to default
2

The Taxonomy Connector is part of the Tridion DX suite, which is a combination of Tridion Sites and Docs.

Tridion Sites 9.0 in combination with Docs 13 SP2 (and UDP/DXD 11.0) forms the first version of this Tridion DX suite.

Can you elaborate on your use case for the Taxonomy Connector for SDL Web 8?

Improve this answer
3
  • We have a client that is using Web 8.1 and Docs 13 SP2. They to manage taxonomies in their Web 8.1 instance that can be connected into their Docs 13 SP2 instance. The only solution I can think of is to re-implement the taxonomy connector to work with the available core service in Web 8.1, which is a shame, since we don't have access to any code for the taxonomy connector...
    – Damian Jewett
    Commented Jun 13, 2019 at 0:33
  • I can think of another solution: convince the client to upgrade to Sites 9. :-). The use case is still not clear to me, but it seems like your client wants to do some kind of “content mashup” (combining content from Tridion Sites and Docs). We developed the Tridion DX suite for that purpose.
    – Rick Pannekoek
    Commented Jun 13, 2019 at 5:57
  • Does your client realize that Web 8.1 is EOL, so further investment in it may not be the smartest thing to do?
    – Rick Pannekoek
    Commented Jun 13, 2019 at 6:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.