Alteryx Analytics Cloud Product Ideas

Users onboarded to Trifacta cannot be deleted from the GUI, only using API. In the GUI users can only be disabled but they still count toward the licensed users. Please allow users to be deleted from the GUI.

If a flow is shared between multiple editors and someone make changes in it, there should be a way we can see all the changes made to that flow by different users, like creating a trigger that will notify the users about the changes made in the flow by someone as soon as the recipe changes or if we can extract the information about the flow or the job. I have attached the snippet of data that can be useful to us.

At the moment the only edit history visible to Trifacta users is within each recipe. Some actions are done within flows rather than recipes, e.g. recipe creation/deletion/taking union/etc. Such actions are not covered within the edit history, but for compliance purposes/troubleshooting it is important for users to know when these actions were taken/who by. Please would it be possible to add the functionality to Trifacta to have an edit history on flows as well as within recipes?

As of now the once a user deletes the flow, the flow will not be visible to anyone, except in the database. But the flow is soft deleted in the database. So can enable the option for admins to see all the deleted flows and recover those flows if required, so that in case some one deletes the flow by mistake then admins can retrieve it by recover option. This has to be an option by check box, where they can recover those flows all at once if it is a folder. This option can also be given to folder recovery where they can recover all the flows in the folder.

When output a Trifacta formated date, like a derived year (year(mydate) ) or formatted to mmddyyyy that when it is published to a SQL table that it maintains that format or transformation. Currently putting out a formatted or transformed date is put out to the SQL Table in the input format and all transformation and formatting is lost.

When creating a destination to and SQL table on an SQL server, allow you to set the field length and not use the Trifacta output standard of varchar (1024). This would help keep the maintenance on the table easier.

Hi team,

We would need a page where a user can handle all the email notifications they are receiving from all the flows (success and failure).

Thank you

Hello,

Here what I have when I want to do an http requests in Plan :

Where is the entry for payload, body (like here, I have to specify my client_id..) ?

Edit : my bad, it was a post request and here the recommandation for get
https://www.rfc-editor.org/rfc/rfc2616#section-9.3

Hi Alteryx,

Most of our clients, particularly those from the government and financial sectors, have strict restrictions on cloud-based data storage. While they are open to using cloud products, they are concerned about the possibility of users uploading sensitive data to the cloud.

Given this, could you consider implementing a control that prevents data uploads to the cloud, while still allowing access to cloud-based features where necessary?

Being able to output data to Microsoft Dataverse tables via Alteryx Designer Cloud would be super helpful and a wonderful addition to this great tool. I need to be able to schedule a daily flow to output data to Dataverse tables. While my organization has Alteryx One, we have elected not to enable Cloud Execution for Desktop (for security or maintenance reasons) and we do not have Alteryx Server. So, I need a solution that works from Alteryx Cloud Designer.

When I rename a field in Alteryx - it would be valuable for Alteryx to look at all tools downstream from the select tool and say "Hey - you are using that field - do you want me to clean up the formulas etc".

A field is not just letters in a formula - a field is a logical concept / an object - so it should be relatively easy to inspect everywhere there's a dependance on this object downstream and just clean this up automatically.

This would get rid of all the painful toil of having to reconfigure tools, change formulae, change select tools etc - that can just all go away in a puff of Aidan Magic.

Hey all,

There is already an option to clean up data in the results section - but it's limited to only the cleanups that the Cleanse tool used to do in the on-prem version.

Please could you use an inspection of the field to see what cleanup may be relevant?

For example:

A_B - there's no need to offer to clean up numbers - or perhaps just visually decrease that option

    A_B - here the obvious cleanup is leading spaces

"A_B" - the obvious cleanup here is remove quotes

It seems that we can bring some smarts to this, since Alteryx AIDAN is AI enabled, to eliminate the toil of data cleansing.

When people ask what's so great about designer desktop, one of the simple things I mention is the record count. I think this would be a great addition to designer cloud. As an example, here's a pointless workflow in designer cloud:

Seems ok, but here's the same thing in desktop:

By just looking at the picture, you can see that I messed up my join and my 780 records have ballooned to 608,400. I can also see that I didn't have any unjoined records pretty easily. Designer cloud has this record count information when you click on each tool, but I think they should display the counts on the canvas like desktop.