Page tree

 

Support | BlogContact Us | 844.332.2821

 

Contents:

This documentation applies to Trifacta Wrangler. Download this free product.
Registered users of this product or Trifacta Wrangler Enterprise should login to Product Docs through the application.

Contents:


November 15, 2017 Update

This release of Trifacta® Wrangler introduces various updates to Flow View and a completely revamped Transformer page for a simpler, faster, and more consistent user experience. Read below for additional features and details.

What's New

Import:

Workspace:

Transformer Page:

  • New navigation and layout for the Transformer page simplifies working with data and increases the area of the data grid. See Transformer Page.
  • Highlight the recipe steps where a specific column is referenced. See Column Menus
  • Disable individual steps in your recipes. See Recipe Panel
  • Search for columns by name. See Data Grid Panel.
  • Apply fuzzy logic when matching join keys. See Join Page.

 

Language:

Changes to System Behavior

Transform Editor has been removed

In Release 4.0.1 and earlier, you could type in Wrangle transformation steps as plain text in the Transform Editor as well as use the Transform Builder. 

In Release 4.1 and later, the Transform Editor has been removed, in favor of an enhanced version of the Transform Builder.

Tip: You can copy and paste raw Wrangle commands into the Choose a transformation textbox of the Transform Builder. The documentation still displays example transformation steps as Wrangle text commands.

See Transform Builder.

Dependencies Browser has been replaced

In Release 4.0.1, you could explore dependencies between your datasets through the Dependencies Browser, which was accessible through a graph in the toolbar in the Transformer page. 

In Release 4.1 and later, this browser has been replaced by the Dataset Navigator. In the Transformer page, click the drop-down next to the name of the current dataset. In the Dataset Navigator, you can browse the datasets through a list or flow view to locate another wrangled dataset to load. See Dataset Navigator

Key Bug Fixes

TicketDescription
TD-25438Deleting an upstream reference node does not propagate results correctly to the Transformer page.
TD-23787When publishing location is unavailable, spinning wheel hangs indefinitely without any error message.
TD-22467Last active sample is not displayed during preview of multi-dataset operations.
TD-22128Cannot read multi-file Avro stream if data is greater than 500 KB.
TD-19865

You cannot configure a publishing location to be a directory that does not already exist. See Generate Results Dialog.

TD-17657

splitrows transform allows splitting even if required parameter on is set to an empty value.

TD-15509

TDE files generated by the TDE download option may fail to open in Tableau if column names are more than 124 characters in length.

NOTE: When you run the job, include a publishing option to publish to TDE format. When you export the generated results, this issue no longer appears in the output.

New Known Issues

TicketComponentDescription
TD-25419Profiling

When a pivot transform is applied, some column histograms may not be updated.

Workaround: Refresh the page.

TD-21836Transformer Page

Values in a newly collected sample do not appear in sorted order, even though a sort transform had been previously applied.

Workaround: You can re-apply the sort transform to the new sample. Some limitations apply. For more information, see Sort Transform.


March 9, 2017 Update

This release features menu-based shortcuts for accessing common transformations, a visualization of relationships between datasets in flows, human-readable recipe steps, and a number of new Wrangle functions and capabilities. Details are below. 

What's New

Workspace:

  • The new flow details page includes a visual representation of your flow and detailed information about its datasets and recipes. From the Flow View page, users can swap datasets as well. See Flow View Page.

Transformer Page:

  • Column width settings now persist across transform steps, other actions, and user sessions. See Transformer Page
  • Wrangle steps can now be displayed in natural language. See Data Grid Panel.
  • New column menu shortcuts allow you to quickly assemble recipe steps from menu selections, based on a column's data type. See Column Menus.
  • New column browser streamlines interactions involving multiple columns. See Column Browser Panel

