New web interface. Version 10 of the 1010data Insights Platform offers an entirely new experience for users. The new web interface provides many features and enhancements that make performing most tasks in the Insights Platform easier than ever before. To learn more about the new Insights Platform web interface, see the launch site, Trillion-Row Spreadsheet Getting Started Guide, and 1010data User’s Guide - Version 10.

Trillion-Row Spreadsheet^®. The new Trillion-Row Spreadsheet makes performing ad hoc analysis on the Insights Platform even more interactive and intuitive. The Timeline feature makes it possible to easily change and rerun queries without breaking your workflow.

Macro Language Workshop. The Macro Language Workshop is a new tool for composing and debugging Macro Language code from a basic query to a complex QuickApp™. The Macro Language Workshop provides a suite of options for better understanding and optimizing your Macro Language code.

Simple and Custom Uploader tools. The new web interface provides redesigned upload utilities that make it easier than ever to upload and maintain data in the Insights Platform.

Enhanced Favorites system. The new web interface offers a great way to save your favorite tables, folders, and reports for easy access.

Workspaces. Pick up where you left off in the Insights Platform using Workspaces. Workspaces can easily be saved and restored for easy retrieval of recent work. Workspaces are also saved automatically, so if you get logged out by accident, you can go right back to where you were before.

Updates to the QuickApp framework. The QuickApp web application development framework has received numerous enhancements and updates, including a new charting engine, new layouts, new widgets, and new widget attributes.

Multi-metric cross tabulations. Cross tabulations now support the creation of metrics using more than one column group. This feature enables users to create more detailed summary tables.

Integrated documentation. Select documentation assets can now be viewed directly from within the new web interface.

Flat file support in TenUp™. The TenUp data loading utility now supports flat files. This upgrade allows for scripting and automating data loading tasks that require flat files without the need to use the XML API.

Faster, more scalable savetable API transaction. The XML API savetable transaction has been improved to perform faster and handle larger tables.

Approximate unique count in tabulations. Tabulations now feature the aucnt function, which uses the hyper-log-log (HLL) algorithm to greatly increase the speed of calculating unique values. The aucnt function can be used in the Trillion-Row Spreadsheet or called directly from Macro Language queries.

New web interface. The new web interface provides many new features, tools, and utilities. However, it is a substantially different experience from working in the legacy 1010data web interface. While the new interface provides a considerable number of enhancements and improvements, some workflows may not easily transfer.

New evaluation of expressions. Macro Language expressions will now cause errors if they are ambiguous. See Expressions in Version 10 FAQ for additional details.

Deprecated <defwidget>. Any QuickApp that contains the <defwidget> XML element will return errors or exhibit unpredictable behavior; <defwidget> was never supported.

Change to the behavior of <do>. <do value_="foo" col_="a"> now assigns a list-value to variable foo, while it previously assigned a comma-separated list. This may impact queries that handle the variable returned as a comma-separated list, though list-values are interchangeable with comma-separated lists in many situations.

Change to the behavior of <defop>. Operations defined with <defop> will now expand as if called with <call> as opposed to <insert>. Functionally, this means that <defop> only has access to its own variables and assignments and does not have access to variables declared and/or set in an enclosing <block> operation (i.e., <block>, <defop>, etc.).

Export button not functional in stand-alone QuickApps. QuickApps built using <widget class_="button" type_="export"> were built for situations where QuickApps were launched from the Folders and Tables browser in the legacy web interface. The export button still behaves as expected for QuickApps launched this way. However, if the same QuickApp is launched in stand-alone mode, the export button will not function as expected. Alternatively, use render.

Change to simple uploads. The Simple Uploader currently does not support the inclusion of @-prefixed metadata in flat files. For information about @-prefixed metadata, see Text File Format in the 1010data User's Guide.

Changing password in a workspace. When multiple workspaces are open and one of them is used to change a user’s password, other workspaces will not be able to communicate with the Insights Platform. To avoid this issue, change your password when only one workspace is open.

