When implementing Custom Views you can map fields in the view output to an input parameter in the view syntax. This makes it possible for TimeXtender to track lineage through a view. There is currently a shortcoming in this approach: if you are combining two source fields from different tables into one field in the view, you cannot make a mapping for both. The only way to do this is to add a dummy field to the view that you do not actually need which wastes resources and reduces the clarity of the syntax.
It would be nice if view fields can be mapped to at least one source parameter to resolve this.
