All geek questions in one place

SDL Tridion TOM.NET Documentation

The SDL Tridion TOM.NET API has replaced the deprecated TOM (Tridion object model), starting, I suppose, version R5.3.

Besides the issue of stack overflow problems (Exchange), what documentation should I contact when working with the TOM.NET API and learning about it?

So far I have found (login required):

I see these (plus questions on the forum), but I can’t say which is better. What do you use most when working with TOM.NET?

+6
source share
3 answers

Good question, and probably most Tridion developers might wonder when to use them. I would say that both documents have a different purpose and go side by side. The API documentation provides information on methods and usage, SDL Live Content documents provide more information on what to use for your scenario. We get questions like this when we are aboard the new developer, "Which document provides me with the most information."

I look at these simple examples to explain the differences in when to use this documentation.

  • which variables are available in the package (vs). What API method should be used when reading variables from a package?

We send Live Docs for the first and API document for the second

  1. How do I iterate over nested fields (vs), which method do I use to loop through embedded value fields?

We send Live Docs for the first and API document for the second. I see that this question with different variations persists almost every month.

I know I used simple use cases, but sometimes it's easier to keep it simple. Hope this information helps.

+6
source

Also in accordance with this page in the TOM.NET API documentation should only be used in templates and event handlers. For third-party applications, you should use the Core Service API.

+5
source

I use the API documentation, and when I really want to learn more, use Reflector. But this is not very advisable (?).

+4
source

Source: https://habr.com/ru/post/915685/

More articles:


All Articles