Is it possible to use self-joined tables as a source?

[modelpoint]

Looks like there is a bug in a current version (1.1). When creating a transformation with only one table selected as a source, UI does not ask how many times table should be used in transformation and how instances of these tables are related, instead it goes directly to the mapping screen. That effectivelly prohibits the use of self-joined tables in transformation.

[Torgil Zethson]

I think this was actually possible in version 1.0. We removed this functionality in 1.1 because we could not think of a case where it would be useful, and we wanted to reduce the number of steps in the transformation wizard. Thanks for bringing this to our attention - I think it will be easy for us to revert back to the original behavior in time for the 1.2 release.

Cheers,
- Torgil

[modelpoint]

Thank you Torgil. Also for future versions, could you consider adding SQL queries (and may be stored procedures) as source of transformation data? Oftentimes web service request transformation only requires a couple of values from the database and it's just not practical to create and maintain a view for every case like this.

[Ilan]

For stored procedures, users have been using the DBLookup function to call stored procedures passing data into the sp's from the source database.

Also, if you need to test something in the short term, if you create a dummy table with only one record and include that in the source then you'll be able to test using your table multiple times and make sure that Jitterbit can do what you need before this feature is re-introduced.

Thanks.
Ilan.

[Torgil Zethson]

Thanks for bringing this to our attention - I think it will be easy for us to revert back to the original behavior in time for the 1.2 release.

The first beta version of 1.2, with this fix included, is now available here:

http://sourceforge.net/project/showfile ... _id=458975