From 68ddf4eaae0104bf471db28481ceba3e499d7b81 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:44:50 +0000 Subject: [PATCH 1/7] Initial plan From 197bdad224fbf3bf431012ce5a1d27cf4b87d4aa Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:48:56 +0000 Subject: [PATCH 2/7] Add documentation for related (linked entity) columns using dotted notation in TALXIS Grid Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 55 +++++++++++++++++++ .../applications/controls/grid.md | 6 ++ 2 files changed, 61 insertions(+) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index ce96de38..a52a7622 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -383,7 +383,62 @@ When both Columns binding and `savedqueryid` are present: - Columns binding details override corresponding layoutxml information - Additional columns in Columns binding are added alongside layoutxml columns +##### Related (Linked Entity) Columns +When a Dataverse view includes columns from related entities (via `link-entity` in FetchXml), these columns use a **dotted notation** format in the `name` and `alias` properties: + +``` +{link-entity-alias}.{attribute-name} +``` + +The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the view's FetchXml. This alias is auto-generated by Dataverse when columns from related entities are added to a view. + +For example, given a FetchXml view that links to a related entity: + +```xml + + + + + + + + + +``` + +The corresponding Columns binding would reference the related column using the link-entity alias and dotted notation: + +```json +[ + { + "name": "pba_name", + "alias": "pba_name", + "dataType": "SingleLine.Text", + "displayName": "Name", + "order": 0, + "visualSizeFactor": 100 + }, + { + "name": "pba_projekt", + "alias": "pba_projekt", + "dataType": "Lookup.Simple", + "displayName": "Project", + "order": 1, + "visualSizeFactor": 100 + }, + { + "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", + "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", + "dataType": "SingleLine.Text", + "displayName": "Related Code", + "order": 2, + "visualSizeFactor": 100 + } +] +``` + +> **Tip:** To find the correct alias for a related column, open the view definition (savedquery) in Dataverse and inspect the `` alias in the FetchXml, or check the view's `layoutxml` for the column names — related columns will already use the dotted notation there. ##### Virtual Columns diff --git a/src/en/developer-guide/applications/controls/grid.md b/src/en/developer-guide/applications/controls/grid.md index 686c606d..95fc1b3c 100644 --- a/src/en/developer-guide/applications/controls/grid.md +++ b/src/en/developer-guide/applications/controls/grid.md @@ -12,6 +12,12 @@ Grid is a dataset PCF wrapper over [Virtual Dataset](./VirtualDataset/general.md Since Grid can be directly bound to a Subgrid or Homepage grid, it does not require any additional configuration. You can simply add the Grid control to your form and bind it to the desired dataset. Of course, you can still use other parameters to customize the control's behavior the same way as you would with the Virtual Dataset control. Grid behaves the same as Virtual Dataset with `FetchXmlDataProvider`, so the behavior (for example in regards to the `Columns` binding) is identical. +## Column Configuration + +When Grid is bound to a Subgrid, column definitions are derived from the underlying Dataverse view. You can override or extend these columns by configuring the `Columns` parameter on the control. The `Columns` parameter accepts a JSON array of column definitions — see the [Column Configuration section of the Virtual Dataset documentation](./VirtualDataset/general.md#column-configuration) for a full reference of supported properties. + +If the underlying view includes columns from related entities (via `link-entity`), you must use the **dotted notation** (`{link-entity-alias}.{attribute-name}`) in both the `name` and `alias` fields. See [Related (Linked Entity) Columns](./VirtualDataset/general.md#related-linked-entity-columns) for details and examples. + ## Ribbon Grid is able to leverage the same Ribbon commands as the standard Power Apps grids. This means that you can use the existing Ribbon buttons and commands to perform actions on the Grid control, such as creating new records, deleting records, or exporting data. You can also render these buttons inline by following the instructions in the [Ribbon section of the Virtual Dataset documentation](./VirtualDataset/general.md#inline-ribbon). From 52524f13aa5dcbebcd781e4b916b81c9b3fd954d Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:49:55 +0000 Subject: [PATCH 3/7] Address code review: improve example with distinct from/to attributes and note about auto-generated alias Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index a52a7622..5ac3764c 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -397,16 +397,18 @@ For example, given a FetchXml view that links to a related entity: ```xml - + - - + + ``` +> **Note:** The alias (e.g. `a_e1371f3c98fd4fa094ca25fbf67eacb0`) is auto-generated by Dataverse when you add a related column to a view through the view designer. You must use this exact alias value in the Columns binding. + The corresponding Columns binding would reference the related column using the link-entity alias and dotted notation: ```json @@ -420,10 +422,10 @@ The corresponding Columns binding would reference the related column using the l "visualSizeFactor": 100 }, { - "name": "pba_projekt", - "alias": "pba_projekt", + "name": "pba_customerid", + "alias": "pba_customerid", "dataType": "Lookup.Simple", - "displayName": "Project", + "displayName": "Customer", "order": 1, "visualSizeFactor": 100 }, @@ -431,7 +433,7 @@ The corresponding Columns binding would reference the related column using the l "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", "dataType": "SingleLine.Text", - "displayName": "Related Code", + "displayName": "Investment Action Code", "order": 2, "visualSizeFactor": 100 } From e7b22831840890d4af45bfb7230e3065e3d9a85d Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:53:58 +0000 Subject: [PATCH 4/7] Move view/savedquery references from VirtualDataset to Grid docs, use talxis_ prefix and English names Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 45 +++++-------- .../applications/controls/grid.md | 63 ++++++++++++++++++- 2 files changed, 78 insertions(+), 30 deletions(-) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index 5ac3764c..1c7933c0 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -374,74 +374,63 @@ If you wish to use Edit Columns feature with Memory Provider, you must specify a #### FetchXml Provider -FetchXml Provider handles columns differently than Memory Provider: - -- **Without `savedqueryid`**: Behaves like Memory Provider - only explicitly specified columns in Columns binding are displayed (only `name` property is mandatory) -- **With `savedqueryid`**: Automatically retrieves associated layoutxml to define columns - -When both Columns binding and `savedqueryid` are present: -- Columns binding details override corresponding layoutxml information -- Additional columns in Columns binding are added alongside layoutxml columns +Only explicitly specified columns in the Columns binding are displayed. Only the `name` property is mandatory for each column. ##### Related (Linked Entity) Columns -When a Dataverse view includes columns from related entities (via `link-entity` in FetchXml), these columns use a **dotted notation** format in the `name` and `alias` properties: +When the FetchXml query contains `link-entity` elements to join related entities, columns from those linked entities use a **dotted notation** format in the `name` and `alias` properties: ``` {link-entity-alias}.{attribute-name} ``` -The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the view's FetchXml. This alias is auto-generated by Dataverse when columns from related entities are added to a view. +The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the FetchXml query. -For example, given a FetchXml view that links to a related entity: +For example, given a FetchXml query that links to a related entity: ```xml - - - - - + + + + + ``` -> **Note:** The alias (e.g. `a_e1371f3c98fd4fa094ca25fbf67eacb0`) is auto-generated by Dataverse when you add a related column to a view through the view designer. You must use this exact alias value in the Columns binding. - -The corresponding Columns binding would reference the related column using the link-entity alias and dotted notation: +The corresponding Columns binding would reference the linked entity column using dotted notation: ```json [ { - "name": "pba_name", - "alias": "pba_name", + "name": "talxis_name", + "alias": "talxis_name", "dataType": "SingleLine.Text", "displayName": "Name", "order": 0, "visualSizeFactor": 100 }, { - "name": "pba_customerid", - "alias": "pba_customerid", + "name": "talxis_customerid", + "alias": "talxis_customerid", "dataType": "Lookup.Simple", "displayName": "Customer", "order": 1, "visualSizeFactor": 100 }, { - "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", - "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", + "name": "linked_category.talxis_description", + "alias": "linked_category.talxis_description", "dataType": "SingleLine.Text", - "displayName": "Investment Action Code", + "displayName": "Category Description", "order": 2, "visualSizeFactor": 100 } ] ``` -> **Tip:** To find the correct alias for a related column, open the view definition (savedquery) in Dataverse and inspect the `` alias in the FetchXml, or check the view's `layoutxml` for the column names — related columns will already use the dotted notation there. - ##### Virtual Columns FetchXml Provider supports virtual columns that do not exist in Dataverse. Set the `isVirtual` property to `true` in the column definition to indicate this to the provider. diff --git a/src/en/developer-guide/applications/controls/grid.md b/src/en/developer-guide/applications/controls/grid.md index 95fc1b3c..efc638ae 100644 --- a/src/en/developer-guide/applications/controls/grid.md +++ b/src/en/developer-guide/applications/controls/grid.md @@ -14,9 +14,68 @@ Since Grid can be directly bound to a Subgrid or Homepage grid, it does not requ ## Column Configuration -When Grid is bound to a Subgrid, column definitions are derived from the underlying Dataverse view. You can override or extend these columns by configuring the `Columns` parameter on the control. The `Columns` parameter accepts a JSON array of column definitions — see the [Column Configuration section of the Virtual Dataset documentation](./VirtualDataset/general.md#column-configuration) for a full reference of supported properties. +When Grid is bound to a Subgrid or Homepage grid, column definitions are automatically derived from the underlying Dataverse view (`savedqueryid`). You can override or extend these columns by configuring the `Columns` parameter on the control. The `Columns` parameter accepts a JSON array of column definitions — see the [Column Configuration section of the Virtual Dataset documentation](./VirtualDataset/general.md#column-configuration) for a full reference of supported properties. -If the underlying view includes columns from related entities (via `link-entity`), you must use the **dotted notation** (`{link-entity-alias}.{attribute-name}`) in both the `name` and `alias` fields. See [Related (Linked Entity) Columns](./VirtualDataset/general.md#related-linked-entity-columns) for details and examples. +When both the `Columns` parameter and the underlying view are present: +- Column details in the `Columns` parameter override the corresponding view layout information +- Additional columns defined in the `Columns` parameter are added alongside the view columns + +### Related (Linked Entity) Columns + +If the underlying Dataverse view includes columns from related entities (via `link-entity`), these columns use a **dotted notation** format in the `name` and `alias` properties: + +``` +{link-entity-alias}.{attribute-name} +``` + +The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the view's FetchXml. This alias is typically auto-generated by Dataverse when columns from related entities are added to a view through the view designer. + +For example, given a view with this FetchXml: + +```xml + + + + + + + + + +``` + +The corresponding `Columns` parameter would reference the related column using the link-entity alias and dotted notation: + +```json +[ + { + "name": "talxis_name", + "alias": "talxis_name", + "dataType": "SingleLine.Text", + "displayName": "Name", + "order": 0, + "visualSizeFactor": 100 + }, + { + "name": "talxis_customerid", + "alias": "talxis_customerid", + "dataType": "Lookup.Simple", + "displayName": "Customer", + "order": 1, + "visualSizeFactor": 100 + }, + { + "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", + "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", + "dataType": "SingleLine.Text", + "displayName": "Category Description", + "order": 2, + "visualSizeFactor": 100 + } +] +``` + +> **Tip:** To find the correct alias for a related column, open the view definition (savedquery) in Dataverse and inspect the `` alias in the FetchXml, or check the view's `layoutxml` for the column names — related columns will already use the dotted notation there. ## Ribbon From b88b30d62a7c0e8136f1f0aa620ffb6e1dd190fe Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:58:39 +0000 Subject: [PATCH 5/7] Revert previous changes - VirtualDataset can work with savedqueries Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 45 ++++++++----- .../applications/controls/grid.md | 63 +------------------ 2 files changed, 30 insertions(+), 78 deletions(-) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index 1c7933c0..5ac3764c 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -374,63 +374,74 @@ If you wish to use Edit Columns feature with Memory Provider, you must specify a #### FetchXml Provider -Only explicitly specified columns in the Columns binding are displayed. Only the `name` property is mandatory for each column. +FetchXml Provider handles columns differently than Memory Provider: + +- **Without `savedqueryid`**: Behaves like Memory Provider - only explicitly specified columns in Columns binding are displayed (only `name` property is mandatory) +- **With `savedqueryid`**: Automatically retrieves associated layoutxml to define columns + +When both Columns binding and `savedqueryid` are present: +- Columns binding details override corresponding layoutxml information +- Additional columns in Columns binding are added alongside layoutxml columns ##### Related (Linked Entity) Columns -When the FetchXml query contains `link-entity` elements to join related entities, columns from those linked entities use a **dotted notation** format in the `name` and `alias` properties: +When a Dataverse view includes columns from related entities (via `link-entity` in FetchXml), these columns use a **dotted notation** format in the `name` and `alias` properties: ``` {link-entity-alias}.{attribute-name} ``` -The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the FetchXml query. +The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the view's FetchXml. This alias is auto-generated by Dataverse when columns from related entities are added to a view. -For example, given a FetchXml query that links to a related entity: +For example, given a FetchXml view that links to a related entity: ```xml - - - - - + + + + + ``` -The corresponding Columns binding would reference the linked entity column using dotted notation: +> **Note:** The alias (e.g. `a_e1371f3c98fd4fa094ca25fbf67eacb0`) is auto-generated by Dataverse when you add a related column to a view through the view designer. You must use this exact alias value in the Columns binding. + +The corresponding Columns binding would reference the related column using the link-entity alias and dotted notation: ```json [ { - "name": "talxis_name", - "alias": "talxis_name", + "name": "pba_name", + "alias": "pba_name", "dataType": "SingleLine.Text", "displayName": "Name", "order": 0, "visualSizeFactor": 100 }, { - "name": "talxis_customerid", - "alias": "talxis_customerid", + "name": "pba_customerid", + "alias": "pba_customerid", "dataType": "Lookup.Simple", "displayName": "Customer", "order": 1, "visualSizeFactor": 100 }, { - "name": "linked_category.talxis_description", - "alias": "linked_category.talxis_description", + "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", + "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", "dataType": "SingleLine.Text", - "displayName": "Category Description", + "displayName": "Investment Action Code", "order": 2, "visualSizeFactor": 100 } ] ``` +> **Tip:** To find the correct alias for a related column, open the view definition (savedquery) in Dataverse and inspect the `` alias in the FetchXml, or check the view's `layoutxml` for the column names — related columns will already use the dotted notation there. + ##### Virtual Columns FetchXml Provider supports virtual columns that do not exist in Dataverse. Set the `isVirtual` property to `true` in the column definition to indicate this to the provider. diff --git a/src/en/developer-guide/applications/controls/grid.md b/src/en/developer-guide/applications/controls/grid.md index efc638ae..95fc1b3c 100644 --- a/src/en/developer-guide/applications/controls/grid.md +++ b/src/en/developer-guide/applications/controls/grid.md @@ -14,68 +14,9 @@ Since Grid can be directly bound to a Subgrid or Homepage grid, it does not requ ## Column Configuration -When Grid is bound to a Subgrid or Homepage grid, column definitions are automatically derived from the underlying Dataverse view (`savedqueryid`). You can override or extend these columns by configuring the `Columns` parameter on the control. The `Columns` parameter accepts a JSON array of column definitions — see the [Column Configuration section of the Virtual Dataset documentation](./VirtualDataset/general.md#column-configuration) for a full reference of supported properties. +When Grid is bound to a Subgrid, column definitions are derived from the underlying Dataverse view. You can override or extend these columns by configuring the `Columns` parameter on the control. The `Columns` parameter accepts a JSON array of column definitions — see the [Column Configuration section of the Virtual Dataset documentation](./VirtualDataset/general.md#column-configuration) for a full reference of supported properties. -When both the `Columns` parameter and the underlying view are present: -- Column details in the `Columns` parameter override the corresponding view layout information -- Additional columns defined in the `Columns` parameter are added alongside the view columns - -### Related (Linked Entity) Columns - -If the underlying Dataverse view includes columns from related entities (via `link-entity`), these columns use a **dotted notation** format in the `name` and `alias` properties: - -``` -{link-entity-alias}.{attribute-name} -``` - -The `link-entity-alias` corresponds to the `alias` attribute on the `` element in the view's FetchXml. This alias is typically auto-generated by Dataverse when columns from related entities are added to a view through the view designer. - -For example, given a view with this FetchXml: - -```xml - - - - - - - - - -``` - -The corresponding `Columns` parameter would reference the related column using the link-entity alias and dotted notation: - -```json -[ - { - "name": "talxis_name", - "alias": "talxis_name", - "dataType": "SingleLine.Text", - "displayName": "Name", - "order": 0, - "visualSizeFactor": 100 - }, - { - "name": "talxis_customerid", - "alias": "talxis_customerid", - "dataType": "Lookup.Simple", - "displayName": "Customer", - "order": 1, - "visualSizeFactor": 100 - }, - { - "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", - "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", - "dataType": "SingleLine.Text", - "displayName": "Category Description", - "order": 2, - "visualSizeFactor": 100 - } -] -``` - -> **Tip:** To find the correct alias for a related column, open the view definition (savedquery) in Dataverse and inspect the `` alias in the FetchXml, or check the view's `layoutxml` for the column names — related columns will already use the dotted notation there. +If the underlying view includes columns from related entities (via `link-entity`), you must use the **dotted notation** (`{link-entity-alias}.{attribute-name}`) in both the `name` and `alias` fields. See [Related (Linked Entity) Columns](./VirtualDataset/general.md#related-linked-entity-columns) for details and examples. ## Ribbon From 82b153a3c562a33eb7836203860ee82492a57d47 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 09:59:39 +0000 Subject: [PATCH 6/7] Update VirtualDataset examples to use talxis_ prefix and English column names Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index 5ac3764c..766b3614 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -397,11 +397,11 @@ For example, given a FetchXml view that links to a related entity: ```xml - - - - - + + + + + @@ -414,26 +414,26 @@ The corresponding Columns binding would reference the related column using the l ```json [ { - "name": "pba_name", - "alias": "pba_name", + "name": "talxis_name", + "alias": "talxis_name", "dataType": "SingleLine.Text", "displayName": "Name", "order": 0, "visualSizeFactor": 100 }, { - "name": "pba_customerid", - "alias": "pba_customerid", + "name": "talxis_customerid", + "alias": "talxis_customerid", "dataType": "Lookup.Simple", "displayName": "Customer", "order": 1, "visualSizeFactor": 100 }, { - "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", - "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.pba_code", + "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", + "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", "dataType": "SingleLine.Text", - "displayName": "Investment Action Code", + "displayName": "Category Description", "order": 2, "visualSizeFactor": 100 } From ccd0ab6a2e6140904d59d683c5010fdb6498c44c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 11 Mar 2026 11:42:36 +0000 Subject: [PATCH 7/7] Shorten related column examples by omitting unrelated regular column definitions Co-authored-by: TomProkop <4339668+TomProkop@users.noreply.github.com> --- .../controls/VirtualDataset/general.md | 20 ++----------------- 1 file changed, 2 insertions(+), 18 deletions(-) diff --git a/src/en/developer-guide/applications/controls/VirtualDataset/general.md b/src/en/developer-guide/applications/controls/VirtualDataset/general.md index 766b3614..388d5c64 100644 --- a/src/en/developer-guide/applications/controls/VirtualDataset/general.md +++ b/src/en/developer-guide/applications/controls/VirtualDataset/general.md @@ -398,8 +398,7 @@ For example, given a FetchXml view that links to a related entity: ```xml - - + ... @@ -413,22 +412,7 @@ The corresponding Columns binding would reference the related column using the l ```json [ - { - "name": "talxis_name", - "alias": "talxis_name", - "dataType": "SingleLine.Text", - "displayName": "Name", - "order": 0, - "visualSizeFactor": 100 - }, - { - "name": "talxis_customerid", - "alias": "talxis_customerid", - "dataType": "Lookup.Simple", - "displayName": "Customer", - "order": 1, - "visualSizeFactor": 100 - }, + ... { "name": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description", "alias": "a_e1371f3c98fd4fa094ca25fbf67eacb0.talxis_description",