Two new block variables have been added:

• @gmtoffset_
The user's preferred time zone with Daylight Saving Time (DST) taken into account.
@gmtoffset_ provides a correction to GMT in the U.S. that takes into account DST (as observed in NYC).
• @lastlogin_
A decimal value (in date+time form) of the login date and time for the current user's last session (adjusted with @gmtoffset_).

The once attribute has been added to the <import> element of a <block> statement.
This new attribute accepts an integer value of 0 or 1 that specifies whether libraries from a path that has already been imported to the current context should be reloaded.
When once="1", libraries are not reloaded if the specified path has already been imported.
The default is 0.

Using <widget class_="chart"> allows you to create client-side data visualizations rendered by the Kendo UI^® charting engine.

The following 11 Kendo UI chart types are available:

• area
Using <widget class_="chart" type_="area"> produces a line chart with the area between the plot points and the x-axis filled with a color.
• bar
Using <widget class_="chart" type_="bar"> produces a chart with bars whose lengths represent the values in the data.
• boxplot
Using <widget class_="chart" type_="boxplot"> produces a chart that visually displays data distributions and provides information about key indicators such as the highest value, lowest value, mean, and median for the given set of columns.
• bubble
Using <widget class_="chart" type_="bubble"> produces a chart with bubbles whose size and positions on the x-axis and y-axis represent values in the data set.
• column
Using <widget class_="chart" type_="column"> produces a chart with columns whose lengths represent values in the data.
• line
Using <widget class_="chart" type_="line"> produces a chart consisting of a line of interconnected points for each column of numeric data.
• pie
Using <widget class_="chart" type_="pie"> produces a chart that displays each value in the given data set as a section of a circular pie, representing its percentage of the whole.
• rangebar
Using <widget class_="chart" type_="rangebar"> produces a chart that displays bars which represent ranges of values.
• rangecolumn
Using <widget class_="chart" type_="rangecolumn"> produces a chart that displays columns which represent ranges of values.
• scatter
Using <widget class_="chart" type_="scatter"> produces a chart in which each value is plotted as a separate data point.
• scatterline
Using <widget class_="chart" type_="scatterline"> produces a chart in which the values are plotted as separate data points with a line joining them together.

Two elements are available for the Kendo UI charting engine:

• <graphspec>
The <graphspec> element is contained within a <widget class_="chart">. Using <graphspec>, you can specify any of the Kendo UI chart-related properties, such as tick rotation or axis label color.
• <layer>
The <layer> element is contained within a <widget class_="chart">. Using <layer>, you can specify the data to be plotted via a 1010data query.

The <materialize> operation has two new attributes:

• adv_type
Specifies the manner in which the segments are distributed over the machines specified by adv_machs.
Valid values are:
• group
Each segment is written to a specified number of machines in each group in the adv_machs list. The number of machines in each group is specified by the corresponding value in the adv_stripe attribute.
• list
Each segment is consecutively written to the groups of machines in the adv_machs list, cycling through the groups until complete.
For example, the first segment is written to the first group of machines, the second segment is written to the second group, etc. When the end of the list is reached, the next segment is written to the first group in the list, and so on until all segments are written.
The default is list.
• adv_stripe
A comma-separated list of stripe values for each group specified by the adv_machs attribute.
When adv_type="group", this list consists of the number of machines in each group to which the segment should be written.
Note: The number of items in adv_stripe must match the number of groups in adv_machs.

The splitseg attribute of <materialize> no longer requires segby. If segby is not specified, the segment is split in the middle until the threshold is reached.

The sets attribute for the <rollup> operation is new.
Specifies one or more sets, where each set is a different comma-separated list of columns. Multiple sets are separated by semi-colons.
The columns in each of the sets must be among the break columns or within the subset of columns specified by the cols attribute.

