@gooddata/sdk-maql-language-server 0.0.0-stage → 11.65.0-alpha.11

package/esm/docs/en/docs/create-metrics/maql/statistic/standard-deviation-functions.js

@@ -0,0 +1,88 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# Standard Deviation Functions
+Standard deviation function return the statistical standard deviation of
+all values in the set based on a sample of the population (STDEV), or
+based on a biased population (STDEVP).
+
+Standard deviation is useful for measuring variance within a data set
+and, in application, confidence in statistical results. For example, in
+finance, standard deviation can measure the potential deviation from
+expected return rate, measuring the volatility of the investment.
+Depending on the number of values in the sample set, you should use
+either of the following metrics.
+
+-   \`STDEV (*numeric*)\`, also known as the **corrected standard deviation**
+
+    ![Equation - Standard Deviation](https://www.gooddata.com/developers/cloud-native/doc/maql/stdev.png)
+    -   where *numeric* is a fact or metric
+    -   Computes the sum of squared differences from the mean for *n*
+        values divided by a sample size factor. If the input values are
+        a sample of the total (biased) population, the divisor is *(n -
+        1)* sample size, which is used in the STDEV function.
+
+    -   This value is the **variance**. See [Variance Functions](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/statistic/variance-functions/). The square root of the above value represents the standard deviation.
+
+        If individual values are used as inputs, STDEV, generates a null
+        value. In these cases, use STDEVP instead.
+
+-   \`STDEVP (*numeric*)\`, also known as the **uncorrected standard deviation**.
+
+    ![Equation - Standard Deviation for Populations](https://www.gooddata.com/developers/cloud-native/doc/maql/stdevp.png )
+
+    -   where *numeric* is a fact or metric
+    -   Computes square root of the sum of squared differences from the mean for *n* values divided by *n*
+    -   Use STDEVP for calculating standard deviations if the input set
+        contains the entire (unbiased) population of values. The
+        deviation for a single value is zero.
+
+## Syntax
+
+\`\`\`
+SELECT STDEV(…)
+SELECT STDEV(metric)
+SELECT STDEVP(fact)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT STDEV({metric/internal_rate_of_return})
+SELECT STDEVP({metric/gross_weight})
+\`\`\`
+
+## Using Standard Deviation
+
+You can use standard deviation to create ranges as other metrics.
+Suppose you have a standard deviation metric (StDev Transaction Amt):
+
+### Example 1: +1 Std.
+
+\`\`\`
+SELECT {metric/avg_transaction_amt} + {metric/stdev_transaction_amt}
+\`\`\`
+
+### Example 2: +2 Std.
+
+\`\`\`
+SELECT {metric/avg_transaction_amt} + ({metric/stdev_transaction_amt} * 2)
+\`\`\`
+
+### Example 3: -1 Std.
+
+\`\`\`
+SELECT {metric/avg_transaction_amt} + ({metric/stdev_transaction_amt} * -1)
+\`\`\`
+
+### Example 4: -2 Std.
+
+\`\`\`
+SELECT {metric/avg_transaction_amt} + ({metric/stdev_transaction_amt} * -2)
+\`\`\`
+
+### Sample Chart
+
+Using the examples above, you can create a combo chart that shows all
+individual transactions (X axis) and where they fall within bands of
++2/-2 standard deviations (Y axis).
+
+![Transaction amounts compared to standard deviations](https://www.gooddata.com/developers/cloud-native/doc/maql/stdev-transaction-accounts.png)`;