Language:

  • Window transform now supports use of aggregation functions. See Window Transform.
  • New NOW and TODAY functions.
  • New ROLLINGSUM function computes the rolling sum over a specified number of rows before and after the current row. See ROLLINGSUM Function.
  • New ROLLINGAVERAGE function computes rolling average over a specified window. See ROLLINGAVERAGE Function.
  • New ROWNUMBER function computes the row number for each row, based on order and optional grouping parameters. See ROWNUMBER Function.
  • New COUNTA function can be used to count the number of non-null values in a column based on order and grouping parameters. See COUNTA Function.
  • New COUNTDISTINCT function counts distinct number of values in a specified column. See COUNTDISTINCT Function.
  • Four new functions for testing conditional data validation: IFNULLIFMISMATCHEDIFMISSING, and IFVALID. See Type Functions.
  • New *IF functions for each available aggregation function. See Aggregate Functions.
  • For more information, see Changes to the Language.

Changes in System Behavior

Changes to the Language:

  • set and settype transforms now work on multiple columns.
  • Recipe steps are now displayed in natural language format by default in the recipe panel and suggestion cards. 
  • Some functions have been renamed to conform to common function names. 
  • For more information, see Changes to the Language.

Key Bug Fixes

TicketDescription
TD-20524Join tool hangs due to mismatched data types.
TD-20344No sample data is displayed when joins yield a data mismatch. 
TD-20173NUMFORMAT string #.#0 fails to be converted to supported string format on upgrade, and script step fails validation. For more information, see Changes to the Language.
TD-18836find function accepts negative values for the start index. These values are consumed but produce unexpected results.
TD-18746Previews in the data grid may take up to 30 seconds to dismiss.
TD-16419Comparison functions added through Builder are changed to operators in recipe

New Known Issues

TicketComponentDescription
TD-21737Transformer Page

Cannot transform downstream datasets if an upstream dataset fails to contain a splitrows transform.

Workaround: Add a splitrows transform to the upstream dataset. See Splitrows Transform.

January 16, 2017 Update

This release features the introduction of the following key features:

  • A completely redesigned execution engine (codename: Photon), which enables much better performance across larger samples in the Transformer page and faster execution. 
  • The Transform Builder, a menu-driven interface for rapidly building transforms. 

  • Fuzzy matching options for joins.
  • In-app live chat support.
  • Updated workspace terminology and organization.
  • Numerous other features and performance enhancements.

Details are below.

What's New

Workspace:

Transformer Page:

  • Substantial increase in the size of samples in Transformer page for better visibility into source data and more detailed profiling.
  • A newly designed interface helps you to quickly build transform steps. See Transform Builder
  • Scrolling and loading improvements in the Transformer page.
  • Use the Dependencies Browser to review and resolve dependency errors between your datasets. See Dataset Navigator.
  • Join tool now supports fuzzy join options. See Join Page.

Job Execution and Performance:

  • Superior performance in job execution. Run jobs on the Trifacta engine at a faster rate.

  • Numerous performance improvements to the web application across many users.
  • Improved error message on job failure.

Live Chat Support

  • Chat with Trifacta Support via in-app live chat during business hours Pacific time. Select Chat Support from the Help menu.

Changes to System Behavior

This section outlines changes to how the platform behaves that have resulted from features or bug fixes in this release.

Object Model

  • Architecture changes and related changes to the Trifacta Application enable greater flexibility in asset reuse in current and future releases. Terminology and organization in the workspace have been updated as well.

    NOTE: Beginning in this release, Trifacta Wrangler is transitioning to an enhanced object model, which is designed to support greater re-usability of objects and improved operationalization. This new object model and its related features will be introduced over multiple releases. For more information, see Changes to the Object Model.

Changes to Wrangle

  • The multisplit transform has been replaced by a more flexible version of the split transform. For more information, see Split Transform.
  • A number of functions have been renamed to conform to common function names. See Changes to the Language

Key Bug Fixes

