Hi Michal,

The TranslationJob objects and information are available through the API layer of SDL Tridion Docs.

The following section in our documentation portal: https://docs.sdl.com/806356/201162/sdl-tridion-docs-14-sp3/translationjob-2-5 shows the available functions.

The SOAP interface is using XML structures to communicate the parameters back and forth. Each function is described in the docs portal as well as some hints around working with the API layer (https://docs.sdl.com/806356/242920/sdl-tridion-docs-14-sp3/basic-concepts-when-using-the-web-services-api)

I hope this helps you already with finding what is possible and using it to meet your requirement(s).

Kind Regards,

Raf

Hi Michal,

The TranslationJob objects and information are available through the API layer of SDL Tridion Docs.

The following section in our documentation portal: https://docs.sdl.com/806356/201162/sdl-tridion-docs-14-sp3/translationjob-2-5 shows the available functions.

The SOAP interface is using XML structures to communicate the parameters back and forth. Each function is described in the docs portal as well as some hints around working with the API layer (https://docs.sdl.com/806356/242920/sdl-tridion-docs-14-sp3/basic-concepts-when-using-the-web-services-api)

I hope this helps you already with finding what is possible and using it to meet your requirement(s).

Kind Regards,

Raf

Hi Raf,

Thanks! this is very helpful. Already started to get familiar with soap api.

I have already tested really simple request with soap and it works.

But now when I want to send the "more advanced" requests I receive bad requests responses.

Are there any live examples for translation job requests such as find or create/delete with using the filter or other metadata "sub-queries"?

I think I am doing it wrong most probably or strictly according to documentation with translation job2.5 docs but maybe something is no longer available?

Here is my snippet for a body of the request:

Many many thanks in advance!

Hi Michal,

The psXMLRequestedMetadata property should always (in all API calls that it can be applied) contain an empty list of fields that you would like to retrieve for the object type.
So the ishfield definition needs to point to a field existing on the object that you are querying (on the level that you are refering to).

So given your sample above the structure should read like:

In order to know which name/level combinations are valid for which object types, you can use the ISHRemote powershell library.

Executing the following commands from it will present all of the available fields with their respective levels for the different object types.

1/ New-IshSession -wsBaseUrl "">yourmachineurl/ISHWS" -PSCredentials Get-Credentials

(provide in the prompted login box username and password to connect towards SDL Tridion Docs

2/ Query for the fields defined by the object types using

Get-IshTypeFieldDefintion | out-gridview

(this will build the list and make it available in a filterable and sortable grid. See screenshot below.

I hope this helps,

Raf