Alteryx Designer Desktop Ideas

It would be oh so nice to be able to copy a container's properties and paste those formatting options onto other containers.  It could be accomplished through a Paint Brush icon on CTRL-Copy and Right Click to paste format.  either way it would save setting the Color (multi-step select), Margin, transparency.

Cheers,

Mark

Hi,

Would be helpful to have an Input and Output Tool for ProjectOnline like the SharePoint and OneDrive Tools.

This way we can read the projects in a tabular form and automate our project management tasks.

Thank you.

When you start using DCM - you may have existing canvasses which use regular old connection strings which you want to migrate to DCM.

Currently (in 2023.1.1.123) - when you select "Use Data Connection Manager" - it shreds the configuration of your input tool which makes it difficult to just convert these from an existing connection to a DCM connection

The only way to then make sure that you don't lose any configuration on the tool then is to use the XML editing functionality of the tools and copy across your old configuration.

Could you please add the capability to keep my current tool configuration, but just change from using a regular old connection string to using DCM?

Many thanks 

Sean

cc: @wesley-siu @_PavelP 

After multiple years of using Alteryx, The tabbed document feature was left out of 2022.1.  This feature allows for a much cleaner canvas for exploring workflow and output data.  I view this feature as a basic function of Alteryx, I was surprised to find out that the development team intentionally omitted this function.   I really don't want to revert back to older versions but it may be only the way to have a more comfortable feel of Alteryx.

I would love a tool to be created for looking up a value in a table based on a condition. It could be called "Lookup." One input to the tool would be the lookup list, the other is the main database. Inside the tool you could enter functions that can query the lookup table and return the results either as an overwrite of an existing field in the main DB or as a new field in the main DB, similar to the options in the Multi-Row Formula tool.

Here is a link to my post in Community that explains the problem. The solution, in a nutshell, was to create a Join (which resulted in millions of additional rows), run the conditional formula, then filter to get rid of the millions of rows that were created by the Join so only those that met the condition remained (the original database rows).

Here is the text of my Community post describing my project (slightly modified for clarity):

Table 1:  A list of Pay Dates (the lookup table)

Table 2:  Daily timekeeper data with Week Start and Week End Date fields.

The goal:  To find the Pay Date in Table 1 that is greater than the Week Start Date in Table 2 and no more than 13 days after the Week End Date in Table 2.

[Table 2: Week Start Date] < [Table 1: Pay Date]

and [Table 2: Week End Date] < [Table 1: Pay Date]

and DateTimeDiff([Table 1: Pay Date], [Table 2: Week End Date], 'Days') <= 13

There are many different flows I could use this type of tool for that would save time and simplify the flow.

Thanks!

It would be great if you could include a new Parse tool to process Data Sets description (Meta data) formatted using the DCAT (W3C) standard in the next version of Alteryx.

DCAT is a standard for the description of data sets. It provides a comprehensive set of metadata that can be used to describe the content, structure, and lineage of a data set.

We believe that supporting DCAT in Alteryx would be a valuable addition to the product. It would allow us to:

• Improve the interoperability of our data sets with other systems (M2M)
• Make it easier to share and reuse our data sets
• Provide a more consistent way to describe our data sets
• Bring down the costs of describing and developing interfaces with other Government Entities
• Work on some parts of making our data Findable – Accessible – Interopable - Reusable (FAIR)

We understand that implementing support for this standards requires some development effort (eventually done in stages, building from a minimal viable support to a full-blown support). However, we believe that the benefits to the Alteryx Community worldwide and Alteryx as a top-quality data preparation tool outweigh the cost.

I also expect the effort to be manageable (perhaps a macro will do as a start) when you see the standard RDF syntax being used, which is similar to JSON.

DCAT, which stands for Data Catalog Vocabulary, is a W3C Recommendation for describing data catalogs in RDF. It provides a set of classes and properties for describing datasets, their distributions, and their relationships to other datasets and data catalogs. This allows data catalogs to be discovered and searched more easily, and it also makes it possible to integrate data catalogs with other Semantic Web applications. 

DCAT is designed to be flexible and extensible, so they can be used to describe a wide variety. They are both also designed to be interoperable, so they can be used together to create rich and interconnected descriptions of data and knowledge.