TicketDescription
TD-18319Inconsistent results for DATEDIFF function across running environments. For more information, see Changes to the Language.
TD-16255windowfill function fails to fill over some empty cells.
TD-16086Job list drop-down fails to enable selection of correct jobs.
TD-15609Column filtering only works if filtering value is entered in lowercase.
TD-15330Pivot transform generates "Cannot read property 'primitive' of undefined" error.
TD-13162Join key selection screen and buttons are not accessible on a small desktop screen.
TD-12209In some cases, client-side runtime error messages in script steps may persist even after the issue has been fixed or may be generated if there is no valid error.
PE-557In Windows 10, the operating system default application icon is displayed.

 

New Known Issues

TicketComponentDescription
TD-19678Transformer Page

Column browser does not recognize when you place a checkmark next to the last column in the list.

Workaround: You can move the column to another location and then select it.


TD-19384Transformer Page

Preview cards take a long time to load when selecting values from a Datetime column.

Workaround: For selection purposes, you can change the data type to String. Then, make your selections and build your transform steps before switching back to Datetime data type.

TD-18584Type System

settype transforms that do not include a specified Datetime formatting string and its variant fail on upgrade. In previous releases, this formatting was permitted, and the variant to apply was inferred.

Workaround: Please review the variant information in the transform. Then, remove the step and re-apply the Date formatting through the Type drop-down for the column. The required type information is applied.

TD-19150Transformer Page

On Photon, unnest transform fails if pluck=true.

Workaround: The pluck parameter forces the removal of the unnested values from the source. You may be able to use the replace transform on the source column to remove these values.

TD-18836Transformer Page

find function accepts negative values for the start index. These values are consumed but produce unexpected results.

Workaround: Use non-negative values as inputs.

TD-18746Transformer Page

When Photon is enabled, previews in the data grid may take up to 30 seconds to dismiss.

Workaround: This issue is related to the display of suggestion cards. Although it's not an ideal solution, you can experiment with disabling the display of preview cards in the data grid options menu. See Data Grid Panel .

TD-18288Installer/Upgrader

In previous releases, any datasource that has never been used to create a dataset is no longer available after upgrade.

Workaround: The assets remain untouched on the datastore where located. As long as the user has read permissions to the datastore area, the assets can be re-imported into the platform for this release and later.

TD-17657Transform Builder

splitrows transform allows splitting even if required parameter on is set to an empty value.

Workaround: Make sure you specify a valid value for on.

TD-16419Transform BuilderComparison functions added through Builder are changed to operators in recipe.
TD-14131Compilation/Executionsplitrows transform does not work after a backslash.

August 11, 2016 Update

This release includes minor bug fixes and usability improvements.

June 27, 2016 Update

What's New

Core Transform & Profiling:

  • Union: support for custom mapping, data refresh and multi-dataset selection
  • Join: Edit and update joins. See Join Page.
  • Row number and row-based transforms
  • Additional Datetime formats: 
    • Support milliseconds. 
    • Support for ISO 8601 time zones, non-delimited datetime values (for example, yyyymmdd), and the 12-hour clock (for example,  1pm or 11:13am). 
    • See Supported Data Types.

Proxy Errors:

  • If your environment connects to the public Internet through a proxy server that modifies certificates in use, please contact your IT administrator. 

Wrangle Language:

  • New pivot transform enables pivoting and aggregating your data through a single transform step. See Pivot Transform
  • New flatten transform allows for simple unnesting of single columns of arrays into separate rows. Simpler syntax and usage than the unnest transform. See Flatten Transform
  • New if function supersedes ternary expressions and simplifies the syntax. While ternaries are still supported, you should use the if function for scripts in the future. See IF Function.
  • New sourcerownumber() function can be used to reference the original sort order of the dataset. See SOURCEROWNUMBER Function.

    NOTE: Some transforms may make original row order information unavailable. See SOURCEROWNUMBER Function.

  • header transform now accepts a sourcerownumber parameter, which references the row from the original sort order when the dataset was created. See Header Transform.
  • Expanded syntax to support deep key extraction for unnest transform. See Unnest Transform.
  • New groupEvery parameter for the unpivot transform lets you specify the number of grouped output columns. See Unpivot Transform.
  • Regular expressions are now validated in the Transform Editor. For more information, see Supported Special Regular Expression Characters.

