Reconnect Enterprise Guide Query Nodes to New Input Data
When using Enterprise Guide we often create very long flows with many intermediate tables.
However, a problem occurs if we are to change the name of one of these intermediate tables.
The new table is no longer linked to the next step in the process flow.
Below is an example process flow which creates intermediate tables in the work library:
It is necessary to rename the output of Query 1 from QRY1_Out to QRY_OutB, this can be done by modifying Query 1 (the query that creates the table).
When Query 1 is rerun the results are output to a new table but this is no longer linked to the next query in the chain so the process flow will no longer work.
Furthermore if Enterprise Guide is restarted the temporary tables will be deleted and no longer available, so Query 2 and all subsequent steps will now fail. To resolve this problem it is possible to modify Query 2 so that it uses the new input table.
To do this, modify the query and right click on the input table that has changed, selecting its properties.
From the properties dialogue select the change option, this allows a new table to be selected in place of the current one.
Selecting the new table (QRY_OutB) and closing the dialogues connects the new table to Query 2 and repairs the overall flow.
This technique can save a lot of rework when one of the first steps in a process requires modification.
When replacing an input table with one that has different columns to the original, any columns that are no longer available will be flagged and must be removed before the query will run. Also if the table being replaced is involved in a join with other tables and one of the joining keys is missing then Enterprise Guide will not allow the substitution.