Two new attributes are available for the <sel> operation:

• sample
Accepts an integer value of 1 or 0 that specifies whether or not to generalize the selection based on the value of the value attribute.
When sample="1", a row will appear in the post-selection result with a probability equal to the value of the value attribute. The value attribute can be an expression (or number) that evaluates at each row to a float between 0 and 1 or may also be N/A, which is equivalent to 0.
For instance, <sel sample="1" value="0.1"/> should select approximately 10% of the rows uniformly across the entire table.
The default is 0.
Note: The optional attribute seed can be specified to change the random seed for the sample selection.
• seed
Accepts a decimal number that specifies the random seed for the sample selection.
By default, the seed is based on the query hash so that the identical query will deterministically create the same sample.
If seed="0", a seed is non-deterministically generated when the query is run. Because of caching, the sample won't change for the current session unless the cache is cleared, but runs of the same query with seed="0" in different sessions will in general take a different sample.

The <tabu> operation may now contain multiple <tcol> elements, allowing for multi-metric cross tabulations.
The columns specified by the multiple <tcol> elements are grouped together under each column break, and the row-total columns appear at the beginning in <tcol> order.
For instance, if there are m <tcol> elements and n values in the column breaks, there will be a total of m*(1+n) columns, which will be named: t0, t1, ..., tm, m0_0, m1_0, ..., mn_0, m0_1, m1_1, ..., mn_1, ..., m0_n, m1_n, ..., mn_n. (This is an extension of the regular naming scheme for cross-tabulations.)

Cross tabulations can contain multiple <tcol> elements, allowing for multi-metric cross tabulations. The columns specified by the multiple <tcol> elements are grouped together under each column break, and the row-total columns appear at the beginning in order. Labels are not provided to differentiate the multiple <tcol> columns unless the attribute cmlabel is specified, in which case the text supplied as the value of cmlabel indicates the row of the cross-tab header on which the <tcol> labels are shown. The attribute cmorder determines whether the <tcol> labels appear in the first or last row of the header and the manner in which the <tcol> columns and column breaks are grouped in the cross tabulation.

The following two attributes are now available for the <tcol> operation:

• cmlabel
Specifies the text used to designate the row in the header that displays the <tcol> labels in a multicolumn cross tabulation. (The attribute cmlabel can be set to an empty string if no designation is needed in the header but the <tcol> labels are still desired.)
Note: If a label is specified for a <tcol>, that label is used in the header for that <tcol>; otherwise, the default label for the <tcol> is used.
By default, the row of labels appears in the final row of the cross-tab header. You can specify whether it appears in the first row or the last row of the header using the cmorder attribute, which also determines the grouping of the <tcol> columns and column breaks.
• cmorder
Specifies where to place the <tcol> labels in a multi-column cross tabulation and how to group <tcol> columns and column breaks.
Note: The attribute cmlabel must be specified; otherwise, the <tcol> labels are not shown at all.

• first
Places the <tcol> labels in the top row of the header before the column breaks; groups columns first by which <tcol> they came from, then by column breaks.
• last
Places the <tcol> labels in the last row of the header after the column breaks; groups columns first by column breaks, then by which <tcol> they came from.
The default is last.

It is no longer necessary (though it is typically desirable) for every <tcol> in a regular tabulation to be unique.

In <tcol>, all combinations of the [P|F|R][R|C|G] prefixes (expressing the result as a percentage, fraction, or rank relative to the row, column, or grand total) may now be used with most <tcol> functions (the ones that yield numeric results). Formerly they were available only in conjunction with sum and cnt.

The following changes have been made to values for the functions in a <tcol> element:

• aucnt
Provides the approximate number of unique values using the hyper-log-log algorithm.
Note: While this function can be used for small tables, it is generally used to compute the approximate number of distinct values in a column with a large number of uniques, or across a table with a very large number of rows.
• cnt
It is no longer necessary to specify the source attribute when fun="cnt".

