Alteryx Designer Desktop Ideas

We have lots of tools that create new column(s) from the Inputs, e.g., Generate Rows. It'd be very nice if the new column(s) is/are highlighted in the Output. This makes it a lot easier for users when developing the workflow.

Good morning!

This may be a very simple thing, but would it be possible to add a DateTimeQuarter() function? We have DateTime Second, Minute, Day, Month, and Year, and being able to have an easy formula for the quarter as well would be incredibly convenient. 

Thanks,

Kat

Hello all,

Apache Doris ( https://doris.apache.org/ ) is a modern datawarehouse with a lot of ambitions. It's probably the next big thing.

You can read the full doc here https://doris.apache.org/docs/get-starting/what-is-apache-doris but to sum it up, it aims to be THE reference solution for OLAP by claiming even better performance than Clickhouse, DuckDB or MonetDB. Even benchmarks from the Clickhouse team seem to agree.

Best regards,

Simon

I think it would be great to have a tool that allows you to update a dataset with another dataset. For example, this could be used in updating an archive table on a daily basis as data changes. Having a tool available that streamlines this data operation would be helpful to simplify workflows.

In the tool, you would be given the option to select your primary key fields, which are the fields used to identify records. Additionally, you have the option to perform an insert, modify, or delete operation, according to the primary key fields that you choose in the configuration.

Obviously this is something that anybody could create a macro for if they wanted to. But it would be nice to have a tool in place so that we dont have to worry about it. I think this would be a nice use case to bolster Alteryx usage as a data engineering tool for relational database management in particular.

When a workflow runs on the server and the server tells me there was an error with Tool ID 103, I'd like to be able to open that workflow in my designer and search for that Tool ID 103.  We have some really large workflows and it takes a long time to manually locate that tool.

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

It would be great if you could include a new Parse tool to process Business Glossary concepts formatted using the SKOS (W3C) standard in the next version of Alteryx.

SKOS is a widely used standard for the representation of concept and term relationships. It provides a consistent way to define and organize concepts (including versioning), which is essential for the interoperability of these data.

We believe that supporting SKOS 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.

SKOS, which stands for Simple Knowledge Organization System, is a W3C Recommendation for representing controlled vocabularies in RDF. It provides a set of classes and properties for describing concepts, their relationships, and their labels. This allows KOS to be shared and exchanged more easily, and it also makes it possible to use KOS data in Semantic Web applications.

SKOS 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 SKOS:

• Improved discoverability: SKOS makes it easier to discover and use KOS, as they provide a standard way of describing their attributes.
• Increased interoperability: SKOS allows KOS to be integrated with other Semantic Web applications, making it possible to create more powerful and interoperable applications.
• Enhanced semantic richness: SKOS 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 SKOS and DCAT are being used:

• The Library of Congress uses SKOS to describe its controlled vocabularies.
• The Dutch Government made it a mandatory standard for all Dutch Government Agencies.

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

SKOS

• Reference Page: https://www.w3.org/TR/skos-reference/
• Dutch (NL) Standard: https://forumstandaardisatie.nl/open-standaarden/skos
• WIKI Pedia on SKOS: https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System
• Video: https://youtu.be/pbTRDDQ43Sw?si=RG3f-jPBsx2OK8IQ
• Tools: https://csiro-enviro-informatics.github.io/info-engineering/semantic-tools.html

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

Sometimes, Control Containers produce error messages even if they are deactivated by feeding an empty table into their input connection.

(Note that this is a made up example of something which can happen if input tables might be from different sources and have different columns so that they need separated treatment.)

According to the product team, this is expected behaviour since a selection does not allow zero columns selected. This might be true (which I doubt a bit), but it is at least counter-intuitive. If this behaviour cannot be avoided in total, I have a proposal which would improve the user experience without changing the entire workflow validation logic.

(The support engineer understands the point and has raised a defect.)

Instead of writing messages inside Control Containers directly to the log output (on screen, in logfile) and to mark the workflow as erroneous, I propose to introduce a message (message, warning, error) stack for tools inside Control Containers:

1. When the configuration validation is executed:
1. Messages (messages, warnings, errors) produced outside of Control Containers are output to the screen log and to the log files (as today).
2. Messages (messages, warning, errors) produced inside of Control Containers are not yet output but stored in a message stack.
2. At the moment when it is decided whether a Control container is activated or deactivated:
1. If Control Container activated: Write the previously stored message stack for this Control Container to the screen and to the log output, and increase error and warning counts accordingly.
2. If Control Container deactivated: Delete the message stack for this Control Container (w/o reporting anything to the log and w/o increasing error and warning count).

This would result in a different sequence of messages than today (because everything inside activated Control Containers would be reported later than today). Since there’s no logical order of messages anyways, this would not matter. And it would avoid the apparently illogical case that deactivated Control Containers produce errors.

We currently have language support for a few major languages. I know Chinese is available, but the writing system is only Simplified at this moment. 

I was recently in conversation with a few people from Taiwan, and they are using the Traditional writing system of Chinese. 

If Alteryx can provide Traditional as an additional to their already available Simplified writing system, I think Alteryx can help capture the market in Taiwan better. 

The people I spoke with never heard of Alteryx before, and after a demo - they were impressed. If it has this language support, then I think it’ll be much easier to get more sign ups for Alteryx from the Taiwanese market. 

Currently when debug mode is entered in analytic apps and macros, the direct inputs to the app/macro when the error occurred are hardcoded into a workflow in debug mode, so that errors can be more easily detected.

However, inputs into analytic apps also create global variables which can be used in the more code-heavy aspects of Alteryx such as the Formula Tool. These are not updated in the same way which can cause workflows to break in debug mode - it would be really helpful if global variables could be updated in the same way as the inputs into tools are.

There should be a quick way to delete all unwanted tools for specific output/browse tool in workflow. This would be useful when we have huge multiple cross connect workflow. By deleting all not requited tools, it would make it easy and faster to test as segregated.

Everyone knows the importance of adding the appropriate controls and governance to your workflows - and often, this means including events that will generate notifications if a workflow is running with errors.

But who is the audience of that email? If it's not a developer, will that person know what they are reading and where to focus?

How about a developer that would like to customize the message that the end user will receive?

Porting some existing functionality from other tools in the Alteryx toolkit to the Events page could easily provide added flexibility to event generation:

1) Add a formatting bar to the tool like shown in the image below

