Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #39: Trouble Shooting a Broken Macro

josh_brandt
6 - Meteoroid

Fixed - took me a few minutes to track down the different issues.

tcroberts
12 - Quasar

Here's my solution:

 

Spoiler
Spoiler
WC39FixedMacro.PNG

Really liked this style of challenge, and the opportunity to practice a different type of example. Debugging others and your own workflows is an integral part of mastering these tools

danilang
19 - Altair
19 - Altair


Good Challenge.  Even after you fix the connection and field name problems to get the Macro to run, there are still logic errors in the calculations around the time span to look back at! @mmongeon I found an problem with the macro that no-one else did.  Not even the official solution.  Can you find it!

Spoiler
Solution 39.png

 

Dan

CaraI
Alteryx
Alteryx

This was great practice working through error messages.

 

Spoiler
Workflow 39 Macro.jpg
OldDogNewTricks
10 - Fireball

All fixed up...

danrh
13 - Pulsar
 
kat
12 - Quasar
Spoiler
Challenge #39 macro.PNG
kelly_gilbert
13 - Pulsar
Spoiler
* Connected Action tool #10 to the Text Input Tool #9
* Changed date format in DateTime Parse tools #15 and 16 to "Month dd, yyyy"
* Turned off too-many-records warning in Append Fields tool #11
* Changed Filter tool #7 to from -6 years to -2 years and added underscores to field names
* Formula tool #5: added underscore to Close_Date and added end bracket

 

 

 

Inactive User
Not applicable
 
Kenda
16 - Nebula
16 - Nebula
Spoiler
39.PNG