The new geohash(latitude;longitude;precision) data-handling function returns a geohash symbol with a given precision based on the coordinates of a particular location.

The following two modeling-related functions are now available:

• g_info_iv(G;S;X;Y)
Returns the information value (IV) of X provided Y.
• g_info_woe(G;S;X;Y)
Returns the information theoretic value weight of evidence (WoE) of X provided Y.

Five new statistics functions are now available:

• g_aucnt(G;S;X;Z)
Returns an aucnt object that can be used to compute the approximate unique count of values in a given column.
• g_aucnt_merge(G;S;M;N)
Returns an aucnt object that contains a signature of two or more merged aucnt objects.
• aucnt_estimate(M)
Returns the approximate number of unique values from an aucnt object.
• g_auroc(G;S;X;Y)
Returns a model object with four different representations of the Area Under the Receiver Operator Characteristic (AUROC) as well as the perfect model value.
• g_outlier(G;S;X;Z)
Returns a numeric value indicating outliers or extreme values.

The prof_pic attribute has been added to the userdata(U;K) system function. This attribute provides a URL to the user's profile picture.

The following two attributes have been added to the alert element:

• color_
Accepts a string that specifies the background color of the widget.
The color can be specified as any valid HTML color name, an RGB value, or a hex value.
• textcolor_
Accepts a string that specifies the color of the text in the widget.
The color can be specified as any valid HTML color name, an RGB value, or a hex value.

The browser element has the following three new attributes:

• showpermissions_
Specifies whether or not to display an icon next to each item in the browser widget indicating that the user owns the item or has permission to modify it. Accepts a 1 or 0.
The default is 0.
• descicon_
Specifies whether or not to display an information icon for an item when the mouse points to it in the browser widget.
The default is 1.
• descdelay_
Specifies the number of seconds to wait before displaying the description when the mouse points to an item in the browser widget.
The default is 0.5.

The onsubmit_ attribute of the <do> operation now accepts a comma-separated list of values.

The following 21 values are now available for the action_ attribute of the <do> operation:

• action_="allocctrl"
Using <do action_="allocctrl"> changes the slave allocation strategy used by MDB.
• action_="cacheclear"
Using <do action_="cacheclear"> clears the cache after running the associated 1010data query, if specified. If no query is specified, this action simply clears the cache.
• action_="cachectrl"
Using <do action_="cachectrl"> controls cache behavior and inspects cache statistics.
• action_="compcheck"
Using <do action_="compcheck"> performs a compatibility check on a given 1010data query.
• action_="files"
Using <do action_="files"> retrieves a list of files in a valid FTP directory.
• action_="getfilter"
Using <do action_="getfilter"> gets the filter, if one exists, for a specified table.
• action_="getquery"
Using <do action_="getquery"> places the Macro Language code of a given query into an XML variable and/or as text into a dynamic variable.
• action_="hashdel"
Using <do action_="hashdel"> removes a key/value association from the user-specific private store.
• action_="hashget"
Using <do action_="hashget"> retrieves the value associated with a given key from the user-specific private store.
• action_="hashput"
Using <do action_="hashput"> saves a key/value association to the user-specific private store.
• action_="limits"
Using <do action_="limits"> sets or inspects system settings.
• action_="log"
Using <do action_="log"> sends a message to the 1010data system logger.
• action_="password"
Using <do action_="password"> changes a user's 1010data password.
• action_="qqtoqa"
Using <do action_="qqtoqa"> loads a legacy Quick Query and constructs a QuickApp with the same functionality.
• action_="query"
Using <do action_="query"> runs the given 1010data query even if no data is retrieved or if the underlying block code has not changed.
• action_="savefile"
Using <do action_="savefile"> saves the results of a 1010data query as a delimited file on the user's FTP account.
• action_="saveqa"
Using <do action_="saveqa"> commits changes to the ops of a rendered and potentially modified QuickApp and saves them as a new QuickApp.
• action_="savequery"
Using <do action_="savequery"> expands a given 1010data query and saves the ops resulting from the expansion as a query.
• action_="savetable"
Using <do action_="savetable"> executes a given 1010data query and saves the results as a table.
• action_="setfilter"
Using <do action_="setfilter"> sets the filter on a specified table.
• action_="userprofile"
Using <do action_="userprofile"> sets or retrieves user profile data and preferences.

