Skip to main content
Tridion

Return to Answer

highlighted code
Source Link
Bart Koopman
Bart Koopman
  • 29.6k
  • 3
  • 40
  • 90

There is no method build into ECL - the Tridion UI doesn't really have anything ECL could build it on top of as far as I know. An Anguilla data extender can't return a result and a warning. It can return a result or an error.

Try to avoid throwing exceptions in IContentLibrary.CreateContextIContentLibrary.CreateContext. Unless you need to determine if the specific user has access to the remote server you should typically not even make any calls to the remote server here - it will slow down the UI when expanding publication nodes.

One workaround that can give some visual indication of an error without opening the error dialog would be to inject a node in the tree giving some visual feedback. So when the user expandexpands the mountpoint node (ECL will call IContentLibraryContext.GetFolderContentIContentLibraryContext.GetFolderContent), she will get a node with an error icon and for example the title "Unable to connect to the server". Any other operation (including calls to GetFolderContentGetFolderContent for any other folder than the mountpoint folder) should throw the standard exception. To avoid someone managing to add this error node as an image somewhere I recommend using a folder item.

There is no method build into ECL - the Tridion UI doesn't really have anything ECL could build it on top of as far as I know. An Anguilla data extender can't return a result and a warning. It can return a result or an error.

Try to avoid throwing exceptions in IContentLibrary.CreateContext. Unless you need to determine if the specific user has access to the remote server you should typically not even make any calls to the remote server here - it will slow down the UI when expanding publication nodes.

One workaround that can give some visual indication of an error without opening the error dialog would be to inject a node in the tree giving some visual feedback. So when the user expand the mountpoint node (ECL will call IContentLibraryContext.GetFolderContent), she will get a node with an error icon and for example the title "Unable to connect to the server". Any other operation (including calls to GetFolderContent for any other folder than the mountpoint folder) should throw the standard exception. To avoid someone managing to add this error node as an image somewhere I recommend using a folder item.

There is no method build into ECL - the Tridion UI doesn't really have anything ECL could build it on top of as far as I know. An Anguilla data extender can't return a result and a warning. It can return a result or an error.

Try to avoid throwing exceptions in IContentLibrary.CreateContext. Unless you need to determine if the specific user has access to the remote server you should typically not even make any calls to the remote server here - it will slow down the UI when expanding publication nodes.

One workaround that can give some visual indication of an error without opening the error dialog would be to inject a node in the tree giving some visual feedback. So when the user expands the mountpoint node (ECL will call IContentLibraryContext.GetFolderContent), she will get a node with an error icon and for example the title "Unable to connect to the server". Any other operation (including calls to GetFolderContent for any other folder than the mountpoint folder) should throw the standard exception. To avoid someone managing to add this error node as an image somewhere I recommend using a folder item.

Source Link
Lars Møllebjerg
Lars Møllebjerg
  • 4.6k
  • 13
  • 24

There is no method build into ECL - the Tridion UI doesn't really have anything ECL could build it on top of as far as I know. An Anguilla data extender can't return a result and a warning. It can return a result or an error.

Try to avoid throwing exceptions in IContentLibrary.CreateContext. Unless you need to determine if the specific user has access to the remote server you should typically not even make any calls to the remote server here - it will slow down the UI when expanding publication nodes.

One workaround that can give some visual indication of an error without opening the error dialog would be to inject a node in the tree giving some visual feedback. So when the user expand the mountpoint node (ECL will call IContentLibraryContext.GetFolderContent), she will get a node with an error icon and for example the title "Unable to connect to the server". Any other operation (including calls to GetFolderContent for any other folder than the mountpoint folder) should throw the standard exception. To avoid someone managing to add this error node as an image somewhere I recommend using a folder item.