package/esm/docs/en/docs/create-metrics/maql/statistic/variance-functions.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Variance Functions\nReturns the statistical variance - how far a set of values is spread out based on a sample of the population (VAR), or based on a biased population (VARP). Variance is non-negative, zero indicates that all values are identical.\n\nVariance computation is used to build standard deviation and other statistical functions.\n\nTo measure spread, variance calculates the mean of all values in the\nsample. For each input value in the set, the difference of the value\nfrom the mean is computed, and this difference is squared. All of the\nsquares are added together, and then divided by a sample size factor,\ndepending on the function you are using.\n\n-   Values for variance are non-negative. A value of 0 indicates that\n    there is no variance among the values; all values are identical.\n-   The square root of variance is the standard deviation. See [Standard Deviation Functions](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/statistic/standard-deviation-functions/).\n-   Covariance measures how two sets of values change together. See\n    [Covariance Functions](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/statistic/covariance-functions/).\n\nThe spread is measured for a sample of the (biased) population (VAR) or\nfor the entire (unbiased) population (VARP).\n\n-   For a sample of the population, use the VAR function, which divides\n    the sum of squares by the number of values in the same size (N-1):\n\n    ![Equation - Variance](https://www.gooddata.com/developers/cloud-native/doc/maql/var.png)\n    -   `VAR (*numeric*)`\n        -   where *numeric* is a fact or metric\n        -   Computes the sum of squared differences from the mean for\n            *n* values divided by *n-1*\n\n-   If the set of values is the entire population of values, use the\n    VARP function, which divides the sum of squares by N:\n\n    ![Equation - Variance for Populations](https://www.gooddata.com/developers/cloud-native/doc/maql/var.png)\n\n    -   `VARP (*numeric*)``\n        -   where *numeric* is a fact or metric\n        -   Computes the sum of squared differences from the mean for\n            *n* values divided by *n*]\n\n## Syntax\n\n```\nSELECT VAR(\u2026)\nSELECT VAR(metric)\nSELECT VARP(fact)\n```\n\n## Examples\n\n```\nSELECT VAR({metric/internal_rate_of_return})\nSELECT VARP({metric/gross_weight})\n```";
+//# sourceMappingURL=variance-functions.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/statistic/variance-functions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"variance-functions.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/statistic/variance-functions.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,y3EAoDb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/statistic/variance-functions.js

@@ -0,0 +1,54 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# Variance Functions
+Returns the statistical variance - how far a set of values is spread out based on a sample of the population (VAR), or based on a biased population (VARP). Variance is non-negative, zero indicates that all values are identical.
+
+Variance computation is used to build standard deviation and other statistical functions.
+
+To measure spread, variance calculates the mean of all values in the
+sample. For each input value in the set, the difference of the value
+from the mean is computed, and this difference is squared. All of the
+squares are added together, and then divided by a sample size factor,
+depending on the function you are using.
+
+-   Values for variance are non-negative. A value of 0 indicates that
+    there is no variance among the values; all values are identical.
+-   The square root of variance is the standard deviation. See [Standard Deviation Functions](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/statistic/standard-deviation-functions/).
+-   Covariance measures how two sets of values change together. See
+    [Covariance Functions](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/statistic/covariance-functions/).
+
+The spread is measured for a sample of the (biased) population (VAR) or
+for the entire (unbiased) population (VARP).
+
+-   For a sample of the population, use the VAR function, which divides
+    the sum of squares by the number of values in the same size (N-1):
+
+    ![Equation - Variance](https://www.gooddata.com/developers/cloud-native/doc/maql/var.png)
+    -   \`VAR (*numeric*)\`
+        -   where *numeric* is a fact or metric
+        -   Computes the sum of squared differences from the mean for
+            *n* values divided by *n-1*
+
+-   If the set of values is the entire population of values, use the
+    VARP function, which divides the sum of squares by N:
+
+    ![Equation - Variance for Populations](https://www.gooddata.com/developers/cloud-native/doc/maql/var.png)
+
+    -   \`VARP (*numeric*)\`\`
+        -   where *numeric* is a fact or metric
+        -   Computes the sum of squared differences from the mean for
+            *n* values divided by *n*\]
+
+## Syntax
+
+\`\`\`
+SELECT VAR(…)
+SELECT VAR(metric)
+SELECT VARP(fact)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT VAR({metric/internal_rate_of_return})
+SELECT VARP({metric/gross_weight})
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/time/for-each.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FOR EACH\nThe **FOR EACH** clause allows you to display all attribute values in your visualization, even if they are missing.\n\nIf you want to display how many visits are planned for each particular month, the visualization normally shows you all months with at least one visit planned.\n\n![Table](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins02.png)\n\nIf you use the **FOR EACH** for month of the year, the visualization will show you also the months that have no visits planned. \n\n![FOR Each in Metric](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins01.png)\n\nWhen creating metrics with `FOR EACH`, remember that:\n\n* The visualizations in Analytical Designer must be sliced with the same attributes that are used in the `FOR EACH` clauses to display the missing values. Otherwise, `FOR EACH` is ignored.\n\n* If the visualization contains multiple metrics with `FOR EACH` applied, the visualization displays all attribute values. \n\n* When `FOR EACH` is applied, the visualization displays all attribute values between the first and the last metric values available. \n    \n    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins04.png)\n\n    If the visualization contains multiple metrics, it displays attribute values from all metrics.\n\n     ![Metrics in One Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins05.png)\n\nYou can also select the **show all values** option in your visualizations in Analytical Designer to display similar results. For details, see [FOR EACH versus Show All Values](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-each/#for-each-versus-show-all-values) and [Create Visualizations](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-visualizations/).\n\n#### Day versus Day of Week\n\nWhen With date attributes, the `FOR EACH` clause displays the following:\n\n* For `month` and similar, the `FOR EACH` clause displays attribute values from the first to the last metric values available, including the missing values in between.\n    ![Month](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins06.png)\n\n* For `month of year` and similar date attributes, the `FOR EACH` clause display always all attribute values.\n     ![Month of Year](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins07.png)\n\n\n\n#### FOR EACH versus Show All Values\n\nThe `FOR EACH` clause and the `Show all values` option in Analytical Designer show similar results.\n\n* `FOR EACH` displays attribute values between the first and the last metric values of each metric, including the missing values in between. \n\n    If any attribute value falls outside of such intervals for all metrics, it is not displayed.\n\n    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins08.png)\n\n* `Show all values` displays all attribute values regardless of the metric values available.\n\n    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins09.png)\n\n\n\n## Syntax\n\n```\nSELECT ... BY ... FOR EACH (attribute/label), (attribute/label), ...\n```\n\n## Examples\n\nDisplay the sum for all sold items every month. The `FOR EACH` clause displays also items and months with no sale.\n```\nSELECT SUM(fact/sales) FOR EACH (attribute/saledate.month), (attribute/item)\n```\n\nDisplay the moving average. The `FOR EACH` clause displays also the days without any change.\n```\nSELECT RUNAVG({metric/value}) ROWS BETWEEN 6 PRECEDING AND CURRENT ROW FOR EACH(date.day)\n```\n\nDisplay the moving average. The `FOR EACH` clause displays also the days without any change and shows missing values as zeros. \n```\nSELECT RUNAVG( IFNULL({metric/value},0)) ROWS BETWEEN 6 PRECEDING AND CURRENT ROW FOR EACH(date.day)\n```\n\nDisplay the bottom 10 products with the lowest number of orders. The `FOR EACH` clause counts also the products with no orders.\n```\nSELECT COUNT({label/order_id}) FOR EACH {label/product_name} WHERE BOTTOM(10) OF (COUNT({label/order_id}) )\n```\n\n## Data Source Support for Dates\n\nSome of the data sources may not fully support FOR EACH with **date attributes**:\n\n* *Dremio*, *Drill*, *Redshift*, and *Synapse* do not support FOR EACH for date attributes.\n\n* *SQL Server 2022 (16.x)*, *Azure SQL Database* and *Azure SQL Managed Instance* support date attributes only from the compatibility level 160.\n\nOther data sources fully support FOR EACH for all attributes.\n\nYou can create metrics with FOR EACH even if your data source does not support it. If you add such metric to a visualization, Analytical Designer will display an error.\n{{% /alert %}}";
+//# sourceMappingURL=for-each.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/for-each.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-each.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/for-each.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,8tJA8FL,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/for-each.js

@@ -0,0 +1,96 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FOR EACH
+The **FOR EACH** clause allows you to display all attribute values in your visualization, even if they are missing.
+
+If you want to display how many visits are planned for each particular month, the visualization normally shows you all months with at least one visit planned.
+
+![Table](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins02.png)
+
+If you use the **FOR EACH** for month of the year, the visualization will show you also the months that have no visits planned. 
+
+![FOR Each in Metric](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins01.png)
+
+When creating metrics with \`FOR EACH\`, remember that:
+
+* The visualizations in Analytical Designer must be sliced with the same attributes that are used in the \`FOR EACH\` clauses to display the missing values. Otherwise, \`FOR EACH\` is ignored.
+
+* If the visualization contains multiple metrics with \`FOR EACH\` applied, the visualization displays all attribute values. 
+
+* When \`FOR EACH\` is applied, the visualization displays all attribute values between the first and the last metric values available. 
+    
+    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins04.png)
+
+    If the visualization contains multiple metrics, it displays attribute values from all metrics.
+
+     ![Metrics in One Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins05.png)
+
+You can also select the **show all values** option in your visualizations in Analytical Designer to display similar results. For details, see [FOR EACH versus Show All Values](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-each/#for-each-versus-show-all-values) and [Create Visualizations](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-visualizations/).
+
+#### Day versus Day of Week
+
+When With date attributes, the \`FOR EACH\` clause displays the following:
+
+* For \`month\` and similar, the \`FOR EACH\` clause displays attribute values from the first to the last metric values available, including the missing values in between.
+    ![Month](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins06.png)
+
+* For \`month of year\` and similar date attributes, the \`FOR EACH\` clause display always all attribute values.
+     ![Month of Year](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins07.png)
+
+
+
+#### FOR EACH versus Show All Values
+
+The \`FOR EACH\` clause and the \`Show all values\` option in Analytical Designer show similar results.
+
+* \`FOR EACH\` displays attribute values between the first and the last metric values of each metric, including the missing values in between. 
+
+    If any attribute value falls outside of such intervals for all metrics, it is not displayed.
+
+    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins08.png)
+
+* \`Show all values\` displays all attribute values regardless of the metric values available.
+
+    ![Metrics in Separate Visualizations](https://www.gooddata.com/developers/cloud-native/doc/maql/outerjoins09.png)
+
+
+
+## Syntax
+
+\`\`\`
+SELECT ... BY ... FOR EACH (attribute/label), (attribute/label), ...
+\`\`\`
+
+## Examples
+
+Display the sum for all sold items every month. The \`FOR EACH\` clause displays also items and months with no sale.
+\`\`\`
+SELECT SUM(fact/sales) FOR EACH (attribute/saledate.month), (attribute/item)
+\`\`\`
+
+Display the moving average. The \`FOR EACH\` clause displays also the days without any change.
+\`\`\`
+SELECT RUNAVG({metric/value}) ROWS BETWEEN 6 PRECEDING AND CURRENT ROW FOR EACH(date.day)
+\`\`\`
+
+Display the moving average. The \`FOR EACH\` clause displays also the days without any change and shows missing values as zeros. 
+\`\`\`
+SELECT RUNAVG( IFNULL({metric/value},0)) ROWS BETWEEN 6 PRECEDING AND CURRENT ROW FOR EACH(date.day)
+\`\`\`
+
+Display the bottom 10 products with the lowest number of orders. The \`FOR EACH\` clause counts also the products with no orders.
+\`\`\`
+SELECT COUNT({label/order_id}) FOR EACH {label/product_name} WHERE BOTTOM(10) OF (COUNT({label/order_id}) )
+\`\`\`
+
+## Data Source Support for Dates
+
+Some of the data sources may not fully support FOR EACH with **date attributes**:
+
+* *Dremio*, *Drill*, *Redshift*, and *Synapse* do not support FOR EACH for date attributes.
+
+* *SQL Server 2022 (16.x)*, *Azure SQL Database* and *Azure SQL Managed Instance* support date attributes only from the compatibility level 160.
+
+Other data sources fully support FOR EACH for all attributes.
+
+You can create metrics with FOR EACH even if your data source does not support it. If you add such metric to a visualization, Analytical Designer will display an error.
+{{% /alert %}}`;

package/esm/docs/en/docs/create-metrics/maql/time/for-next-period.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FOR NextPeriod\nFOR NextPeriod function allows you to compute a metric for a future time\nperiod the granularity of which is determined contextually by the most\ngranular date attribute that is defined in the visualization.\n\nFOR NextPeriod works similarly to FOR Next function unless the\nadaptable functions adapt to the context of the visualization. Even\nthough the metric is defined as FOR NextPeriod(Quarter), for example,\nthe function returns values from the next month, as month is the most\ngranular date attribute in this visualization.\n\n## Syntax\n\n```\nSELECT \u2026 FOR NextPeriod(\u2026,\u2026)\nSELECT metric FOR NextPeriod( time_attribute )\n```\n\n## Examples\n\n```\nSELECT {metric/revenue} FOR NextPeriod({attribute/quarter} )\nSELECT {metric/payment} FOR NextPeriod({attribute/quarter} , 3)\n```\n\nAs was the case for the functions Previous( ) and PreviousPeriod( ), see\n[Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/),\nthe differences between Next( ) and NextPeriod( ) become most relevant\nwhen a visualization contains a more granular date attribute than the one that is specified\nwithin the functions themselves.\n\nThe chart below demonstrates the\ndifferences between `Leads FOR Next{attribute/quarter})` and `Leads FOR\nNextPeriod{attribute/quarter})` in a visualization broken across a more granular *Date*\nattribute.\n\n![iThe Next( ) function strictly follows the date attribute specified within the functions parentheses.](https://www.gooddata.com/developers/cloud-native/doc/maql/for-next-period.jpg)";
+//# sourceMappingURL=for-next-period.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/for-next-period.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-next-period.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/for-next-period.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,gpDAoCoK,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/for-next-period.js

@@ -0,0 +1,38 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FOR NextPeriod
+FOR NextPeriod function allows you to compute a metric for a future time
+period the granularity of which is determined contextually by the most
+granular date attribute that is defined in the visualization.
+
+FOR NextPeriod works similarly to FOR Next function unless the
+adaptable functions adapt to the context of the visualization. Even
+though the metric is defined as FOR NextPeriod(Quarter), for example,
+the function returns values from the next month, as month is the most
+granular date attribute in this visualization.
+
+## Syntax
+
+\`\`\`
+SELECT … FOR NextPeriod(…,…)
+SELECT metric FOR NextPeriod( time_attribute )
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT {metric/revenue} FOR NextPeriod({attribute/quarter} )
+SELECT {metric/payment} FOR NextPeriod({attribute/quarter} , 3)
+\`\`\`
+
+As was the case for the functions Previous( ) and PreviousPeriod( ), see
+[Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/),
+the differences between Next( ) and NextPeriod( ) become most relevant
+when a visualization contains a more granular date attribute than the one that is specified
+within the functions themselves.
+
+The chart below demonstrates the
+differences between \`Leads FOR Next{attribute/quarter})\` and \`Leads FOR
+NextPeriod{attribute/quarter})\` in a visualization broken across a more granular *Date*
+attribute.
+
+![iThe Next( ) function strictly follows the date attribute specified within the functions parentheses.](https://www.gooddata.com/developers/cloud-native/doc/maql/for-next-period.jpg)`;

package/esm/docs/en/docs/create-metrics/maql/time/for-next.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FOR Next\nBy default, the FOR Next function refers to values from one time period\nin the future. This can be customized by adding a second parameter to\nthe function.\n\n## Syntax\n\n```\nSELECT \u2026 FOR Next(\u2026,\u2026)\nSELECT metric FOR Next(time_attribute)\n```\n\n## Examples\n\n```\nSELECT {metric/revenue} FOR Next({attribute/quarter})\n```\n\nYou can customize FOR Next() by adding a second parameter to the\nfunction. For example, you might want to return a payment value from\nthree quarters in the future with respect to a certain time period (see\nbelow).\n\n```\nSELECT {metric/payment} FOR Next({attribute/quarter},3)\n```";
+//# sourceMappingURL=for-next.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/for-next.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-next.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/for-next.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,yoBAyBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/for-next.js

@@ -0,0 +1,27 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FOR Next
+By default, the FOR Next function refers to values from one time period
+in the future. This can be customized by adding a second parameter to
+the function.
+
+## Syntax
+
+\`\`\`
+SELECT … FOR Next(…,…)
+SELECT metric FOR Next(time_attribute)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT {metric/revenue} FOR Next({attribute/quarter})
+\`\`\`
+
+You can customize FOR Next() by adding a second parameter to the
+function. For example, you might want to return a payment value from
+three quarters in the future with respect to a certain time period (see
+below).
+
+\`\`\`
+SELECT {metric/payment} FOR Next({attribute/quarter},3)
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/time/for-previous-period.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FOR PreviousPeriod\nThe FOR PreviousPeriod function is similar to FOR Previous functions\nunless the adaptable functions adapt to the context of the visualization by\nhand.\n\nEven though the metric is defined as FOR PreviousPeriod({attribute/quarter}),\nfor example, the function returns values from the previous month, as\nmonth is the most granular date attribute in this visualization.\n\n## Syntax\n\n```\nSELECT \u2026 FOR PreviousPeriod(\u2026,\u2026)\nSELECT metric FOR PreviousPeriod(time_attribute)\n```\n\n## Examples\n\n```\nSELECT {metric/payment} FOR PreviousPeriod({attribute/quarter})\nSELECT {metric/payment} FOR PreviousPeriod({attribute/quarter}, 2)\n```\n\nFor differences between FOR Previous and FOR PreviousPeriod,\nsee [Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/).";
+//# sourceMappingURL=for-previous-period.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/for-previous-period.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-previous-period.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/for-previous-period.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,i6BAwBoK,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/for-previous-period.js

@@ -0,0 +1,26 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FOR PreviousPeriod
+The FOR PreviousPeriod function is similar to FOR Previous functions
+unless the adaptable functions adapt to the context of the visualization by
+hand.
+
+Even though the metric is defined as FOR PreviousPeriod({attribute/quarter}),
+for example, the function returns values from the previous month, as
+month is the most granular date attribute in this visualization.
+
+## Syntax
+
+\`\`\`
+SELECT … FOR PreviousPeriod(…,…)
+SELECT metric FOR PreviousPeriod(time_attribute)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT {metric/payment} FOR PreviousPeriod({attribute/quarter})
+SELECT {metric/payment} FOR PreviousPeriod({attribute/quarter}, 2)
+\`\`\`
+
+For differences between FOR Previous and FOR PreviousPeriod,
+see [Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/).`;

package/esm/docs/en/docs/create-metrics/maql/time/for-previous.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FOR Previous\nBy default, the FOR Previous function refers to values from one time\nperiod ago. You can customize FOR Previous by adding a second parameter\nto the function.\n\n## Syntax\n\n```\nSELECT \u2026 FOR Previous(\u2026,\u2026)\nSELECT metric FOR Previous(time_attribute)\nSELECT metric FOR Previous(time_attribute, #periods_ago)\n```\n\n## Examples\n\n```\nSELECT {metric/revenues} FOR Previous({attribute/quarter})\n```\n\nYou can customize FOR Previous() by adding a second parameter to the function. For\nexample, you may want to return a revenue value from three quarters ago\n(see below).\n\n```\nSELECT {metric/revenues} FOR Previous({attribute/quarter} , 3)\n```\n\nFor differences between FOR Previous and FOR PreviousPeriod,\nsee [Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/).";
+//# sourceMappingURL=for-previous.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/for-previous.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-previous.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/for-previous.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,u6BA4BoK,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/for-previous.js

@@ -0,0 +1,30 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FOR Previous
+By default, the FOR Previous function refers to values from one time
+period ago. You can customize FOR Previous by adding a second parameter
+to the function.
+
+## Syntax
+
+\`\`\`
+SELECT … FOR Previous(…,…)
+SELECT metric FOR Previous(time_attribute)
+SELECT metric FOR Previous(time_attribute, #periods_ago)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT {metric/revenues} FOR Previous({attribute/quarter})
+\`\`\`
+
+You can customize FOR Previous() by adding a second parameter to the function. For
+example, you may want to return a revenue value from three quarters ago
+(see below).
+
+\`\`\`
+SELECT {metric/revenues} FOR Previous({attribute/quarter} , 3)
+\`\`\`
+
+For differences between FOR Previous and FOR PreviousPeriod,
+see [Functions For Referring to Past Time Periods](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/functions-for-referring-to-past-time-periods/).`;

package/esm/docs/en/docs/create-metrics/maql/time/functions-for-referring-to-past-time-periods.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Functions For Referring to Past Time Periods\nThe following MAQL functions allow you to create metrics showing a time\nover time comparison (for example, month over month, or quarter over\nquarter) of past time periods:\n\n-   [FOR Previous](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-previous/)\n-   [FOR PreviousPeriod](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-previous-period/)\n\n## Differences Between FOR Previous and FOR PreviousPeriod\n\nThe difference between the Previous( ) and PreviousPeriod( ) functions\nbecomes clear when the date attribute in a visualization is more granular than the\ndate attribute specified within the function's parentheses.\n\nFOR Previous( ) strictly follows the date attribute specified by the\nmetric author within the parentheses of the function.\n\nOn the other hand, FOR PreviousPeriod( ) adapts to the context of the\nvisualization. Regardless of the date attribute specified by the metric, the PreviousPeriod( ) function takes on the date attribute of the smallest granularity in the visualization.\n\nIn the following example, even though the metric in the final column has\nbeen defined as `FOR PreviousPeriod(quarter)`, the function returns\nvalues from the previous *month*, as month is the most granular date\nattribute in this visualization.\n\nThe Previous( ) function strictly follows the date attribute specified within the function's parentheses. PreviousPeriod ( ) takes on the most granular date attribute that is contained within the visualization.\n\n![PreviousPeriod](https://www.gooddata.com/developers/cloud-native/doc/maql/for-previous-period.png)\n\nEven if PreviousPeriod( ) automatically takes on the granularity of the\nsmallest date attribute in a visualization, it is still important to specify a\ndate attribute within the PreviousPeriod( ) function as a way of\nspecifying the date dimension of interest. This is because workspaces\noften have multiple date dimensions, such as Date(Lead Created),\nDate(MQL Qualified), or Date(Snapshot).";
+//# sourceMappingURL=functions-for-referring-to-past-time-periods.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time/functions-for-referring-to-past-time-periods.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"functions-for-referring-to-past-time-periods.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time/functions-for-referring-to-past-time-periods.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,+jEAkCoB,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time/functions-for-referring-to-past-time-periods.js

@@ -0,0 +1,36 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# Functions For Referring to Past Time Periods
+The following MAQL functions allow you to create metrics showing a time
+over time comparison (for example, month over month, or quarter over
+quarter) of past time periods:
+
+-   [FOR Previous](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-previous/)
+-   [FOR PreviousPeriod](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/time/for-previous-period/)
+
+## Differences Between FOR Previous and FOR PreviousPeriod
+
+The difference between the Previous( ) and PreviousPeriod( ) functions
+becomes clear when the date attribute in a visualization is more granular than the
+date attribute specified within the function's parentheses.
+
+FOR Previous( ) strictly follows the date attribute specified by the
+metric author within the parentheses of the function.
+
+On the other hand, FOR PreviousPeriod( ) adapts to the context of the
+visualization. Regardless of the date attribute specified by the metric, the PreviousPeriod( ) function takes on the date attribute of the smallest granularity in the visualization.
+
+In the following example, even though the metric in the final column has
+been defined as \`FOR PreviousPeriod(quarter)\`, the function returns
+values from the previous *month*, as month is the most granular date
+attribute in this visualization.
+
+The Previous( ) function strictly follows the date attribute specified within the function's parentheses. PreviousPeriod ( ) takes on the most granular date attribute that is contained within the visualization.
+
+![PreviousPeriod](https://www.gooddata.com/developers/cloud-native/doc/maql/for-previous-period.png)
+
+Even if PreviousPeriod( ) automatically takes on the granularity of the
+smallest date attribute in a visualization, it is still important to specify a
+date attribute within the PreviousPeriod( ) function as a way of
+specifying the date dimension of interest. This is because workspaces
+often have multiple date dimensions, such as Date(Lead Created),
+Date(MQL Qualified), or Date(Snapshot).`;

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-add.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# DATETIME_ADD\nThe `DATETIME_ADD` function adds a specified amount of intervals based on the granularity. \n\n## Syntax\n\n```\nSELECT \u2026 WHERE DATETIME_ADD(time_attribute, amount) >= time_attribute\nSELECT \u2026 WHERE DATETIME_ADD(time_attribute, granularity, amount) >= time_attribute\n```\n\n**Time attribute** can have the following formats:\n- Timestamp: ` {label/date.day}`\n- Date and time macro: `THIS(DAY)`\n- Strings: `\"2022\"` \n\nThe strings must be in the following formats: \n\n`\"YYYY-MM-DD HH24:MI\"` for minutes, `\"YYYY-MM-DD HH24\"` for hours, `\"YYYY-MM-DD\"` for days, `\"YYYY-MM\"` for months, `\"YYYY-WW\"` for weeks, and `\"YYYY\"` for years.\n\n**Amount** is an integer and specifies the amount of intervals of the given granularity.\n\n**Granularity** can be one of the following:\n* `MINUTE`\n* `HOUR`\n* `DAY`\n* `WEEK`\n* `MONTH`\n* `YEAR`\n\n* If the time attribute is a string, you must specify the granularity.\n* The granularity of the time attribute and the specified granularity in the function may be different.\n* If you do not specify the granularity, the granularity of the time attribute is used.\n\n## Examples\n\nReturn the number of loans that was returned in the last three days:\n\n```\nSELECT COUNT({label/l_loankey}) WHERE {label/l_returned.day} >= DATETIME_ADD({label/l_to.day}, -2)\n```\n\nReturn the number of loans from the 20th week of 2022:\n\n```\nSELECT COUNT({label/l_loankey}) WHERE {label/l_from.day} >= DATETIME_ADD(\"2022-01\", WEEK, 19) \n```\n\nReturn the sum of the shipping prices in the 7 days before the last returned loan.\n\n```\nSELECT SUM({fact/l_shippingprice}) WHERE {label/l_returned.day} >= DATETIME_ADD(MAX({label/l_returned.day}, {dataset/loan}), -7) \n```";
+//# sourceMappingURL=datetime-add.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-add.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"datetime-add.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-add.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,gtDAmDb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-add.js

@@ -0,0 +1,53 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# DATETIME_ADD
+The \`DATETIME_ADD\` function adds a specified amount of intervals based on the granularity. 
+
+## Syntax
+
+\`\`\`
+SELECT … WHERE DATETIME_ADD(time_attribute, amount) >= time_attribute
+SELECT … WHERE DATETIME_ADD(time_attribute, granularity, amount) >= time_attribute
+\`\`\`
+
+**Time attribute** can have the following formats:
+- Timestamp: \` {label/date.day}\`
+- Date and time macro: \`THIS(DAY)\`
+- Strings: \`"2022"\` 
+
+The strings must be in the following formats: 
+
+\`"YYYY-MM-DD HH24:MI"\` for minutes, \`"YYYY-MM-DD HH24"\` for hours, \`"YYYY-MM-DD"\` for days, \`"YYYY-MM"\` for months, \`"YYYY-WW"\` for weeks, and \`"YYYY"\` for years.
+
+**Amount** is an integer and specifies the amount of intervals of the given granularity.
+
+**Granularity** can be one of the following:
+* \`MINUTE\`
+* \`HOUR\`
+* \`DAY\`
+* \`WEEK\`
+* \`MONTH\`
+* \`YEAR\`
+
+* If the time attribute is a string, you must specify the granularity.
+* The granularity of the time attribute and the specified granularity in the function may be different.
+* If you do not specify the granularity, the granularity of the time attribute is used.
+
+## Examples
+
+Return the number of loans that was returned in the last three days:
+
+\`\`\`
+SELECT COUNT({label/l_loankey}) WHERE {label/l_returned.day} >= DATETIME_ADD({label/l_to.day}, -2)
+\`\`\`
+
+Return the number of loans from the 20th week of 2022:
+
+\`\`\`
+SELECT COUNT({label/l_loankey}) WHERE {label/l_from.day} >= DATETIME_ADD("2022-01", WEEK, 19) 
+\`\`\`
+
+Return the sum of the shipping prices in the 7 days before the last returned loan.
+
+\`\`\`
+SELECT SUM({fact/l_shippingprice}) WHERE {label/l_returned.day} >= DATETIME_ADD(MAX({label/l_returned.day}, {dataset/loan}), -7) 
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-diff.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# DATETIME_DIFF\nThe `DATETIME_DIFF` function calculates the difference between two timestamps or dates. The resulting number is the difference between the two specified timestamps/dates based on the granularity. \n\nThe function can be used, for example, to calculate the duration of your business processes.\n\n## Syntax\n\n```\nSELECT DATETIME_DIFF(time_attribute1, time_attribute2)\nSELECT DATETIME_DIFF(time_attribute1, time_attribute2, granularity)\nSELECT \u2026 WHERE DATETIME_DIFF(time_attribute1, time_attribute2) > 5\n```\n**Time attributes** can have the following formats:\n- Timestamp: ` {label/date.day}`\n- Date and time macro: `THIS(DAY)`\n- Strings: `\"2022\"` \n\n* The strings must be in the following formats: `\"YYYY-MM-DD HH24:MI\"` for minutes, `\"YYYY-MM-DD HH24\"` for hours, `\"YYYY-MM-DD\"` for days, `\"YYYY-MM\"` for months, `\"YYYY-WW\"` for weeks, and `\"YYYY\"` for years..\n* Use max one string as time attribute.\n* Strings must have the same granularity as the second time attribute.\n\n\n**Granularity** is optional and can be one of the following:\n* `MINUTE`\n* `HOUR`\n* `DAY`\n* `WEEK`\n* `MONTH`\n* `YEAR`\n\n* If the time attribute is in the `date` format, you cannot use the `MINUTE` or `HOUR` granularity.\n* If you do not specify the granularity, the greater granularity of the two date attributes is used.\n* If you specify the granularity, the two attributes must have the same or lower granularity.\n\n\n## Examples\n\nTo count the difference between two dates without specifying the granularity (the granularity is taken from the attributes):\n\n```\nSELECT DATETIME_DIFF({label/l_from.day}, {label/l_to.day})\n```\n\nDifference in days between two time attributes with hour granularity:\n\n```\nSELECT DATETIME_DIFF({label/l_from.hour}, {label/l_to.hour}, DAY)\n```\n\nFilter data where the duration is greater than the specified amount:\n\n```\nSELECT COUNT({dataset/item}) WHERE DATETIME_DIFF({label/i_decommisioned.day}, THIS(DAY)) > 10\n```";
+//# sourceMappingURL=datetime-diff.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-diff.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"datetime-diff.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-diff.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,g9DAqDb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/time-arithmetics/datetime-diff.js

@@ -0,0 +1,55 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# DATETIME_DIFF
+The \`DATETIME_DIFF\` function calculates the difference between two timestamps or dates. The resulting number is the difference between the two specified timestamps/dates based on the granularity. 
+
+The function can be used, for example, to calculate the duration of your business processes.
+
+## Syntax
+
+\`\`\`
+SELECT DATETIME_DIFF(time_attribute1, time_attribute2)
+SELECT DATETIME_DIFF(time_attribute1, time_attribute2, granularity)
+SELECT … WHERE DATETIME_DIFF(time_attribute1, time_attribute2) > 5
+\`\`\`
+**Time attributes** can have the following formats:
+- Timestamp: \` {label/date.day}\`
+- Date and time macro: \`THIS(DAY)\`
+- Strings: \`"2022"\` 
+
+* The strings must be in the following formats: \`"YYYY-MM-DD HH24:MI"\` for minutes, \`"YYYY-MM-DD HH24"\` for hours, \`"YYYY-MM-DD"\` for days, \`"YYYY-MM"\` for months, \`"YYYY-WW"\` for weeks, and \`"YYYY"\` for years..
+* Use max one string as time attribute.
+* Strings must have the same granularity as the second time attribute.
+
+
+**Granularity** is optional and can be one of the following:
+* \`MINUTE\`
+* \`HOUR\`
+* \`DAY\`
+* \`WEEK\`
+* \`MONTH\`
+* \`YEAR\`
+
+* If the time attribute is in the \`date\` format, you cannot use the \`MINUTE\` or \`HOUR\` granularity.
+* If you do not specify the granularity, the greater granularity of the two date attributes is used.
+* If you specify the granularity, the two attributes must have the same or lower granularity.
+
+
+## Examples
+
+To count the difference between two dates without specifying the granularity (the granularity is taken from the attributes):
+
+\`\`\`
+SELECT DATETIME_DIFF({label/l_from.day}, {label/l_to.day})
+\`\`\`
+
+Difference in days between two time attributes with hour granularity:
+
+\`\`\`
+SELECT DATETIME_DIFF({label/l_from.hour}, {label/l_to.hour}, DAY)
+\`\`\`
+
+Filter data where the duration is greater than the specified amount:
+
+\`\`\`
+SELECT COUNT({dataset/item}) WHERE DATETIME_DIFF({label/i_decommisioned.day}, THIS(DAY)) > 10
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/time-macros.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Time Macros\nTime macros or time macro functions are \"floating\" references to day, month, week, and other date-related attribute values, relative to the present.\nMAQL supports the following time macro functions:\n\n- THIS\n- PREVIOUS\n- NEXT\n\nThese macros are useful for creating visualizations that relate to data from \"today\", \"yesterday\", \"this month\", \"next year\" etc.\n\n### \"THIS\" Macro\n\nTHIS macro references the current value of the specified date granularity.\n\nIn the following example, THIS macro is used with the day granularity, effectively meaning *this day*, or \"today\":\n\n```\nSELECT {metric/payment} WHERE {attribute/date} = THIS(DAY)\n```\n\nIf the date granularity of the macro changes, so does the meaning of THIS. You can use following time macro granularities:\n\n- DAY\n- MONTH\n- QUARTER\n- YEAR\n- WEEK\n- WEEKOFYEAR\n- MONTHOFYEAR\n- QUARTEROFYEAR\n- DAYOFMONTH\n- DAYOFWEEK\n- DAYOFYEAR\n\nOther date granularities supported by GoodData platform (such as HOUR, MINUTE etc.) are currently not available for time macros.\n\n### Referencing past or future dates\n\nOptionally you can specify second parameter of THIS macro to reference future\nor previous time periods. For example,\n\n```\nSELECT {metric/payment} WHERE {attribute/month} = THIS(Month, -2)\n```\n\ncomputes payments of the month two months ago.\n\nTo illustrate more, suppose the current date is **November 3, 2014**.\nThen following table summarizes values of THIS macro for various combinations of granularities (in rows) and period shifts (columns).\nNote that `THIS(<granularity>, 0)` is equivalent to `THIS(<granularity>)`.\n\n|  | 0 | 2 | -1 |\n| - | - | - | - |\n| Day | 11/3/2014 | 11/5/2014 |  11/2/2014 |\n| DayOfWeek | 1 (Monday) | 3 (Wednesday) | 0 (Sunday) |\n| MonthOfYear | 11 (November) | 1 (January) | 10 (October) |\n| QuarterOfYear | Q4 | Q2 | Q3 |\n| Quarter | Q4/2014 | Q2/2015 | Q3/2014 |\n\n\nNotice that if the date granularity is periodic, such as QuarterOfYear (Q1, Q2,\nQ3, Q4) or MonthOfYear (January, February, March, etc), the resulting value might roll over to the next or\nbackward to the previous period.\n\n### \"PREVIOUS\" and \"NEXT\" Macros\n\nFor convenience MAQL also supports shortcuts for the other two most common relative periods: previous and next.\n\n- `PREVIOUS(<granularity>)` is equivalent to `THIS(<granularity>, -1)`\n- `NEXT(<granularity>)` is equivalent to `THIS(<granularity>, 1)`\n- `PREVIOUS(<granularity>, <shift>)` is equivalent to `THIS(<granularity>, - <shift>)`\n- `NEXT(<granularity>, <shift>)` is equivalent to `THIS(<granularity>, shift>)`\n\nExample:\n\n```\nSELECT {metric/payment} WHERE {attribute/month} = PREVIOUS(Month)\n```";
+//# sourceMappingURL=time-macros.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/time-macros.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"time-macros.d.ts","sourceRoot":"","sources":["../../../../../../src/docs/en/docs/create-metrics/maql/time-macros.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,wpFA6Eb,CAAC"}