Core User Experience:

  • Workspace: Streamlined dataset creation and enhanced Excel support. See  Import Dataset Page .
  • Additional script performance improvements.
  • User experience enhancements: wrapping script lines, updated preview for replace and set, better transformer loading experience

Performance:

  • Improvements in script performance for larger scripts in the following areas:
    • Click Add to Script when editing the Nth step of a script.
    • Add a script step through the Transform Editor.

    • Click a column name and wait for the suggestion cards.

Documentation:

  • Integrated search product documentation and Support Portal through the application. In the menu bar, click the ? icon.

  • Improved Wrangle Language reference content is now available in product documentation. Includes detailed examples for each transform and function. See Wrangle Language.

    NOTE: This content is available through the application. Select User menu > Language Cheat Sheet. The old version of this content is no longer maintained.

Changes to System Behavior

This section outlines changes to how the platform behaves that have resulted from features or bug fixes in this release.

More consistent lookups

Prior to this release, a lookup into a file containing multiple matches of the lookup returned only a single match at execution time. 

Beginning in this release, such a lookup returns all matched values but limits the maximum number of matches to 3 per source value.

Improvement to the Type System

See Improvements to the Type System.

Key Bug Fixes

TicketDescription
PE-822

Unable to connect through proxies that modify certificates. For details on the source of the error, see https://www.trifacta.com/support/articles/article/755136-error-no-internet-connection-in-trifacta-wrangler/.

TD-14968Jobs page is slow if many job cards are being loaded for display
TD-14951Workspace page is slow if many datasets are being loaded for display
TD-14908Profiling jobs fail when NaN value appears in a Decimal column
TD-14868Editing an early step in a long script causes script to fail.
TD-14685

Comparison of two null values yields true. The fix is to implemen t three-value t reatment of null values . For details, see Improvements to the Type System .

TD-13685

Datetime type mismatches do not get nulled out upon job execution.

For details, see the Mismatched Datatypes section in Improvements to the Type System.

TD-13372

Execution with a lookup produces incorrect results. See More consistent lookups below.

TD-12927

date function produces output of nested values, instead of Datetime values.

For details, see Improvements to the Type System.

TD-12795Panel for Language Cheat Sheet content is too narrow, and comments and commands in the content are cut off. 
TD-12268

You can only move datasets into projects that are displayed on the first page of the Workspace page.

TD-12166If you lose connectivity while in the Transformer page, all changes that occur until connection is restored are lost.
TD-11255

When you run a job that generates no rows in the results, the job card shows NaN% values for valid, mismatched, and missing counts.

New Known Issues

TicketComponentDescription
TD-15509ConnectivityTDE files generated by the TDE download option may fail to open in Tableau if column names are more than 124 characters in length.
TD-15330Transformer Page

Pivot transform generates "Cannot read property 'primitive' of undefined" error.

Workaround: Use the merge transform to generate the pre-pivot column values as strings. Example:

merge col: pivot_col, ""

See Merge Transform.

TD-14961Script Infrastructure

In upgraded datasets, all rows may fail to appear in the Transformer page when the dataset's scripts include transforms that require some form of Datetime typing. These transforms can include datediff functions or transforms that have conditional expressions resulting in true or false based on date evaluation.

Examples:

keep row: (date(2016, 4, 1) <= RegDate) && (RegDate < date(2016, 5, 1))

derive value: (date_column > date(1, 1, 2014)) ? 'after 2013' : 'before 2014'

