Skip to main content
Tridion

Return to Question

deleted 4 characters in body
Source Link
Velmurugan ♦
Velmurugan ♦
  • 8.2k
  • 2
  • 15
  • 27

When creating content through the WCF core service that includes references to ecl items there is no automatic conversion to a tcm uri of the stub component like the UI does.

In the release notes of Tridion 9.6 it is mentioned that there is a new EnableExternalItems property which is enabled by default on the REST core service. This allows us to address ecl items with the ecl uri, but it does not appear to be able to create a stub item when it does not exist yet like the UI.

It seems that the only way to create a stub component without using the UI is to address the netTCP ecl service api directly. We cannot make this connection from outside of the CM server due to networking constraints. Is there any other way to create stubs for ecl items?

When creating content through the WCF core service that includes references to ecl items there is no automatic conversion to a tcm uri of the stub component like the UI does.

In the release notes of Tridion 9.6 it is mentioned that there is a new EnableExternalItems property which is enabled by default on the REST core service. This allows us to address ecl items with the ecl uri, but it does not appear to be able to create a stub item when it does not exist yet like the UI.

It seems that the only way to create a stub component without using the UI is to address the netTCP ecl service api directly. We cannot make this connection from outside of the CM server due to networking constraints. Is there any other way to create stubs for ecl items?

When creating content through the WCF core service that includes references to ecl items there is no automatic conversion to a tcm uri of the stub component like the UI does.

In the release notes of Tridion 9.6 it is mentioned that there is a new EnableExternalItems property which is enabled by default on the REST core service. This allows us to address ecl items with the ecl uri, but it does not appear to be able to create a stub item when it does not exist yet like the UI.

It seems that the only way to create a stub component without using the UI is to address the netTCP ecl service api directly. We cannot make this connection from outside of the CM server due to networking constraints. Is there any other way to create stubs for ecl items?

Source Link
Erik Henderiks
Erik Henderiks
  • 13
  • 2

Creating ECL stubs without netTCP ecl api

When creating content through the WCF core service that includes references to ecl items there is no automatic conversion to a tcm uri of the stub component like the UI does.

In the release notes of Tridion 9.6 it is mentioned that there is a new EnableExternalItems property which is enabled by default on the REST core service. This allows us to address ecl items with the ecl uri, but it does not appear to be able to create a stub item when it does not exist yet like the UI.

It seems that the only way to create a stub component without using the UI is to address the netTCP ecl service api directly. We cannot make this connection from outside of the CM server due to networking constraints. Is there any other way to create stubs for ecl items?