Error logging for additional data sources

Hi Lars,

I definitely agree with you here.  There should always be some indication as to what went wrong if something doesn't work as expected.  

Missing this feature as well. It is crucial to actually know why an object failed, even though we have decided to ignore it on the specific execution.

This is the same feature request:

https://support.timextender.com/hc/en-us/community/posts/205686043-Information-of-failed-transfer-of-data-sources-with-relaxed-error-handling?page=1#community_comment_360009416091

Hi Lars

Thanks for submitting your idea. Your continued feedback on our product is very important to us.

As Sten pointed out, you are not the only one with this request. I have passed your input to our R&D department for further evaluation. 

At the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer, and User Portal. With this splitting and evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.

If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in your region. 

Thanks!