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.
At the moment, I have a lovely formatted XLS with corporate branding, logos, filled cells, borders etc. The data from the Alteryx output needs to start in cell B6. I have tried the output tools to this named range, but Alteryx destroys all the Excel formatted cells in the data block.
As a workaround on the forums, many Alteryx users pump out to a hidden "Output" tab, and then code =OutputA1 in the formatted sheet. This looks messy to the users who then go hunting for the hidden tab. Personally I end up pumping the workflow out to a temporary CSV file. Then opening that in Excel, selecting all, and then pasting values in the pretty Excel file.
This is fine for one file, but I need to split the output report block by a country field and do this 100s of time for each month end.
Please can we have a output tool that does the same as my workaround. Outputs directly from a workflow to a range in Excel that doesnt destroy the workbook's formatting.
In a browse tool, sometimes I need to check any metrics haven’t been lost or omitted in different summarise tools (eg the totals still add up with different group by).
I would LOVE the quick win of selecting some cells in the browse tool results pane, and a label somewhere shows me the sum, average, count, distinct count, etc. I hate to use the line but ... “a bit like Excel does”. They even alow a user to choose what metrics they want to show in the label by right clicking. :-)
This improvement would save me having to export to Excel, check they add up just by selecting, and jumping back, or even worse getting my calculator out and punching the numbers in.
Now that we have a Snowflake Bulk Loader option, it would be great to utilize the built-in Snowflake internal staging. This eliminates the need for an end-user to have the technical know-how or access to IT resources to utilize a separate S3 bucket and generally reduces friction in the process.
We now have the ability to output to an ESRI File Geodatabase, which is great, but it only allows you to output it to the WGS84 coordinate system. I would like to have the same functionality to export it to other projections or coordinate systems similar to the ESRI Shapefile or ESRI Personal Geodatabase output tools (we specifically need NAD83 but I'm sure others would like other options as well).
I know others have talked about it here and here and here other places. And everyone suggests the dynamic rename tool and it's drawbacks.
Our users regularly need to write data to various places on a worksheet and we end up authoring VBA to delete the header rows often. It would make a huge difference to our users if there was a checkbox to exclude column headers when writing out.
I feel like I must be missing something, but saw a similar suggestion for TDE outputs, so maybe this really doesn't currently exist. We sometimes add descriptions to fields we create, and some inputs come with descriptions, but we can't seem to get them into the final database using the Output tool. Can there be a checkbox to persist the metadata along with the data when writing to a database?
When saving an output that has high audit ability requirements I want to save the workflow version as part of the file (along with the workflow name which I can already get). Should there be any questions even years later regarding how a particular output was obtained, it would be easy to answer with confidence by referencing the specific workflow version used to produce it.
Today I have some workflows which have certain steps that occur after files are output. I have these set up inside of Tool Containers so that I can easily enable/disable them as I am working if I do not want to produce output for this particular run. However, sometimes if I need to troubleshoot on a workflow that I haven't worked on for awhile, I can neglect to disable these, which can cause errors. This is usually harmless, but annoying.
Having two more options on Tool Containers could really help to improve this!
Disable When Browse Tools Disabled would be useful for any analysis/debugging steps that I only want to run when I am browsing to find data, but should not run otherwise.
Disable When Output Disabled would be really useful to ensure that these tools are turned off alongside the "Disable all tools that write output" option in Workflow-Configuration-Runtime.
This would save me a lot of unnecessary error messages and moments of panic, and would make these types of workflows easier for other users to debug without extensive notes.
When selecting an Action in the Summary Tool - like Count. The Output filed Name becomes Count. It s/b Filed Name_Count so I don't have to rename all the Output Field Names with a more descriptive name.
Is anyone else annoyed that the default Output Options for the output tool usually need to be changed? What I've found in my couple of years of using this (wonderful) tool is that for Excel and Tableau outputs especially, the default is always 'Create new [sheet OR Extract File]'.
But when you use that option for your output tool, you can't use the Alteryx flow again; you get an error (Sheet already exists you moron, or Extract already exists stupid) (c'mon, you know Alteryx is judging you and the strikethroughs are there in spirit).
The 'stupid' is silent
If you ever want to run your workflow again, you've got to change it to 'Overwrite [Sheet (Drop) OR Existing Extract File (Create if does no Exist)]'.
I'm not sure about you, but I've been (passive aggressively?) hoping that with each new release of Alteryx, I would get a means to change my defaults. I would LOVE the option to have my output tools default to the overwrite, ratherthan create, option automatically. That one step is just... annoying to do over and over again.
So, I'm not going to be a passive-aggressive twit any longer. I am formally asking for what I want like an adult.
Can I please have an option in Options>User Settings>Defaults with a drop-down for Output tool preferences: Create by default, Overwrite by default, Append by default, and whatever the other options are generally categorised according to how the Output tools are done? I really only care about the overwrite one, but you're getting my gist at this point, right?
As a MicroStrategy customer it would be nice if Alteryx would support output for either the .mstr file format or better direct creation and publication of the iCUBE, intelligent cube format on their server solution. This would be similar to the existing features of writing a twbx or TDE file extract and publish to Tableau server.
Opposite if the Input connector could read from an intelligence cube on the MSTR iServer as datasource that would be great as well.
Below a link to their SOA webservices documentation to pull data into applications, perhaps an option.
Hello - does anyone know if it's possible to to place text both above and below a table in the report text tool (in this instance i'm using it to feed an automated email)
I have some text which is the body of the email but also want to add some text with a hyperlink to unsubscribe to the email, below a table but as far as I can tell, there's not a way to input the table in between text, only above/below/left/right
I want my Save Setting to stick on the Browse tool when I save output. I almost always save to Excel. The default is to save the output as an Alteryx .yxdb. That is useless unless I going to further slice and dice in Alteryx - which I'm not - which it why it being output to Excel to go to the end user. Once a file type is chosen - let that file type stick for future exports as most people save there output in the same file type each time. I find myself inadvertently saving .yxdb and then needing to resave in .xlsx.
I received from an AWS adviser the following message:
Skip Compression Analysis During COPY Checks for COPY operations delayed by automatic compression analysis.
Rebuilding uncompressed tables with column encoding would improve the performance of 2,781 recent COPY operations. This analysis checks for COPY operations delayed by automatic compression analysis. COPY performs a compression analysis phase when loading to empty tables without column compression encodings. You can optimize your table definitions to permanently skip this phase without any negative impacts.
Between 2018-10-29 00:00:00 UTC and 2018-11-01 23:33:23 UTC, COPY automatically triggered compression analysis an average of 698 times per day. This impacted 44.7% of all COPY operations during that period, causing an average daily overhead of 2.1 hours. In the worst case, this delayed one COPY by as much as 27.5 minutes.
Implement either of the following two options to improve COPY responsiveness by skipping the compression analysis phase: Use the column ENCODE parameter when creating any tables that will be loaded using COPY. Disable compression altogether by supplying the COMPUPDATE OFF parameter in the COPY command. The optimal solution is to use column encoding during table creation since it also maintains the benefit of storing compressed data on disk. Execute the following SQL command as a superuser in order to identify the recent COPY operations that triggered automatic compression analysis: WITH xids AS ( SELECT xid FROM stl_query WHERE userid>1 AND aborted=0 AND querytxt = 'analyze compression phase 1' GROUP BY xid) SELECT query, starttime, complyze_sec, copy_sec, copy_sql FROM (SELECT query, xid, DATE_TRUNC('s',starttime) starttime, SUBSTRING(querytxt,1,60) copy_sql, ROUND(DATEDIFF(ms,starttime,endtime)::numeric / 1000.0, 2) copy_sec FROM stl_query q JOIN xids USING (xid) WHERE querytxt NOT LIKE 'COPY ANALYZE %' AND (querytxt ILIKE 'copy %from%' OR querytxt ILIKE '% copy %from%')) a LEFT JOIN (SELECT xid, ROUND(SUM(DATEDIFF(ms,starttime,endtime))::NUMERIC / 1000.0,2) complyze_sec FROM stl_query q JOIN xids USING (xid) WHERE (querytxt LIKE 'COPY ANALYZE %' OR querytxt LIKE 'analyze compression phase %') GROUP BY xid ) b USING (xid) WHERE complyze_sec IS NOT NULL ORDER BY copy_sql, starttime;
Estimate the expected lifetime size of the table being loaded for each of the COPY commands identified by the SQL command. If you are confident that the table will remain under 10,000 rows, disable compression altogether with the COMPUPDATE OFF parameter. Otherwise, create the table with explicit compression prior to loading with COPY.
When I run the suggested query to check the COPY commands executed I realized all belonged to the Redshift bulk output from Alteryx.
Is there any way to implement this “Skip Compression Analysis During COPY” in alteryx to maximize performance as suggested by AWS?
I am getting error ORA-00001 Unique Constraint Violated for any error when updating my Oracle table.
Specifically, my workflow's output tool Output Options is "Update, Insert if new" so I should never get an ORA-00001 error. If the record exists, it should be updated, if it does not exist, it should be inserted. The update happens most of the time, however when the update fails, the actual error my database is raising is an ORA-20001 error with a custom error message that I want to pass all the way back to the person reading the workflow log. When I run an update in the database I receive the correct error: ORA-20001: No overrides to Sales allowed on data in closed periods. INVOICE_NBR=12345. But the error Alteryx is presenting my user is: Error: MyWorkflow_output: DataWrap2OCI:endBatch: ORA-00001: unique constraint (MY_SCHEMA.MY_TABLE_PK) violated.
Am I misinterpreting the error in Designer or is the incorrect error being presented to me?