Workaround: In the Transformer page, click the step before the suspect transform. Edit it and add it back to the script. Click the suspect transform, edit it, and add it back to the script. The data should show in the Transformer page.

TD-14524Transformer Page

Transform Editor does not trap out-of-range values for Integer and Decimal types.

Workaround: Please use the safe ranges for each of the data types. See Supported Data Types.

TD-13785Transformer Page

Cannot navigate away from Create Dataset page if the Trifacta Application service restarts.

Workaround: Restart the application.

TD-13162Transformer Page - Tools

Join key selection screen and buttons are not accessible on a small desktop screen.

Workaround: Zoom out to make the controls available, use them, and then zoom in to 100% again.

February 25, 2016 Update

Key Bug Fixes

The following important bug fixes have been addressed in this release.

TicketDescription
PE-789After upgrade, when opening some pre-existing datasets, the Transformer page is blank.

February 23, 2016 Update

What's New

Many new features in this release. Read on!

Core features:

  • Newly supported data types:
    • Social Security Number (SSN)
    • Phone Number
    • Email Address
    • Credit Card
    • Gender
    • Zip Code
    • See Supported Data Types.
  • New workflow for creating projects. See Create Flow Page.
  • Change datasources for your dataset. See Transformer Page.
  • The new Union tool enables concatenation of multiple datasets. See Union Page

Wrangle:

Performance:

  • Improvements in initial column- and row-splitting inference
  • Improvements to UI performance and overall user experience
  • Improvements in Transformer page with long scripts
  • More consistent sorting across data types 

 

Upgrade Changes

Script Upgrade Issues

To support the upgrading of scripts to Release 3.0.1, some changes have been made to your Wrangle scripts.

NOTE: If you are upgrading to Release 3.0.1 or later, please review these known issues and apply the changes listed below. You should also review the required transform updates for Release 3.0.

Changes to auto-generated column names:

The names given to columns that are generated by your script steps has changed:

 

Prior to Release 3.0, these column names were named in the following format:

column1
column2
etc.

For Release 3.0.1 and later, these column names are generated according to the following method:

 

  1. If the transform includes a function reference, the function name is included in the new column. 

    Example TransformColumn Name
    derive value:left(city,3)
    left_city
  2. If the above step is applied again, a duplicate column is generated with the following name:

    Example TransformColumn Name
    derive value:left(city,3)
    left_city1
  3. If the transform does not contain a function reference, the old naming convention is used, as in the following examples:

    Example TransformColumn Name
    derive value:'4'
    column1
    derive value:'5'
    column2

 

The above change has implications in script upgrades:

NOTE: When your existing scripts are upgraded, the old generated names are preserved, and they should work as previously. 

However, to ease migration to the new format, all Lookup steps in your migrated scripts have been converted to Join steps of left outer join type. While it should not be necessary, you can edit the step and re-specify as a Lookup after migration.

  • When you edit a step in an upgraded script through the application, however, the new naming logic is applied. All subsequent steps in the script that apply to the affected column(s) are automatically updated for you.

    NOTE: The propagation of these name changes does not apply to steps that contain joins or unions. These steps may break if they are referencing the old names of updated columns.

    NOTE: If you make edits before any header step in your script may break the header step or any steps in which the old version of the edited column name appears.

  • When you download a script, the new naming logic is applied to your exported script. The names in the script stored in the application are not changed with this operation.

    NOTE: Be aware that copying and pasting of script steps may break if the source and target scripts have not been consistently updated to the new naming convention.

Tip: Beginning in Release 3.0, you can explicitly name generated columns using the as keyword. For the list of transforms that support this keyword, select the User menu > Language Cheat Sheet. Then, search the page for as:.

Required Changes to Transform Parameters

In Release 3.0, improvements on how transform steps are checked against type have illuminated some issues, which may affect scripts created in previous versions. Please be aware of the following if you are upgrading from Release 2.7 or earlier. These issues must be fixed when you edit your scripts in Release 3.0 or later:

merge:

  • In previous releases, you were permitted to use a Trifacta pattern or regex pattern as part when merging columns and strings. Beginning in Release 3.0, your previous scripts will still work, but when you edit them, you must replace any patterns in your merge with string values.

extractlist transform:

  • Prior to Release 3.0, the extractlist transform allowed use of patterns for the delimiter and quote parameters. Beginning in Release 3.0, these values must be literal string values. Patterns are not supported.

extractkv transforms:

  • In previous releases, some parameters were listed as pattern values for this transform in the Transform Editor, even though string values were accepted. When you edit upgraded scripts in Release 3.0 or later, patterns inserted as values for the valueafter and delimiter parameters must be changed to string values.

Key Bug Fixes

The following important bug fixes have been addressed in this release.

TicketDescription
PE-745Generate Results button is still active, even if there is no valid script.
PE-547In the Workspace page, if you can cancel out of a notification window, the empty window remains on-screen.
PE-481If the dataset description includes special characters, you cannot open results from the dataset through the UI.
PE-361
Some data types are not supported in Trifacta Wrangler . Data types for phone number, social security number, email address, credit card, gender, and zip code should be supported.
TD-12276Single backslash characters are shifted in field values by one character.
TD-11662Transformer Page locks up after editing and reloading a script.
TD-11628

The application crashes when unnest step generates too many rows for browser memory.

NOTE: Unnest, union, or join transforms may significantly increase the number of rows or columns in your dataset. To prevent overloading the browser's memory, the application may apply a limit function to the results to artificially limit the number of rows displayed in your sample. You can generate a new sample if desired. This limitation is not applied during the job execution.

TD-11540No suggestion cards are offered for some selections in a dataset with a single record.
TD-10982

When merging column ranges, the with parameter delimiter is not respected.

NOTE: In previous releases, the comma delimiter was used for ranges, regardless of the specification of the with parameter.

merge col: col1~col3, col4 with: ';'

Unless your subsequent script steps depend on the comma delimiter between col1, col2, and col3, no post-upgrade changes should be required. If no with parameter value is specified, the comma delimiter is used.

TD-10710
When columns and strings are merged using Trifacta patterns or regular expressions, a backslash (/) is added before and after string values in the data grid.
TD-6975When you cancel adding additional join keys, a new join key is still added.

Required Changes to Transform Parameters

Improvements on how transform steps are checked against type have illuminated some issues, which may affect scripts created in previous versions. Please be aware of the following if you are upgrading from an earlier version. These issues must be fixed when you edit your scripts:

merge:

  • In previous releases, you were permitted to use a Trifacta pattern or regex pattern as part when merging columns and strings. Beginning in this release, your previous scripts will still work, but when you edit them, you must replace any patterns in your merge with string values.

extractlist transform:

  • In previous releases, the extractlist transform allowed use of patterns for the delimiter and quote parameters. Beginning in this release, these values must be literal string values. Patterns are not supported.

extractkv transforms:

  • In previous releases, some parameters were listed as pattern values for this transform in the Transform Editor, even though string values were accepted. When you edit upgraded scripts in this release or later, patterns inserted as values for the valueafter and delimiter parameters must be changed to string values.

New Known Issues

The following issues are known to appear in this release.

  • Any Known Issues from prior releases that have been fixed are listed in the Key Bug Fixes section. 
  • Unfixed Known Issues from earlier releases are listed in the Release Notes pages for the version where they were discovered.
TicketComponent(s)Description
TD-12268Workspace

You can only move datasets into projects that are displayed on the first page of the Workspace page.

Workaround: Sort or rename your target project so that it appears on the first page of the Workspace page.

TD-12209Transformer Page

In some cases, client-side runtime error messages in script steps may persist even after the issue has been fixed or may be generated if there is no valid error.

