Output Node Runs, but no Hyper File is Created When Custom SQL Used In Flow

Published: 27 Aug 2018
Last Modified Date: 17 Jan 2019


When branching Custom SQL is used in a flow, the output node runs but no Hyper file is created.


  • Tableau Prep


Create two separate nodes - one for each branch - or do not use custom SQL.


When custom SQL is used and then a self-join from one node after an aggregate step on the custom SQL path to another node on the same custom SQL path, this can happen. Tableau Prep can only have one custom SQL query associated with each node, but the branching path is thought of as two separate SQL queries to the same data source connection. Use two distinct starting nodes if you plan to do a self-join.
Did this article resolve the issue?