The filter_ attribute has been added to the dropdown widget. The filter_ attribute accepts a string that specifies how to filter values in the drop-down list with respect to the text that is entered in the input field of the widget.
Valid values are:

• beginswith
Populates the drop-down list with values that begin with the text specified in the input field of the widget.
• contains
Populates the drop-down list with values that contain the text specified in the input field of the widget.

The field widget has the following three new attributes:

• changewhenselect_
Determines whether or not to change the value of the associated dynamic variable when an item is selected from a field widget with type_="auto" or type_="combo". Accepts a 1 or 0.
• emptytext_
Accepts a string that specifies the placeholder text that appears when the field is empty. The placeholder text will appear dimmed until the user enters something in the field.
• initlist_
Accepts a list-value that is used to initialize the field widget when type_="auto" or type_="combo". When the initlist_ attribute is specified, the widget is populated with the items in the list-value, not the query associated with the widget.

The type_ attribute of the field widget now accepts the value password. This creates a field that obfuscates the user's input. This is typically used for fields that take passwords or other content that should be concealed from view.

The image widget has the following three new attributes:

• alturl_
Accepts a string that specifies a URL to an alternate image the widget displays when the user points to the widget.
• fadetime_
Accepts a decimal value that specifies the number of seconds for the transition to fade between the original and alternate images.
• popuplink_
Accepts a string that specifies a URL that opens in a new browser tab when the user clicks the image.

The type_ attribute of the <layout> element now accepts two new values:

• sheaf
Creates a content layout that consists of multiple panels. Only one panel can be displayed at a time.
This layout is essentially identical to type_="tabpanel" but without the tabs.
Each content panel must be defined by its own <layout> between the opening and closing tags of the <layout type_="sheaf">.
Since there is no built-in control to change the content area displayed in this panel, this layout type is useful primarily with the openvalue_ attribute.
• window
Creates a moveable, resizable window for the contents of the layout.

Seven new attributes were added to the <layout> element:

• maxopen_
For <layout type_="collapsible">, maxopen_ accepts an integer value that specifies the maximum number of panels that can be opened.
• minimizable_
For <layout type_="window">, minimizable_ accepts a 1 or 0 that determines whether or not to display a Minimize icon in the upper-right corner of the window.
The default is 1.
• maximizable_
For <layout type_="window">, maximizable_ accepts a 1 or 0 that determines whether or not to display a Maximize icon in the upper-right corner of the window.
The default is 1.
• windowresizable_
For <layout type_="window">, windowresizable_ accepts a 1 or 0 that determines whether or not the window can be resized.
The default is 1.
• managed_
For <layout type_="window">, managed_ accepts a 1 or 0 that determines whether or not the window manager should handle this window when it is in its minimized state.
The default is 0.
• pinned_
For <layout type_="window">, when pinned_="1", the window remains stationary when the page content is scrolled.
The default is 0.
• pinnable_
For <layout type_="window">, when pinnable_="1", the window will contain a pin icon in the title bar that allows the user to pin the window at will.
The default is 0.

For <layout type_="collapsible">, setting the value of the dynamic variable associated with the openvalue_ attribute to the empty string ("") closes all the panels. Also, the value of the dynamic variable can be set to a comma-separated list that contains the indices of the panels to open.

The color_ attribute has been added to the menu widget. The color_ attribute accepts a string that specifies the background color of the widget.
If the bgcolor_ attribute is also specified, the color_ attribute overrides it.