Here are some of the benefits of using DCAT:

• Improved discoverability: DCAT makes it easier to discover and use KOS, as they provide a standard way of describing their attributes.
• Increased interoperability: DCAT allows KOS to be integrated with other Semantic Web applications, making it possible to create more powerful and interoperable applications.
• Enhanced semantic richness: DCAT provides a way to add semantic richness to KOS , making it possible to describe them in a more detailed and nuanced way.

Here are some examples of how DCAT is being used:

• The DataCite metadata standard uses DCAT to describe data catalogs.
• The European Data Portal uses DCAT to discover and search for data sets.
• The Dutch Government made it a mandatory standard for all Dutch Government Agencies.

As the Semantic Web continues to grow, DCAT is likely to become even more widely used.

DCAT

• Reference Page: https://www.w3.org/TR/vocab-dcat/
• Dutch (NL) Standard: https://forumstandaardisatie.nl/open-standaarden/dcat-ap-donl
• WIKI Pedia on DCAT: https://en.wikipedia.org/wiki/Data_Catalog_Vocabulary

RDF

• Reference Page: https://www.w3.org/TR/REC-rdf-syntax/
• Dutch (NL) Standard: https://forumstandaardisatie.nl/open-standaarden/rdf
• WIKI Pedia on DCAT: https://en.wikipedia.org/wiki/Resource_Description_Framework

Would love to have the ability to connect S3 to alteryx using the AWS IAM role instead of needing an AWS access key/secret key.

IT will not hand out the Access/secret key so it would be great to connect to S3 without needing a password.

Apologies if this has been suggested or exists. I often find myself using manual Excel files as a data source. These files frequently use cell formatting elements, such as cell color and text color, to convey important information. However, when these files are imported into Alteryx, this valuable formatting information is unfortunately lost.

To address this, a dedicated input tool that can read Excel files with separate fields for these formatting elements would be very helpful. This would be incredibly beneficial, especially when the data lacks other fields that relate to the coloring. Currently, I manage to achieve this using a Python tool, but integrating this as a built-in feature in Alteryx would undoubtedly be more efficient and user-friendly. This enhancement would not only simplify data preparation but also ensure the preservation of the full context of the original Excel file.

Alteryx offers the ability to add new formulae (e.g. the Abacus addin) and new tools (e.g. the marketplace; custom macros etc) - which is a very valuable and valued way to extend the capability of the platform.

However - if you add a new function or tool that has the same name as an existing function / tool - this can lead to a confusing user experience (a namespace conflict)

Would it be possible to add capability to Alteryx to help work around this - two potential vectors are listed below:

- Check for name conflicts when loading tools or when loading Alteryx - and warn the user.   e.g. "The Coalesce function in package CORE Alteryx conflicts with the same function name in XXX package - this may cause mysterious behaviours"

- Potentially allow prefixes to address a function if there are same names - e.g. CoreAlteryx.Coalesce or Abacus.Coalesce - and if there is a function used in a function tool in a way that is ambiguous (e.g. "Coalesce") then give the user a simple dialog that allows them to pick which one they meant, and then Alteryx can self-cleanup.

cc: @JarrodT  @NicoleJ 

Hi there,

When connecting to data sources using DCM - could we please add the ability to make JDBC connections?

see:

https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Add-the-ability-to-connect-to-data-s...

https://community.alteryx.com/t5/Engine-Works/JDBC-Connections-in-Alteryx/ba-p/968782

As mentioned in these threads - JDBC is very common in large enterprises - and in many cases is better supported by the technology teams / developer community and so is much easier to make a connection.    Added to this - there are many databases (e.g. DB2) where JDBC connections are just much easier 

Please could you add JDBC connections to the DCM tooling?

Thank you

Sean

cc: @wesley-siu @_PavelP 

A "Filter" that would work like a "Formula" - where you can add multiple criteria in one space, and for each criteria, you would get an output anchor.  I use Alteryx to manage master data from several factories - each needing to have separate workstreams.  Stacking Filter criteria functions, but it would be much cleaner to have it managed within a single tool.

There needs to be a way to step into macro a which is component of parent workflow for debugging.

