What happens when?

Second this. It could be in a separate document perhaps, "for advanced users", but more explanation of what is going on under-the-hood would be really helpful for a variety of troubleshooting and development purposes.

This knowledge could have saved me a lot of time debugging a seriously slow lookup. The slow lookup was caused by joining on a field that had a transformation on it essentially creating a join like this:

[snip]
LEFT OUTER JOIN [table] B ON DATEADD(S,[SECONDS],[DATE])<=B.[TODATETIME] AND DATEADD(S,[SECONDS],[DATE])>B.[FROMDATETIME]
[/snip]

Not the best join predicate to be sure and not one I would ever knowingly have created.

I agree. We had a custom transform that was being re-used like your example which at one point generated an nvarchar instead of an int and thus a conversion error.

Radek from TX and I had to dig very deep to find the error as the error message was very cryptic and there was no "visible" nvarchar to int conversion...

Hi Rasmus

Thanks for submitting your ideas. Your continued feedback on our product is very important to us. And so is your engagement in our community.

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 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!