"Take File/Table Name from Field" is checked. When the macro runs as part of a workflow, the SQL statement will be changed to "Select * from dbo.User", if you pass in "dbo.User" as the table name, and the SQL will execute correctly. There is no table called "_TableName_" in my DB. The invalid SQL string "Select * from _TableName_" is the reason the Dynamic Input tool displays an error in the Macro.
It's also set up to pass the tablename field to use in the Output tool. It replaces the "_TableName_" with the value that was set by the control parameter in the previous step. You'll need this because the Dynamic Input does some modifications to this string Leave the Query the way it is, "Select * from _TableName_". You'll need to change the connection to connect to your actual DB. The Dynamic Input tool is configured like this This particular macro uses the control parameter to replace the tablename that's in the Text Input tool. The batch macro will run once for every record that's passed in to the control parameter, but the runs will be completely independent. To get around this, you'll need to use a batch macro. This is because Alteryx will read data from multiple tables in a standard workflow, but as soon the schema differs from the 1st table, the input tool will skip the table.
As to in his post, if the schema of the tables are different, which is the case in every SQL data database, you can't use a standard workflow to extract the data. Hi a workflow that will connect to any SQL database, extract the data from a list of tables and write the results to separate sheets in an excel workbook.
0 kommentar(er)
