Today, Dynamics 365 Finance & Operations only allows personalization of fields that originate from the primary datasource already defined on the form. Fields from related or joined tables do not appear in the “Add columns” personalization dialog unless a developer first adds the related table as a datasource in a form extension.

Community documentation confirms that even when a custom datasource is added to a form, its fields only appear for personalization when the join is explicitly added with the correct link type (e.g., Outer Join) through an extension, not through the UI itself. This means users cannot expose joined-table fields through personalization alone.

Additionally, personalization guidance shows that users can only insert fields already available on the defined datasource, and no mechanism exists to surface related table fields without development work. [community Dynamics.com] [stackoverflow.com]

This creates unnecessary friction for end users and forces organizations to create extensions for simple visibility needs, such as showing related item, vendor, customer, or dimension fields.

Requested Feature:

Please add the ability for users to add fields from related (joined) tables to list grids through personalization, without requiring a form extension or any X++ customization.

The feature should allow a user to:

Open “Add columns” in personalization.

Browse related tables based on existing table relations.

Select fields from those related tables.

Have the system automatically generate a safe, read‑only join behind the scenes.

Business Value:

Eliminates unnecessary customizations: Many extensions exist only to expose fields from related tables, which could be handled natively.

Empowers users / aligns with low‑code strategy: Improves self‑service personalization and reduces reliance on developers.

Improves productivity: Users can surface the data they need without switching forms or opening inquiries.

Provides consistency with other Dynamics apps: Other D365 products allow richer related-data visibility without development.

Example Use Cases:

Showing Item Group or Product Name on Sales or Purchase lines.

Displaying Vendor Name instead of only Vendor ID.

Surfacing related financial dimensions directly in grids.

Showing customer metadata on orders without customizing the form.

Summary:

Please enhance personalization to allow adding fields from joined/related tables directly in grid views. This would significantly reduce extensions, empower users, and modernize the data‑visibility experience across D365 Finance & Operations.