Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
Cloud Quests
Elevate your workflow skills by solving real-world challenges using the Alteryx Analytics Cloud Platform.
スポイラ
Originally for task 2, I used a join on calendar date and then unioned all outputs. I found that 2024-03-31 was falling out on one side as if it wasn't in my generate rows (it is), and then later found that 2024-04-01 was being counted twice (but I used the updated start file without duplicates). To get around this duplicate confusion, I just used a union and then summarized it taking the longest value for the holiday names (so it would drop the null values). This worked, HOWEVER, If I remove weekends before my union, then I'm off on US holidays by one.
Originally for task 2, I used a join on calendar date and then unioned all outputs. I found that 2024-03-31 was falling out on one side as if it wasn't in my generate rows (it is), and then later found that 2024-04-01 was being counted twice (but I used the updated start file without duplicates). To get around this duplicate confusion, I just used a union and then summarized it taking the longest value for the holiday names (so it would drop the null values). This worked, HOWEVER, If I remove weekends before my union, then I'm off on US holidays by one.
I'm tempted to pull this up in Designer to figure out if it's cloud being funky on me or the data being funky on me - total toss up at this point! I got the answer in the long run, but confused on why some things didn't join as expected whereas others duplicated. Fortunately I came up with a creative workaround with the help of my favorite orange tool. I know I know, I shouldn't play favorites....
