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.
Have you ever wondered how new tools placed on the canvas know what fields are being passed to it? Are they psychic or something? Not at all! It's metadata! The metadata fields Name, Type, Size, Source, and Description are all passed from tool to tool before you even run the workflow. When working with the Python SDK, you are in charge of building and passing that information to downstream tools. This blog post will explain what that entails and how to implement it in your Python-driven plugin.
If you google (a verb) "Date Frustration," the 7th article is Date Conversion Frustration - Alteryx Community. As a follow-up to my previous blog post, Marquee Crew's Guide to Dates, I'll provide you with some tools to better handle incoming date fields and help to teach you how to convert strings to dates. Even with tools like the DATETIME macro, this can be challenging. Hopefully, you'll avoid the frustration and skip directly to happily ever after.
Have you ever wanted to be notified if a workflow ran into an issue? Or get push notifications when incoming data quality didn't meet your standards? Check out the Twilio SMS Alert tool, which will send you a text message based on the tool's incoming data.