This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I'm frustrated by the fact Alteryx has a hard time with aggregating multiple Excel files that are structured the same way. I've used the Batch Macro process and it is too much for such a simple task.
My unfortunate solution at the moment is to add a new weekly file to the workflow and union all the files together, works like a charm but I should not have to do this.
ALTERYX - Why haven't you built a simple solution for this by now? I love your product but sometimes I wonder why you leave out such important features and put it in the hands of the community to solve with convoluted workflows.
I DON'T want to build a batch marco for this simple process because when I end up sharing the workflow I'll have to make sure whoever ends up opening my workflows I have to make sure they have all the right drivers installed on their machine etc... NOT GOOD.
Please give me your feedback....I'm sure I'm not the ONLY one frustrated with this.
@dylanweaver perhaps it's a typo, but in your post you said "structured the same way." In this case, have you tried either a dynamic input tool or a wildcard on your input? If the schemas of the files are identicial then there is no need for a batch macro.
While others are looking at your sample data, I tend to agree that simple is better. I use CReW macros for some tasks that seem difficult. I've posted YouTube videos about dynamic inputs. You might search for MarqueeCrew and Alteryx.
There is a crew macro that addresses your need for opening files too.
Alteryx ACE & Top Community Contributor
Chaos reigns within. Repent, reflect and reboot. Order shall return.
@dylanweaver It's a small distinction, but in this case the file schemas are actually different. If you compare the two files using the "field info" tool, you will notice that the [Directions to Location] field is a different length between the two files:
This is the 2018-10-19 file, where the length is 993.
This is the 2018-11-02 file, where the length is 990.
That's what's throwing off the dynamic input tool. If you were to increase the length of the longest record in the 2018-11-02 file by the length of spaces, you'll see it works.