My client uses SQLExecutor (FME 2016) to call a procedure inside SQL Server.
This complex procedure sends back 10 tables : A Table, B Table, C Table, ... J Table.
But some tables could have no data.
SQLExecutor outputs only tables (as entities) with data (ok normal behaviour, FME dont create empty entities).
But we dont have an index (the cursor ?) to know which table is outputting.
By example :
- The procedure sends : A Table with data, B Table wih data, C Table to I Table with no data and J Table with data.
- SQLExecutor outputs 3 entitites : A Table, B Table and J Table.
-> But we don't know in FME that first entity maps A Table, second maps B table and third maps J Table.
If SQLExecutor could generate a cursor attribute, it would be fine :
Fist entity : _cursor = 0 (means A Table)
Second entity : _cursor = 1 (means B Table)
Third entity : _cursor = 9 (means J Table)