The sorter widget has the following four new attributes:

• clickvalue_
Accepts a dynamic variable to which a value can be saved. When an item in the sorter widget is clicked, the specified dynamic variable is set to the value associated with the item.
• indexvalue_
Accepts a list-value dynamic variable to which multiple values can be saved. Each value is saved as a single list element of the variable. The indices of the items in the initializing data for the sorter widget are stored in the specified variable as elements of the list-value. The indices correspond to either the row numbers within the results of the query associated with the widget, or positions in the list supplied to the initlist_ attribute.
• toindexvalue_
Accepts a list-value dynamic variable to which multiple values can be saved. Each value is saved as a single list element of the variable. The indices of the items in the initializing data for the second list of the sorter widget are stored in the specified variable as elements of the list-value. The indices correspond to either the row numbers within the results of the query associated with the widget, or positions in the list supplied to the initlist_ attribute.
• initlist_
Accepts a list-value that is used to initialize the sorter widget. When the initlist_ attribute is specified, the widget is populated with the items in the list-value, not the query associated with the widget.

The following 13 attributes are now available for the <widget> element:

• windowed_
Accepts a 1 or 0 that determines whether or not to display the widget in a separate window.
The default is 0.
• windowlabel_
Accepts text that provides a label for the window. The label appears in the title bar.
The default is the name of the widget (i.e., the value of the name attribute).
• stripwindow_
Determines whether or not to hide the window's title bar. Accepts a 1 or 0.
When stripwindow_="1", the title bar is hidden until the user points to the window.
When stripwindow_="0", the title bar is always displayed.
The default is 0.
• renamable_
Specifies whether the title of the window can be changed. Accepts a 1 or 0.
When renamable_="1", a Settings icon appears in the title bar. The title of the window can be changed by clicking on the Settings icon and entering a new title for the window. The new title is displayed in the title bar and appears in the dock when the window is minimized.
When renamable_="0", the window cannot be renamed.
The default is 0.
• minimizable_
Accepts a 1 or 0 that determines whether or not to display a Minimize icon in the upper-right corner of the window that minimizes the window when clicked.
The default is 1.
• maximizable_
Accepts a 1 or 0 that determines whether or not to display a Maximize icon in the upper-right corner of the window that maximizes the window when clicked.
The default is 1.
• removable_
Accepts a 1 or 0 that determines whether or not to display a Close icon in the upper-right corner of the window that closes the window when clicked.
The default is 0.
• windowresizable_
Accepts a 1 or 0 that determines whether or not the window can be resized.
The default is 1.
• windowwidth_
Accepts an integer value that specifies the width of the window in which the widget is contained.
• windowheight_
Accepts an integer value that specifies the height of the window in which the widget is contained.
• managed_
Accepts a 1 or 0 that determines whether or not the window manager should handle this window when it is in its minimized state.
The default is 0.
• pinned_
When pinned_="1", the window remains stationary when the page content is scrolled.
The default is 0.
• pinnable_
When pinnable_="1", the window will contain a pin icon in the title bar that allows the user to pin the window at will.
The default is 0.

<widget class_="grid" type_="scroll"> has been updated. The following two attributes have different behavior specifically for this widget class/type:

• width_
Accepts either an integer value describing the fixed width of the container or a percentage value relative to the parent container.
• height_
Accepts either an integer value describing the fixed height of the container or a percentage value relative to the parent container.

The following new attributes are available when <widget class_="grid" type_="scroll">:

• colwidthdef_
When colwidthref_="0", accepts an integer value that specifies the width of all columns. The default is 10.
• initview_
Specifies how the grid widget renders when initialized.
• initview_
Accepts a list-value that is used to initialize the field widget when type_="auto" or type_="combo".
• allowswitchview_
Accepts an integer value of 1 or 0 that specifies whether or not to provide an item in the right-click context menu that allows the user to switch to a one row view.