I have hundreds of routines that extract data from a database and use dynamic input to extract data from another database input.These routines are designed as dynamic input so the user only needs to make one change in the incoming text file for dates and other criteria. Suddenly most of my routines will not run properly due the the following error: "has a different schema than the 1st file in the set". Never had this problem before on any of the routines. Now I have to change the dynamic input and make changes to each input dataset extracting thousands of more records because they are not being filtered from the beginning. What has changed in Alteryx to suddenly get these errors where they never showed up before?
Did the user input differ? For example, when you key in the dates, are they standard (DD-MM-YYYY suddenly becomes DD/MM/YYYY).
In addition, sometimes the data types can change compared to your first reference file used in your Dynamic Input tool, thereby causing the differences.
Null() and Empty() values in extra rows / columns may also lead to that effect causing data type changes (Int to String for example), or just have the data schema thrown out of whack.
One way I would recommend is to create a Batch Macro to account for this. I know the Dynamic Input tool does the trick, but if you want to fully cover it, Batch Macro covers your bases.
Hope this helps.
Cal
Hi @Kardasz
There are two ways to tackle your issue:
Otherwise it will be a goose chase.
Arnaldo