Currently the only way to achieve to debug these is to capture the inputs to the macro from the parent workflow, and then run the amend inputs on the macro. For iterative / batch macros, there is no option to debug at all. This can be tedious, especially if there are a number of inputs, large amounts of data, or you are have nested macros.

There should be an option on the tool representing the macro in the parent workflow to trigger a Debug when running the workflow, this would result in the same behavior when choosing 'Debug' from the interface panel in the macro itself: a new 'debug' workflow is created with the inputs received from the parent workflow.

On iterative / batch macros, which iteration / control parameter value the debug will be triggered on should be required. So if a macro returns an error on the 3 iteration, then the user ticks 'Debug' and Iteration = 3. If it doesn't reach the 3rd iteration, then no debug workflow is created.

Under the Runtime setting, there is an existing option to "Disable All Tools that Write Output". This is incredibly useful when developing workflows when you don't want to overwrite existing files.

But this option doesn't disable all outputs, like Publishing to Tableau! 

I suggest adding the option to disable ALL kinds of outputs, uploads, and publishing (except possibly logging and caching).

In short:
Add an option to cache the metadata for a particular tool so that it doesn't forget when using tool that have dynamic metadata such as batch macros or alteryx metadata engine can't resolve such as python tool.

Longer explanation:

The Problem:

One of the issues I often encounter when making dynamic workflows or ones that require calling external services is that Alteryx often forgets the metadata of what columns to expect. This causes the workflow to forget configuration of downstream tools when a workflow is first opened or when the metadata engine refreshes. There is currently the option to disable the metadata engine from automatically refreshing but this isn't a good option because you miss out on much of the value it brings.

Some of the common tools where I encounter this issue:

• Json parse
• Batch macros
• Python tool
• Regex parsing to rows

Solution:

Instead could we add an option to cache the metadata for a particular tool, this would save the metadata from the last time the workflow ran to within the workflows XML so that it persists when closed and reopened. Then when the metadata engine runs when it gets to this tool instead of resolving the metadata from the tool it instead uses the saved version in the XML. Obviously when it actually runs it would ignore this and any errors would still occur.

This could be an option in navigation pane of each tool. Mockup below:

This would make developing dynamic workflows far easier and resolve issues of configuration being lost when the metadata changes and alteryx forgets the options.

Taking inspiration how you work with Jupyter notebooks and use the notebook to show your workings,  wouldn't it be great if you could document your workflows directly on the canvas more in a notebook style.

I think this essentially can be summarised down into two features:

1) Markdown functionality in the comment tool

2) Ability to import results from IRG and  / or browse tool directly into the canvas.

I have mocked up a version of what this could look like in the screenshot below.

Overall I think it would improve the experience of documenting workflows as you can show your workings in-line while building the workflow. Plus it solves the debate around team vertical vs team horizontal as you build using both! 

Hi all,

I think it would be great if Alteryx could send calendar invites in Outlook (and perhaps other calendaring systems) like it sends emails.

Currently the only way to accomplish this is to send it as an attached ICS file on a regular email.  

In my use case, rather than auto-populating a Shared Mailbox/calendar, someone has to go into the inbox, the email has to be opened then the ICS has to be clicked on to interact with.  

There are ways in Outlook to send an item like this but have it appear automatically without the end user ever seeing the actual invite.  (Our Company adds holidays and other important dates in this manner)

So basically I want this functionality available in Alteryx to do the same.  I have posted about it before in the discussions threads, but basically right now we enter our time in HR system, then have to manually enter the same info on our personal calendar in Outlook and any team calendar whether it be a SharePoint calendar, a group calendar in Outlook etc.

If Alteryx had the ability to send these types of invites, employees could enter the info in our HR system then Alteryx can get the data feed and automatically populate the other calendar (whichever type it may be).

Hopefully this gets some likes.  

Multi-Fill Tool

Please consider a new Multi-Fill tool, not for Apps, but for regular workflows, manually run or scheduled.

Similar to the Interface tool-combination of the Text Box & Action (Update value) tools, this Multi-Fill tool would enable the user to update, for example, the User Name and Password in one place for multiple Download tools. It could also be used to update other tool variables like Filter, Sort, Unique, etc.

Can we have a User Setting that allows the users to select if Alteryx should prevent the computer to go into Sleep or Hibernate mode when running a workflow?