-- Style changes

-- Alignment

-- Highlighting

-- Coloring

-- Images

2) Add a function bar to the tool like shown in the image below

-- Ability to view all available variables

-- Ability to apply formulas using variables

-- Ability to save formulas

What do you think? Give this post a thumbs up if you find the post helpful!

It would be great if we could add example workflows to our macros, accessible in the same way as from the original tools (example hyperlink shown after single-clicking on a tool in the tool palette or when searching in the search bar).

There is a post on how to do it for custom tools How to add an example link in the custom tool (alteryx.com). The way described there has limitations and does not seem to work on macros: I was able to get the link to show up, but nothing happens when I click.

My suggestion, make it easy to add an example workflow to a macro, like it is to change the logo or add a help link.

Hello all,


As of today, we use the good old alias in-memory to connect to our datasources in in-memory. We have several environments so we use constants in order to change the name of the in-memory alias during execution.

To illustrate :

Depending of the environment, the constant « v_gp_contexte » will take different values :

• GP_DS08_SIDATA for la dev.
• GP_EE_SIDATA for prod.

Sounds nice, right? But now, we would like to use DCM and the nightmare begins :

We can't manually change the name and set the question :

if we look at the xml of the workflow, we only find an id so editing it is useless :

(for informationDCM connections are stored in some sqlite db in C:\Users\{yourname}\AppData\Local\Alteryx

So, I would like to use the DCM inside the in-memory alias (the in-memory alias is stored and can be edited), just like for in-db connection alias.

Best regards,

Simon

The ability to output to Amazon Workdocs via a special Output tool would be very helpful for anyone looking into using Workdocs for personal or professional purposes.  This is similar in functionality to the OneDrive connector.

This is a question which is somehow in between Designer and Gallery ideas.

When saving a workflow to the Gallery, the user can select the Assets (elements which are also copied to the Gallery). The point in time during the save process is a bit questionable from my perspective.

Often, I develop workflows locally until they reach a state in which I want to move them to the Gallery so that they can be included in Schedules or be made available to other users. I would like to be able to select which macros or datafiles are copied to the Gallery as well much earlier in the development process. From my perspective, it would be great if the user could set the Assets settings in the "Workflow Dependencies" window as well. I propose 3 possible values for each element (macro or data file):

• "Auto" → decide on asset when saving the workflow to the Gallery (current behaviour)
• "Yes" → Copy this element as asset in the Gallery
• "No" → Do not copy this element to the Gallery 
• "N/A" → The question does not apply to this row (e.g., directory)

It could look like this:

So our company is relatively new to Alteryx Designer and Server and we recently found out that there's no official communication sent out from Alteryx on when there are patch releases for Designer and Server. We've encountered so many bugs that we later found on the release notes that would've been helpful to know about months before.

So my suggestion is to have an option for Administrators to opt in/out for communication emails on when the patches are released.

Thank you!

Hi - Please delete this if it perhaps exists already in a newer version.  (I am on 2022.1 and don't see this functionality.) 

I would love to see the ability to right click a tool that isn't in a container and be able to add it to an existing container.  Currently I drag it over and drop it into the container then move it back to where it was.  Inevitably I misalign the tools and spend time getting it linear again. It would be cool if based upon the choice made in the right click, it would bring the assigned container around the tool in its existing location.

OR

Perhaps within the config of the container you could choose tool #s to add to the container?

Anyways this isn't a huge need but it would be nice to see that additional functionality for people that spend a disproportionate amount of time aligning and distributing their tools HORIZONTALLY.  (Nobody cares about the people that do vertical workflows.)

Our company has a need to link a new data source in Athena.  We have been able to establish a connection using the input functionality however the connection is so slow it is unusable.  We need to have Alteryx build an In Database option for Athena to allow us to link our data lake to Alteryx.