Maintain Composer v6 Custom Metrics
Custom metrics, formerly called calculations, serve as additional metrics to use with your visuals to help you analyze your data. When you define a data source configuration, you can create custom metrics for it. After custom metrics are defined, they are listed with the other metrics in your visuals and dashboards that use the data source and can be used just as any other metric.
You can use custom metrics to aggregate data in different ways, whether from an entire data source or from a selected subset and, as needed, applying arithmetic operators to them. Because a custom metric represents aggregated data, it must be created using an aggregate function. Data can be aggregated on a column-wide scope, a table scope, or a window scope. For more information, see Supported Aggregation Functions.
Scope of data refers to the domain of data included in a custom metric - whether a whole column from the data source, or just part of the column. Composer always excludes data from a custom metric if it is excluded from the visual by a filter even if that data would otherwise be included in the scope of the custom metric. You can further control what data is included by choosing metric functions that match the scope you want.
You can also use row-level functions and constant values to build your formula for a custom metric. In this way, you can create custom metrics of percentages, differences, averages, and the like. For more information about row-level functions, see Composer v6 Supported Row-Level Functions.
Custom metrics can be filtered. Filters are created using the SQL-like expressions WHERE and TRANSFORM and may also use date and time filter aggregate functions. For more information about the use of filters in custom metrics, see Applying Filters to Custom Metrics.
For information on creating and deleting custom metrics, see the following links: