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.
Ever wonder what an Alteryx C++ developer's favorite code editor is? Or a Python developer's favorite book? Or how about a front-end developer's favorite testing framework? If you answered yes to any of those questions, or just wonder where this is all going, continue reading!
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.
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.
No one likes to see an error message, but as an Alteryx tool developer, you have the ability to make seeing an error a useful experience that helps guide the user through configuring your tool. This article will show you how to add error messages through the macro back-end or the front-end.
Want to leverage Alteryx capabilities in a web-app? Maybe you want to create your own data connector. Come as we introduce you to all of our developer tools so that you can show US what Alteryx is truly capable of.
YXI files are a new Alteryx file type that provide a mechanism for packaging and installing new tools in Alteryx. This creates a new possibility of creating and publishing tools so that they are easily added to Alteryx installs.