Add related column clarification to VirtualDataset and Grid docs

src/en/developer-guide/applications/controls/VirtualDataset/general.md

@@ -383,7 +383,48 @@ 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 `<link-entity>` 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
+<fetch>
+  <entity name="talxis_project">
+    ...
+    <link-entity name="talxis_category" from="talxis_categoryid" to="talxis_categoryid" link-type="outer" alias="a_e1371f3c98fd4fa094ca25fbf67eacb0">
+      <attribute name="talxis_description" />
+    </link-entity>
+  </entity>
+</fetch>
+```
+
+> **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": "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 `<link-entity>` 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
 

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).