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

package/esm/docs/en/docs/create-metrics/maql/aggregation/avg.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# AVG\nThe AVG function returns the average value of all numbers in the set (e.g., Salary paid). Null values are ignored.\n\n## Syntax\n\n```\nSELECT AVG(\u2026)\nSELECT AVG(fact)\n```\n\n## Examples\n\nThe metric AVG of Payment is computed by adding all payment transactions\ntogether and dividing by the number of payment transactions:\n\n```\nSELECT AVG({fact/payment})\n```";
+//# sourceMappingURL=avg.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/avg.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/avg.js

@@ -0,0 +1,19 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# AVG
+The AVG function returns the average value of all numbers in the set (e.g., Salary paid). Null values are ignored.
+
+## Syntax
+
+\`\`\`
+SELECT AVG(…)
+SELECT AVG(fact)
+\`\`\`
+
+## Examples
+
+The metric AVG of Payment is computed by adding all payment transactions
+together and dividing by the number of payment transactions:
+
+\`\`\`
+SELECT AVG({fact/payment})
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/aggregation/count.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# COUNT\nUse COUNT to return the number of unique values for an attribute or the number of dataset records.\n - For large amounts of data where complete accuracy is not a priority, consider using APPROXIMATE_COUNT to increase the processing speed. APPROXIMATE_COUNT is available only for workspaces that use [Vertica](https://www.gooddata.com/developers/cloud-native/doc/hosted/connect-data/create-data-sources/vertica/) as a data source.\n\n## Syntax\n\nCOUNT uses the following syntax:\n\n\n  |Form       |        Syntax            |                                           Example|\n  |------------------ |------------------------------------------------------------| --------------------------------------------|\n  |single parameter   |`SELECT COUNT(attribute)`                                    |`SELECT COUNT({attribute/order_id})`|\n  |two parameters     |`SELECT COUNT(attribute, primary_key)`                       |`SELECT COUNT({attribute/order_id}, {attribute/campaign_id})`|\n  |     |`SELECT COUNT(attribute, dataset)`                       |`SELECT COUNT({attribute/order_id}, {SELECT COUNT({attribute/order_id}, {dataset/campaigns})`|\n  |with USING         |`SELECT COUNT(attribute) USING primary_key`   |`SELECT COUNT({attribute/order_id}) USING {attribute/campaign_id}`|\n  |         |`SELECT COUNT(attribute) USING dataset`   |`SELECT COUNT({attribute/order_id}) USING {dataset/campaigns}`|\n\n\n### Single-Parameter Version\n\nThe single-parameter version of COUNT dynamically gets the context of\nwhere to count from the visualization it is used in.\n\n### Two-Parameter Version\n\nIn the two-parameter version, the context where to count the attribute\nis determined explicitly by the second parameter - the primary key of\nthe dataset.\n\nThe primary key is connection point between datasets. It connects the\nCOUNT function's first parameter to the dataset in which the count is\nto take place.\n\n### Count of Dataset Records \nYou can use a dataset identifier as the first argument of COUNT as well.  The behavior of COUNT slightly changes depending on whether a primary key is defined in the dataset. \n\nIf there is a primary key, the number of unique values of the primary key attribute is returned. \n\nIf there is no primary key attribute, the count of all records (including possible duplicates) is returned.\n\n|Form       |        Syntax            |                                           Example|\n  |------------------ |------------------------------------------------------------| --------------------------------------------|\n  |single parameter   |`SELECT COUNT(dataset)`                                    |`SELECT COUNT({dataset/order_lines})`|\n\n\n### Specifying COUNT Context Resolution with USING\n\nIn a metric, USING provides a hint for which context should be used.\nThe context for the computation of COUNT may be ambiguous if there are\nmultiple fact datasets in your logical data model that relate to a counted attribute. \n\nThe following image shows a model with the fact datasets `Purchases` and `Sales` and\nhas both datasets connected to the `Store ID` and `Product ID` attributes.\n\n![model for count example](https://www.gooddata.com/developers/cloud-native/doc/maql/count-ldm-using.png)\n\nTo create a metric that resolves with a specific context, you can specify USING in your metric like in the following \nexample: `SELECT COUNT({label/inventory.productid}) USING {label/purchases.purchaseid}`. \n\nWith this example, the visualization will show the number of uniquely purchased products per store \nbecause the attribute `Purchase ID` from the `Purchases` dataset is in the USING clause.\n\nWith the example model, if you build a visualization to display the count of products per store with \n`SELECT COUNT({label/inventory.productid})` and slice it by Store without specifying USING, it is ambiguous whether \nthe visualization is displaying the number of unique products that have been purchased by store or the number of unique \nproducts that have been sold by the store.\n\nThe attribute in the USING clause can be any attribute which uniquely determines the correct context. For example, you\ncan also use an attribute from the `Purchase Date` dataset in the USING clause. This uses the `Purchases` dataset as \nthe context because the `Sales` dataset has no relationships to `Purchase Date`: \n`SELECT COUNT({label/inventory.productid}) USING {label/purchasedate.year}`";
+//# sourceMappingURL=count.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/count.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/count.js

@@ -0,0 +1,72 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# COUNT
+Use COUNT to return the number of unique values for an attribute or the number of dataset records.
+ - For large amounts of data where complete accuracy is not a priority, consider using APPROXIMATE_COUNT to increase the processing speed. APPROXIMATE_COUNT is available only for workspaces that use [Vertica](https://www.gooddata.com/developers/cloud-native/doc/hosted/connect-data/create-data-sources/vertica/) as a data source.
+
+## Syntax
+
+COUNT uses the following syntax:
+
+
+  |Form       |        Syntax            |                                           Example|
+  |------------------ |------------------------------------------------------------| --------------------------------------------|
+  |single parameter   |\`SELECT COUNT(attribute)\`                                    |\`SELECT COUNT({attribute/order_id})\`|
+  |two parameters     |\`SELECT COUNT(attribute, primary_key)\`                       |\`SELECT COUNT({attribute/order_id}, {attribute/campaign_id})\`|
+  |     |\`SELECT COUNT(attribute, dataset)\`                       |\`SELECT COUNT({attribute/order_id}, {SELECT COUNT({attribute/order_id}, {dataset/campaigns})\`|
+  |with USING         |\`SELECT COUNT(attribute) USING primary_key\`   |\`SELECT COUNT({attribute/order_id}) USING {attribute/campaign_id}\`|
+  |         |\`SELECT COUNT(attribute) USING dataset\`   |\`SELECT COUNT({attribute/order_id}) USING {dataset/campaigns}\`|
+
+
+### Single-Parameter Version
+
+The single-parameter version of COUNT dynamically gets the context of
+where to count from the visualization it is used in.
+
+### Two-Parameter Version
+
+In the two-parameter version, the context where to count the attribute
+is determined explicitly by the second parameter - the primary key of
+the dataset.
+
+The primary key is connection point between datasets. It connects the
+COUNT function's first parameter to the dataset in which the count is
+to take place.
+
+### Count of Dataset Records 
+You can use a dataset identifier as the first argument of COUNT as well.  The behavior of COUNT slightly changes depending on whether a primary key is defined in the dataset. 
+
+If there is a primary key, the number of unique values of the primary key attribute is returned. 
+
+If there is no primary key attribute, the count of all records (including possible duplicates) is returned.
+
+|Form       |        Syntax            |                                           Example|
+  |------------------ |------------------------------------------------------------| --------------------------------------------|
+  |single parameter   |\`SELECT COUNT(dataset)\`                                    |\`SELECT COUNT({dataset/order_lines})\`|
+
+
+### Specifying COUNT Context Resolution with USING
+
+In a metric, USING provides a hint for which context should be used.
+The context for the computation of COUNT may be ambiguous if there are
+multiple fact datasets in your logical data model that relate to a counted attribute. 
+
+The following image shows a model with the fact datasets \`Purchases\` and \`Sales\` and
+has both datasets connected to the \`Store ID\` and \`Product ID\` attributes.
+
+![model for count example](https://www.gooddata.com/developers/cloud-native/doc/maql/count-ldm-using.png)
+
+To create a metric that resolves with a specific context, you can specify USING in your metric like in the following 
+example: \`SELECT COUNT({label/inventory.productid}) USING {label/purchases.purchaseid}\`. 
+
+With this example, the visualization will show the number of uniquely purchased products per store 
+because the attribute \`Purchase ID\` from the \`Purchases\` dataset is in the USING clause.
+
+With the example model, if you build a visualization to display the count of products per store with 
+\`SELECT COUNT({label/inventory.productid})\` and slice it by Store without specifying USING, it is ambiguous whether 
+the visualization is displaying the number of unique products that have been purchased by store or the number of unique 
+products that have been sold by the store.
+
+The attribute in the USING clause can be any attribute which uniquely determines the correct context. For example, you
+can also use an attribute from the \`Purchase Date\` dataset in the USING clause. This uses the \`Purchases\` dataset as 
+the context because the \`Sales\` dataset has no relationships to \`Purchase Date\`: 
+\`SELECT COUNT({label/inventory.productid}) USING {label/purchasedate.year}\``;

package/esm/docs/en/docs/create-metrics/maql/aggregation/first.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FIRST_VALUE\nThe `FIRST_VALUE` function returns the first value of a sequence. \n\nThe function is typically used to determine the first value of semi-additive fact when used together with sum aggregation.\n\n\n## Syntax\n\n```\nSELECT FIRST_VALUE({numeric})\n      ORDER BY {attribute/label} [ASC|DESC]\n      [WITHIN (... | CURRENT)]\n\n```\n\nThe argument of the function is a metric or a subselect defining an aggregation.\n\n> If you use facts, make sure that the fact has only a single value defined for each `ORDER BY` attribute.\n\nThe sequence is determined by the attribute in `ORDER BY`. The metric is broken down by the given attribute and the results are displayed in the ascending order by default.\n\n> To show the result in the descending order, use the DESC directive.\n>\n> `NULL` values are considered as the smallest values.\n\nIf the metric is broken down by other attributes, these attributes define a partition in which the first value is being determined. \n\nUse the `WITHIN` keyword to avoid this behavior and use the common first value for all the values of the given attributes.\n\n## Examples\n\nThe first value of a sum of semi-additive snapshots from a dataset with daily snapshots. \n\nExample of such a semi-additive snapshot can be **account balance** (values of multiple accounts can be summed up but not their daily snapshots).\n\n```\nSELECT FIRST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}\n```\n\nFor a more complex example, see also [LAST_VALUE](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/aggregation/last/).";
+//# sourceMappingURL=first.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/first.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/first.js

@@ -0,0 +1,41 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FIRST_VALUE
+The \`FIRST_VALUE\` function returns the first value of a sequence. 
+
+The function is typically used to determine the first value of semi-additive fact when used together with sum aggregation.
+
+
+## Syntax
+
+\`\`\`
+SELECT FIRST_VALUE({numeric})
+      ORDER BY {attribute/label} [ASC|DESC]
+      [WITHIN (... | CURRENT)]
+
+\`\`\`
+
+The argument of the function is a metric or a subselect defining an aggregation.
+
+> If you use facts, make sure that the fact has only a single value defined for each \`ORDER BY\` attribute.
+
+The sequence is determined by the attribute in \`ORDER BY\`. The metric is broken down by the given attribute and the results are displayed in the ascending order by default.
+
+> To show the result in the descending order, use the DESC directive.
+>
+> \`NULL\` values are considered as the smallest values.
+
+If the metric is broken down by other attributes, these attributes define a partition in which the first value is being determined. 
+
+Use the \`WITHIN\` keyword to avoid this behavior and use the common first value for all the values of the given attributes.
+
+## Examples
+
+The first value of a sum of semi-additive snapshots from a dataset with daily snapshots. 
+
+Example of such a semi-additive snapshot can be **account balance** (values of multiple accounts can be summed up but not their daily snapshots).
+
+\`\`\`
+SELECT FIRST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}
+\`\`\`
+
+For a more complex example, see also [LAST_VALUE](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/aggregation/last/).`;

package/esm/docs/en/docs/create-metrics/maql/aggregation/last.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# LAST_VALUE\nThe `LAST_VALUE` function returns the last value of a sequence. \n\nThe function is typically used to determine the last value of semi-additive fact when used together with sum aggregation.\n\n## Syntax\n\n```\nSELECT LAST_VALUE({numeric})\n      ORDER BY {attribute/label} [ASC|DESC]\n      [WITHIN (... | CURRENT)]\n\n```\n\nThe argument of the function is a metric or a subselect defining an aggregation.\n\n> If you use facts, make sure that the fact has only a single value defined for each `ORDER BY` attribute.\n\nThe sequence is determined by the attribute in `ORDER BY`. The metric is broken down by the given attribute and the results are displayed in the ascending order by default.\n\n> To show the result in the descending order, use the DESC directive.\n>\n> `NULL` values are considered as the smallest values.\n\nIf the metric is broken down by other attributes, these attributes define a partition in which the last value is being determined. \n\nUse the `WITHIN` keyword to avoid this behavior and use the common last value for all the values of the given attributes.\n\n> See also [FIRST_VALUE](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/aggregation/first/) for additional information.\n\n## Examples\n\nThe last value of a sum of semi-additive snapshots from a dataset with daily snapshots. \n\nExample of such a semi-additive snapshot can be **account balance** (values of multiple accounts can be summed up but not their daily snapshots).\n\n```\nSELECT LAST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}\n```\n\nTo show how much your account balance has grown since the beginning of the year, you can use the following metrics and syntax:\n\n| Metric | Syntax |\n| --- | --- |\n| last_day_value | `SELECT LAST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}` |\n| first_day_value_in_year | `SELECT FIRST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day} WITHIN ({attribute/date.year})` |\n| growth_to_date | `SELECT {metric/last_day_value}/{metric/first_day_value_in_year}-1` |\n\n</br>\nThe result may look as follows:\n\n| Date - Month/Year| last_day_value | first_day_value_in_year | growth_to_date |\n| --- | --- | --- | --- |\n|2022-01|1,000|1,000|0%|\n|2022-02|2,000|1,000|+100%|\n|2022-03|3,000|1,000|+200%|\n|2022-04|4,000|1,000|+300%|\n|2022-05|5,000|1,000|+400%|\n|2022-06|6,000|1,000|+500%|\n|2022-07|7,000|1,000|+600%|\n|2022-08|8,000|1,000|+700%|\n|2022-09|9,000|1,000|+800%|\n|2022-10|10,000|1,000|+900%|\n|2022-11|11,000|1,000|+1000%|\n|2022-12|12,000|1,000|+1100%|\n|2023-01|13,000|12,000|+8.3%|\n|2023-02|14,000|12,000|+16.7%|\n|2023-03|15,000|12,000|+25%|";
+//# sourceMappingURL=last.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/last.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/last.js

@@ -0,0 +1,69 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# LAST_VALUE
+The \`LAST_VALUE\` function returns the last value of a sequence. 
+
+The function is typically used to determine the last value of semi-additive fact when used together with sum aggregation.
+
+## Syntax
+
+\`\`\`
+SELECT LAST_VALUE({numeric})
+      ORDER BY {attribute/label} [ASC|DESC]
+      [WITHIN (... | CURRENT)]
+
+\`\`\`
+
+The argument of the function is a metric or a subselect defining an aggregation.
+
+> If you use facts, make sure that the fact has only a single value defined for each \`ORDER BY\` attribute.
+
+The sequence is determined by the attribute in \`ORDER BY\`. The metric is broken down by the given attribute and the results are displayed in the ascending order by default.
+
+> To show the result in the descending order, use the DESC directive.
+>
+> \`NULL\` values are considered as the smallest values.
+
+If the metric is broken down by other attributes, these attributes define a partition in which the last value is being determined. 
+
+Use the \`WITHIN\` keyword to avoid this behavior and use the common last value for all the values of the given attributes.
+
+> See also [FIRST_VALUE](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/aggregation/first/) for additional information.
+
+## Examples
+
+The last value of a sum of semi-additive snapshots from a dataset with daily snapshots. 
+
+Example of such a semi-additive snapshot can be **account balance** (values of multiple accounts can be summed up but not their daily snapshots).
+
+\`\`\`
+SELECT LAST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}
+\`\`\`
+
+To show how much your account balance has grown since the beginning of the year, you can use the following metrics and syntax:
+
+| Metric | Syntax |
+| --- | --- |
+| last_day_value | \`SELECT LAST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day}\` |
+| first_day_value_in_year | \`SELECT FIRST_VALUE(SUM({fact/snapshot_value})) ORDER BY {attribute/date.day} WITHIN ({attribute/date.year})\` |
+| growth_to_date | \`SELECT {metric/last_day_value}/{metric/first_day_value_in_year}-1\` |
+
+</br>
+The result may look as follows:
+
+| Date - Month/Year| last_day_value | first_day_value_in_year | growth_to_date |
+| --- | --- | --- | --- |
+|2022-01|1,000|1,000|0%|
+|2022-02|2,000|1,000|+100%|
+|2022-03|3,000|1,000|+200%|
+|2022-04|4,000|1,000|+300%|
+|2022-05|5,000|1,000|+400%|
+|2022-06|6,000|1,000|+500%|
+|2022-07|7,000|1,000|+600%|
+|2022-08|8,000|1,000|+700%|
+|2022-09|9,000|1,000|+800%|
+|2022-10|10,000|1,000|+900%|
+|2022-11|11,000|1,000|+1000%|
+|2022-12|12,000|1,000|+1100%|
+|2023-01|13,000|12,000|+8.3%|
+|2023-02|14,000|12,000|+16.7%|
+|2023-03|15,000|12,000|+25%|`;

package/esm/docs/en/docs/create-metrics/maql/aggregation/max.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# MAX\n## Metrics\n\nThe MAX function returns the maximum value of all numbers in the set\n(e.g., Salary Paid).\n\n### Syntax\n\n```\nSELECT MAX(\u2026)\nSELECT MAX(fact)\n```\n\n### Example\n\nThe MAX of the Store Sales fact is the highest sales transaction value on record:\n\n```\nSELECT MAX({fact/sales})\n```\n\n## Attributes\n\nThe MAX function can be also used to determine the maximum value of attributes with non-numeric data types (e.g. string or date attributes). \n\nThe results cannot be displayed in insights directly, but they can be used in conditional filtering, for example, to filter the last snapshot.\n\n### Syntax\n\n```\nSELECT MAX(attribute)\nSELECT MAX(attribute,primary_key)\nSELECT MAX(attribute,dataset)\nSELECT MAX(attribute) USING attribute\n```\n\nIf the attribute is referenced from multiple fact datasets, use two parameters in the MAX function. \n\nThe context where to search for maximum value of the attribute is determined by the second parameter - the primary key of the dataset or the dataset identifier. \n\nFor date attributes, use the second attribute or the USING keyword.\n\n### Examples\n\nThe sum of semi-additive snapshot values for the last of the daily snapshots.  \n\n```\nSELECT SUM({fact/snapshot_value}) \nWHERE {attribute/snapshot_date.day} =\n      (SELECT MAX({attribute/snapshot_date.day},{dataset/fact_dataset}))\n```\n\nIf the metric is broken down by other attributes and displayed as a table, the maximum value can be different for each row. \n\nTo use the maximum date for all rows, add `BY ALL OTHER` to the syntax.\n```\nSELECT SUM({fact/snapshot_value}) \nWHERE {attribute/snapshot_date.day} =\n      (SELECT MAX({attribute/snapshot_date.day},{dataset/fact_dataset}) BY ALL OTHER)\n```";
+//# sourceMappingURL=max.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/max.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/max.js

@@ -0,0 +1,61 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# MAX
+## Metrics
+
+The MAX function returns the maximum value of all numbers in the set
+(e.g., Salary Paid).
+
+### Syntax
+
+\`\`\`
+SELECT MAX(…)
+SELECT MAX(fact)
+\`\`\`
+
+### Example
+
+The MAX of the Store Sales fact is the highest sales transaction value on record:
+
+\`\`\`
+SELECT MAX({fact/sales})
+\`\`\`
+
+## Attributes
+
+The MAX function can be also used to determine the maximum value of attributes with non-numeric data types (e.g. string or date attributes). 
+
+The results cannot be displayed in insights directly, but they can be used in conditional filtering, for example, to filter the last snapshot.
+
+### Syntax
+
+\`\`\`
+SELECT MAX(attribute)
+SELECT MAX(attribute,primary_key)
+SELECT MAX(attribute,dataset)
+SELECT MAX(attribute) USING attribute
+\`\`\`
+
+If the attribute is referenced from multiple fact datasets, use two parameters in the MAX function. 
+
+The context where to search for maximum value of the attribute is determined by the second parameter - the primary key of the dataset or the dataset identifier. 
+
+For date attributes, use the second attribute or the USING keyword.
+
+### Examples
+
+The sum of semi-additive snapshot values for the last of the daily snapshots.  
+
+\`\`\`
+SELECT SUM({fact/snapshot_value}) 
+WHERE {attribute/snapshot_date.day} =
+      (SELECT MAX({attribute/snapshot_date.day},{dataset/fact_dataset}))
+\`\`\`
+
+If the metric is broken down by other attributes and displayed as a table, the maximum value can be different for each row. 
+
+To use the maximum date for all rows, add \`BY ALL OTHER\` to the syntax.
+\`\`\`
+SELECT SUM({fact/snapshot_value}) 
+WHERE {attribute/snapshot_date.day} =
+      (SELECT MAX({attribute/snapshot_date.day},{dataset/fact_dataset}) BY ALL OTHER)
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/aggregation/median.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# MEDIAN\nThe MEDIAN function counts the statistical median - an order statistic\nthat gives the middle value of a sample. If the middle falls between two\nvalues, the function returns average of the two middle values. Null\nvalues are ignored.\n\nThe MEDIAN function is especially useful in cases where a small set of\noutliers could drastically skew the average if calculated as a mean.\n\n## Syntax\n\n```\nSELECT MEDIAN(\u2026)\nMEDIAN(fact)\nMEDIAN(metric)\nMEDIAN(metric_expression)\n```\n\n## Examples\n\n```\nSELECT MEDIAN({fact/cost}) BY ALL OTHER\nSELECT MEDIAN({metric/payment}) BY {attribute/customer}\n```";
+//# sourceMappingURL=median.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/median.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/median.js

@@ -0,0 +1,25 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# MEDIAN
+The MEDIAN function counts the statistical median - an order statistic
+that gives the middle value of a sample. If the middle falls between two
+values, the function returns average of the two middle values. Null
+values are ignored.
+
+The MEDIAN function is especially useful in cases where a small set of
+outliers could drastically skew the average if calculated as a mean.
+
+## Syntax
+
+\`\`\`
+SELECT MEDIAN(…)
+MEDIAN(fact)
+MEDIAN(metric)
+MEDIAN(metric_expression)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT MEDIAN({fact/cost}) BY ALL OTHER
+SELECT MEDIAN({metric/payment}) BY {attribute/customer}
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/aggregation/min.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# MIN\n## Metrics\n\nThe MIN function returns the minimum value of all numbers in the set\n(e.g., Salary Paid).\n\n### Syntax\n\n```\nSELECT MIN(\u2026)\nSELECT MIN(fact)\n```\n\n### Example\n\nThe MIN of the *Opportunity Amount* fact is the lowest opportunity\namount value on record:\n\n```\nSELECT MIN({fact/opportunity_amount})\n```\n\n## Attributes\n\nThe MIN function can be also used to determine the minimum value of attributes with non-numeric data types (e.g. string or date attributes). \n\nThe results cannot be displayed in insights directly, but they can be used in conditional filtering, for example, to filter the last snapshot.\n\n### Syntax\n\n```\nSELECT MIN(attribute)\nSELECT MIN(attribute,primary_key)\nSELECT MIN(attribute,dataset)\nSELECT MIN(attribute) USING attribute\n```\n\nIf the attribute is referenced from multiple fact datasets, use two parameters in the MIN function. \n\nThe context where to search for minimum value of the attribute is determined by the second parameter - the primary key of the dataset or the dataset identifier. \n\nFor date attributes, use the second attribute or the USING keyword.\n\n### Examples\n\nThe sum of semi-additive snapshot values for the first of the daily snapshots.  \n\n```\nSELECT SUM({fact/snapshot_value}) \nWHERE {attribute/snapshot_date.day} =\n      (SELECT MIN({attribute/snapshot_date.day},{dataset/fact_dataset}))\n```\n\n\nIf the metric is broken down by other attributes and displayed as a table, the minimum value can be different for each row. \n\nTo use the minimum date for all rows, add `BY ALL OTHER` to the syntax.\n```\nSELECT SUM({fact/snapshot_value}) \nWHERE {attribute/snapshot_date.day} =\n      (SELECT MIN({attribute/snapshot_date.day},{dataset/fact_dataset}) BY ALL OTHER)\n```";
+//# sourceMappingURL=min.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/min.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/min.js

@@ -0,0 +1,63 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# MIN
+## Metrics
+
+The MIN function returns the minimum value of all numbers in the set
+(e.g., Salary Paid).
+
+### Syntax
+
+\`\`\`
+SELECT MIN(…)
+SELECT MIN(fact)
+\`\`\`
+
+### Example
+
+The MIN of the *Opportunity Amount* fact is the lowest opportunity
+amount value on record:
+
+\`\`\`
+SELECT MIN({fact/opportunity_amount})
+\`\`\`
+
+## Attributes
+
+The MIN function can be also used to determine the minimum value of attributes with non-numeric data types (e.g. string or date attributes). 
+
+The results cannot be displayed in insights directly, but they can be used in conditional filtering, for example, to filter the last snapshot.
+
+### Syntax
+
+\`\`\`
+SELECT MIN(attribute)
+SELECT MIN(attribute,primary_key)
+SELECT MIN(attribute,dataset)
+SELECT MIN(attribute) USING attribute
+\`\`\`
+
+If the attribute is referenced from multiple fact datasets, use two parameters in the MIN function. 
+
+The context where to search for minimum value of the attribute is determined by the second parameter - the primary key of the dataset or the dataset identifier. 
+
+For date attributes, use the second attribute or the USING keyword.
+
+### Examples
+
+The sum of semi-additive snapshot values for the first of the daily snapshots.  
+
+\`\`\`
+SELECT SUM({fact/snapshot_value}) 
+WHERE {attribute/snapshot_date.day} =
+      (SELECT MIN({attribute/snapshot_date.day},{dataset/fact_dataset}))
+\`\`\`
+
+
+If the metric is broken down by other attributes and displayed as a table, the minimum value can be different for each row. 
+
+To use the minimum date for all rows, add \`BY ALL OTHER\` to the syntax.
+\`\`\`
+SELECT SUM({fact/snapshot_value}) 
+WHERE {attribute/snapshot_date.day} =
+      (SELECT MIN({attribute/snapshot_date.day},{dataset/fact_dataset}) BY ALL OTHER)
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/aggregation/sum.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# SUM\nThe SUM function returns a sum of all numbers in the set (e.g., Salary\nPaid).\n\n## Syntax\n\n```\nSELECT SUM(\u2026)\nSELECT SUM(fact)\n```\n\n## Examples\n\nThe metric defined by the SUM of the *Sales* fact would be computed by\nadding revenue earned from all individual sales transactions: \n\n```\nSELECT SUM({fact/sales})\n```";
+//# sourceMappingURL=sum.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/aggregation/sum.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/aggregation/sum.js

@@ -0,0 +1,20 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# SUM
+The SUM function returns a sum of all numbers in the set (e.g., Salary
+Paid).
+
+## Syntax
+
+\`\`\`
+SELECT SUM(…)
+SELECT SUM(fact)
+\`\`\`
+
+## Examples
+
+The metric defined by the SUM of the *Sales* fact would be computed by
+adding revenue earned from all individual sales transactions: 
+
+\`\`\`
+SELECT SUM({fact/sales})
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/conditionals/case.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# CASE\nCASE is a conditional statement that performs logical tests on a series\nof conditions and returns values when a condition is met. The CASE\nfunction returns a numeric result. You use CASE for complex conditional\nexpressions that contain two or more conditions.\n\nCASE is followed by WHEN/THEN keywords to specify the conditions, then\nby ELSE to specify the default return.\n\nIf no match is found, the default return expression (ELSE) is used. If\nthere is no default return and no values match, then `null` value is returned.\nAll CASE expressions conclude with the END keyword.\n\n## CASE and Multidimensionality\n\nBefore proceeding to the CASE syntax samples, as a user you have to\nunderstand that usage guidelines for CASE in the MAQL environment are based on multidimensionality. Understanding multidimensionality is crucial to\nensure your CASE metrics return correct results (see [MAQL and Multidimensionality](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/maql-and-multidimensionality/)).\n\n-   CASE does not work with the base data level.\n-   Instead, the condition is evaluated on the aggregation dimension.\n-   All WHENs are evaluated independently but all based on a single\n    dimension (the aggregation dimension mentioned in the previous\n    point).\n\nIn most common scenarios you should follow this rule:\n\n-   Always put the CASE statement inside (not outside) an aggregation (SUM) container.\n\nSee examples below.\n\n## CASE Syntax\n\nCASE can be used in the following two syntax forms:\n\n\n| Form             |  Syntax         | Example|\n|-----------------|------------------|--------------|\n| No aggregation   |  `SELECT CASE WHEN condition1 THEN outcome1, WHEN condition2 THEN outcome 2 ELSE outcome3 END`        |       `SELECT CASE WHEN {attribute/activity_type} IN (\"email\", \"meeting\") THEN 1, WHEN {attribute/activity_type} IN (\"phone_call\") THEN 2 ELSE 0 END`|\n|With aggregation   |`SELECT SUM (SELECT CASE WHEN condition1 THEN outcome1, WHEN condition2 THEN outcome2 ELSE outcome3 END)`  | `SELECT SUM (SELECT CASE WHEN {attribute/activity_type} IN (\"email\", \"meeting\") THEN {fact/amount} ELSE {fact/loss} END)` |\n\nUsing the aggregation container ensures that the CASE conditions are\ncomputed on the correct dimension and returns relevant results.\n\n## How to Use CASE Correctly\n\nAs noted above, we advise you to use CASE inside aggregation containers.\n\nHere is an example of incorrect use of CASE in the following logical\ndata model. For the sake brevity, only one CASE condition is used.\n\n![An example of incorrect use of CASE ](https://www.gooddata.com/developers/cloud-native/doc/maql/case.png)\n\nIf you want to slice the following metric with **Campaign Category**,\nthe visualization would not compute because the WHEN conditions are not\nrelated to visualization dimensionality:\n\n```\nSELECT CASE WHEN {fact/customer_state} IN (\"AR\", \"NY\") THEN SUM ({fact/price}) ELSE SUM({fact/price} * {fact/quantity}) END\n```\n\nOn the other hand, the same metric when sliced by attribute **Customer\nID** (instead of **Campaign Category**) is valid. That is because the\nslicing attribute (**Customer ID**) is directly related to the CASE\ncondition attribute (Customer State).\n\nIf you need to slice by unrelated attribute, put the CASE statement\ninside the SUM aggregation instead:\n\n```\nSELECT SUM(SELECT CASE WHEN {attribute/customer_state} IN (\"AR\", \"NY\") THEN {fact/price} ELSE {fact/price} * {fact/quantity} END)\n```";
+//# sourceMappingURL=case.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/conditionals/case.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/conditionals/case.js

@@ -0,0 +1,73 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# CASE
+CASE is a conditional statement that performs logical tests on a series
+of conditions and returns values when a condition is met. The CASE
+function returns a numeric result. You use CASE for complex conditional
+expressions that contain two or more conditions.
+
+CASE is followed by WHEN/THEN keywords to specify the conditions, then
+by ELSE to specify the default return.
+
+If no match is found, the default return expression (ELSE) is used. If
+there is no default return and no values match, then \`null\` value is returned.
+All CASE expressions conclude with the END keyword.
+
+## CASE and Multidimensionality
+
+Before proceeding to the CASE syntax samples, as a user you have to
+understand that usage guidelines for CASE in the MAQL environment are based on multidimensionality. Understanding multidimensionality is crucial to
+ensure your CASE metrics return correct results (see [MAQL and Multidimensionality](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/maql-and-multidimensionality/)).
+
+-   CASE does not work with the base data level.
+-   Instead, the condition is evaluated on the aggregation dimension.
+-   All WHENs are evaluated independently but all based on a single
+    dimension (the aggregation dimension mentioned in the previous
+    point).
+
+In most common scenarios you should follow this rule:
+
+-   Always put the CASE statement inside (not outside) an aggregation (SUM) container.
+
+See examples below.
+
+## CASE Syntax
+
+CASE can be used in the following two syntax forms:
+
+
+| Form             |  Syntax         | Example|
+|-----------------|------------------|--------------|
+| No aggregation   |  \`SELECT CASE WHEN condition1 THEN outcome1, WHEN condition2 THEN outcome 2 ELSE outcome3 END\`        |       \`SELECT CASE WHEN {attribute/activity_type} IN ("email", "meeting") THEN 1, WHEN {attribute/activity_type} IN ("phone_call") THEN 2 ELSE 0 END\`|
+|With aggregation   |\`SELECT SUM (SELECT CASE WHEN condition1 THEN outcome1, WHEN condition2 THEN outcome2 ELSE outcome3 END)\`  | \`SELECT SUM (SELECT CASE WHEN {attribute/activity_type} IN ("email", "meeting") THEN {fact/amount} ELSE {fact/loss} END)\` |
+
+Using the aggregation container ensures that the CASE conditions are
+computed on the correct dimension and returns relevant results.
+
+## How to Use CASE Correctly
+
+As noted above, we advise you to use CASE inside aggregation containers.
+
+Here is an example of incorrect use of CASE in the following logical
+data model. For the sake brevity, only one CASE condition is used.
+
+![An example of incorrect use of CASE ](https://www.gooddata.com/developers/cloud-native/doc/maql/case.png)
+
+If you want to slice the following metric with **Campaign Category**,
+the visualization would not compute because the WHEN conditions are not
+related to visualization dimensionality:
+
+\`\`\`
+SELECT CASE WHEN {fact/customer_state} IN ("AR", "NY") THEN SUM ({fact/price}) ELSE SUM({fact/price} * {fact/quantity}) END
+\`\`\`
+
+On the other hand, the same metric when sliced by attribute **Customer
+ID** (instead of **Campaign Category**) is valid. That is because the
+slicing attribute (**Customer ID**) is directly related to the CASE
+condition attribute (Customer State).
+
+If you need to slice by unrelated attribute, put the CASE statement
+inside the SUM aggregation instead:
+
+\`\`\`
+SELECT SUM(SELECT CASE WHEN {attribute/customer_state} IN ("AR", "NY") THEN {fact/price} ELSE {fact/price} * {fact/quantity} END)
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/conditionals/if-then-else.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# IF THEN ELSE\nIF THEN ELSE construct is a simplified version of CASE statement: \n\n```\nSELECT IF condition THEN expression ELSE expression END\n```\nis equivalent to\n```\nSELECT CASE WHEN condition THEN expression ELSE expression END\n```\n\nFor the detailed discussion of the semantics see [CASE statement](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/conditionals/case/).\n\n## Syntax\n\n```\nSELECT IF \u2026 THEN \u2026 ELSE \u2026 END\nSELECT IF condition THEN number ELSE number END\nSELECT IF condition THEN arithmetic_operation ELSE arithmetic_operation END\n```\n\n## Examples\n\n```\nSELECT IF SUM({fact/amount})>= AVG({fact/amount}) THEN 10 ELSE 0 END\nSELECT IF SUM({fact/duration}) - AVG({fact/duration}) > 2000  THEN 0 ELSE 1 END\nSELECT IF AVG({fact/probability}) > 0.5 THEN SUM({fact/amount}) * 10 ELSE SUM({fact/amount}) / 10 END\n```";
+//# sourceMappingURL=if-then-else.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/conditionals/if-then-else.d.ts.map

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

package/esm/docs/en/docs/create-metrics/maql/conditionals/if-then-else.js

@@ -0,0 +1,29 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# IF THEN ELSE
+IF THEN ELSE construct is a simplified version of CASE statement: 
+
+\`\`\`
+SELECT IF condition THEN expression ELSE expression END
+\`\`\`
+is equivalent to
+\`\`\`
+SELECT CASE WHEN condition THEN expression ELSE expression END
+\`\`\`
+
+For the detailed discussion of the semantics see [CASE statement](https://www.gooddata.com/developers/cloud-native/doc/hosted/create-metrics/maql/conditionals/case/).
+
+## Syntax
+
+\`\`\`
+SELECT IF … THEN … ELSE … END
+SELECT IF condition THEN number ELSE number END
+SELECT IF condition THEN arithmetic_operation ELSE arithmetic_operation END
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT IF SUM({fact/amount})>= AVG({fact/amount}) THEN 10 ELSE 0 END
+SELECT IF SUM({fact/duration}) - AVG({fact/duration}) > 2000  THEN 0 ELSE 1 END
+SELECT IF AVG({fact/probability}) > 0.5 THEN SUM({fact/amount}) * 10 ELSE SUM({fact/amount}) / 10 END
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/conditionals/ifnull.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# IFNULL\nIFNULL statement allows you to control replacement of missing values that are returned by an expression.\n\nIf a metric expression that is wrapped within an IFNULL statement ever returns a null value, the replacement number specified in the second parameter of the IFNULL function is inserted in place of the null value.\n\nIFNULL is useful especially in cases where a sub-metric is referred to within another metric's definition. Wrapping the sub metric in an IFNULL statement keeps the encompassing metric from becoming null due to one of its components returning a null value. \n\n## Syntax\n\n```\nSELECT IFNULL(\u2026,\u2026)\nSELECT IFNULL(metric, replacement_value)\n```\n\n## Examples\n\n```\nSELECT IFNULL(SUM({fact/amount}), 0)\nSELECT IFNULL(SUM({metric/fb_cost} + {metric/tw_cost}), 0)\nSELECT IFNULL(SUM({fact/amount}) + 100, 1)\n```\n\nSupported replacement values include constants, but not other metric expressions.\n\n## IFNULL Best Practices\n\nThe IFNULL function is used to replace missing values in fact tables and to replace values when a computation generates a null value.\n\nA null value is not the same thing as zero (0). A null value means one of the following:\n\n-   no entry has been made\n-   the value is unknown\n\nThe IFNULL function can be useful for handling or trapping values that are null, which can confuse your analysis.\n\nHowever, the function should not be overused, as it can add significant computing time and consume workspace computational bandwidth.\n\nDo not apply IFNULL to all of your functions or even your basic sum, average, and count functions. Instead, use IFNULL where the presence of null values is causing confusion or ambiguity in the visualizations you have created.\n\nWrapping a metric in the IFNULL statement enables operations where one of the values is null. The syntax for this statement looks like the following:\n\n```\nSELECT IFNULL(metric_reference, replacement_value)\n```\n\nThe IFNULL function can be applied to facts, too.\n\n```\nSELECT IFNULL(fact_name, replacement_value)\n```\n\n**Example - Data with a missing line item**\n\nAn IFNULL does not mean that there is a blank or missing line item.\n\nSuppose your data looks like the following:\n\n  |Date      |   Sales Amounts|\n  |------------| ---------------|\n  |08/01/2013  | $3,000|\n  |08/02/2013  | $5,700|\n  |08/03/2013  | $2,000|\n  |08/05/2013  | $4,400|\n\nWrapping the `Sales Amount` metric in an IFNULL function does not make data for 08/04/2013 appear because there isn't any data for that day.\n\nThe IFNULL function does not populate rows of data when the row does not exist. Instead, IFNULL forces a value to appear when the value is blank.\n\n**Example - IFNULL and arithmetic operations**\n\nThe prime example of when to use IFNULL is when you are performing an arithmetic operation, and one of the values could potentially be null.\n\nSuppose you have different types of transactions: payments, refunds, and partial refunds. You have two metrics to measure payments ( `# Payments` ) and refunds ( `# Refunds` ):\n\n```\nSELECT COUNT({attribute/transaction_id}) WHERE {attribute/transaction_type} = \"Sale\"\nSELECT COUNT({attribute/transaction_id}) WHERE {attribute/transaction_type} IN (\"Full Refund\", \"Partial Refund\")\n```\n\nNow, suppose your daily analysis calculates the difference between the number of payments received and the refunds processed. The difference metric should look like the following:\n\n```\nSELECT {metric/no_of_payments} - {metric/no_of_refunds}\n```\n\nHowever, your enterprise does not process refunds every day. If no refunds are processed for a day, the above metric generates a null value, even if there are payments.\n\nIf one of the values within an expression is null, the entire expression is null. Use `IFNULL` to preserve the computation.\n\nTo solve this problem, you would wrap the expressions in the IFNULL function like the following:\n\n```\nSELECT IFNULL({metric/no_of_payments},0) - IFNULL({metric/no_of_refunds},0)\n```\nIf a refund was not processed for the day, the calculation can still be performed.";
+//# sourceMappingURL=ifnull.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/conditionals/ifnull.d.ts.map

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