"Everyone using Alteryx Designer will inevitably encounter errors. Error messages give us data, and that data is useful! This session will discuss how to get the most use out of error messages to improve processes and avoid unintended outcomes with defensive design."
In this 20-minute sessions I talk about the functionality of error messages and how they can be a force for good. As users we should be reading errors and using the information they provide. As Designers we should craft messages that help the user and prevent unintended results. This sessions is also packed with some of my favorite tips and tricks on error-ing situations as well.
SESSION INFO
Session Type: ACE
Session ID: 305
Session Title: Error Messages Are Data. Data Is good.
Session Date: 05/20/2021
Session Start Time: 12:35 PDT
Session End Time: 12:55 PDT
SESSION INFO
Session Type: ACE
Session ID: 305EM
Session Title: Error Messages Are Data. Data Is good.
Session Date: 05/21/2021
Session Start Time: 04:35 PDT
Session End Time: 04:55 PDT
SESSION INFO
Session Type: ACE
Session ID: 305AP
Session Title: Error Messages Are Data. Data Is good.
Session Date: 05/20/2021
Session Start Time: 22:35 PDT
Session End Time: 22:55 PDT
There's no way to cover everything about errors in this 20-minute sessions (my first practice of just this material was 35 minutes), so let's keep the conversation going here!
Share the best/worst error messages you've seen in Alteryx below!
Looking forward to this session!
Worst:
Best: any time someone uses the Error Message tool to validate user input before processing in an app!
Is that the worst just because it replaced "Chaos Reigns Within" ?
@kelly_gilbert wrote:Best: any time someone uses the Error Message tool to validate user input before processing in an app!
Definitely! That's in the session!
Worst: When you forget to name your field in the formula tool
Off topic, but this is the worst error message I've received from the Alteryx server. Resetting and rethrowing never sounds like a good thing. There is a defect when trying to write out 0 record flat files on the server.
Two words: "DATA WRAP" . . .
Has anyone else seen that red X screen!?
@terry10 wrote:Has anyone else seen that red X screen!?
Yup.
In these abstract error situations, the best thing to do is try to replicate and send as much information as possible to the support team.
Hi Carlie,
Can you please help me with the recording of the session.
Thanks in advance