Workaround: If you encounter an error that you think is invalid or has been fixed, you can do one of the following:

  • Edit the script step and immediately save it without making changes.

  • Undo and re-add the script step.

  • Ignore the error and add a copy of the script step again.

  • Delete and re-add the script step.

If the error still persists, it is probably valid.

TD-12166Transformer PageIf you restart the application or lose connectivity while in the Transformer page, all subsequent changes are lost when connection is restored.
TD-10836Compilation/Execution

Size of first K rows sample or random sample may be inaccurate.

Workaround: This issue may be caused by runaway records with improperly escaped characters. In your dataset, you may look for mismatched sets of fields in specific rows and consider removing them to improve size accuracy.

TD-11255Compilation/ExecutionWhen you run a job that generates no rows in the results, the job card shows NaN% values for valid, mismatched, and missing counts.

January 12, 2016 Update

Happy New Year from  Trifacta!

What's New

  • Updated Terms of Service. See the product for details.

Key Bug Fixes

None.

November 18, 2015 Update

What's New

Support for server access through network proxy.

Key Bug Fixes

None.

November 4, 2015 Update

This update addresses the following issues.

Key Bug Fixes

TicketDescription
PE-603User messaging on file size limit errors is being suppressed, although limits are enforced.
PE-547When some notification windows are canceled, the white container box remains displayed on-screen.
PE-497
If Trifacta Wrangler crashes during job execution, that job remains in-progress forever.
PE-266
If the Trifacta Wrangler server is unavailable, the connection error page does not render properly.
PE-258If the results files are moved through the file system, the Results Summary page fails to load and does not display an error message.

 

Trifacta Wrangler Release 1.0

Welcome to the first release of Trifacta Wrangler

Key Features

  • Import data in text (such as CSVs, TSVs, log files, etc.), JSON, or Excel format. 
    • Compressed GZIP files are automatically unzipped and processed.
  • Locate missing or mismatched data through graphical data quality bars for each column. Then, select missing or mismatched data to be prompted with a set of pre-defined transformations that can be immediately applied to the data. See Overview of Predictive Transformation.
  • Identify statistical outliers in each column using its data histogram. Select these values and make changes to them as needed. See Locate Outliers.
  • Unnest complex, nested data structures with a simple step.
  • Explore data details in individual columns, including frequency of values, standard deviation, and other statistical metrics. You can also select examples here to trigger suggestions. See Column Details Panel
  • Merge your dataset with another or perform joins between datasets through the intuitive interface. 
  • When ready, execute your script and generate results in a variety of formats, including Tableau Data Extract (TDE) format.
  • As needed, you can modify your transformation steps to fine-tune parameters using Wrangle, a purpose-built data transformation language. See Wrangle Language.
  • To get started using Trifacta Wrangler, see Workflow Basics

Known Issues

The following issues are known to appear in this release.

TicketDescription
PE-585After the name of a dataset has been changed, subsequent results generated from the dataset use the old dataset name in the filename.
PE-557In Windows 10, the operating system default application icon is displayed.
PE-547When some notification windows are canceled, the white container box remains displayed on-screen.
PE-500"Job Results" indicator appears in the Sample menu, when it should read, "Results Sample."
PE-481If the dataset description includes special characters, you cannot open results from the dataset through the UI.
PE-414
Use of Trifacta Wrangler is not fully supported across multiple machines. Projects and job executions are stored locally and are therefore not available on secondary machines.
PE-369Timestamp on the output directory is in UTC time zone, instead of the client time zone.
PE-361
Some data types are not supported in Trifacta Wrangler. Data types for phone number, social security number, email address, credit card, gender, and zip code should be supported.
PE-258If the results files are moved through the file system, the Results Summary page fails to load and does not display an error message.
PE-41Some icons are clipped throughout the application.

Your Rating: Results: PatheticBadOKGoodOutstanding! 4 rates

This page has no comments.