Solving Table View Problems in Dynamics 365 Sales: A Troubleshooting Guide

Table of Contents

Dynamics 365 Sales relies heavily on views to display lists of records in a structured format, allowing users to quickly access and manage data. However, users may occasionally encounter issues where data isn’t displaying correctly in columns, records are missing, or default views behave unexpectedly. This guide provides troubleshooting steps and resolutions for common problems related to table views and subgrids within Dynamics 365 Sales. Understanding the underlying causes can help administrators and power users diagnose and fix these issues effectively.

This article will walk through specific scenarios and provide detailed instructions to address them, ensuring your Dynamics 365 views function as intended. Proper configuration of views and subgrids is crucial for maintaining data integrity and enhancing user productivity within the system. By following these steps, you can resolve common view-related problems and ensure a smooth user experience.

Issue 1: Can’t See Data in Certain Columns in Table Views¶

Users might notice that specific columns in a view appear empty or display no data, even though the records themselves exist and have data populated in those fields when viewed on a form. This issue can be frustrating as it prevents users from gaining a complete overview of the data directly from the view. It often suggests a technical discrepancy in how the view is defined.

Cause¶

This problem typically arises from a technical inconsistency within the view’s definition. Specifically, there is a mismatch between the column names defined in the layoutxml and the fetchxml components of the view’s underlying ODATA file (accessible via OrgUrl/api/data/Dynamics 365 version/savedqueries(ViewId)). The layoutxml dictates how columns are visually presented, while the fetchxml determines which data fields are queried. If the names for the same field don’t align between these two components, the system struggles to map the retrieved data to the intended display column, resulting in a blank appearance.

Resolution¶

The most straightforward way to resolve this mismatch is to remove the problematic column from the view definition and then add it back. This action forces the system to regenerate the layoutxml and fetchxml for that specific column, ensuring that the names are correctly synchronized. This is a common fix for synchronization issues within view definitions.

Before proceeding, it’s important to identify the specific view and the particular column within that view that is exhibiting this issue. Make a note of these details to ensure you target the correct elements during the resolution process.

Here are the detailed steps to perform this resolution:

1. Navigate to the system customization area. This is typically done by selecting Settings (gear icon) > Advanced Settings > Settings > Customizations > Customize the System. This path ensures you are working within the solution explorer for comprehensive customizations.
2. In the Solution Explorer on the left pane, expand Entities. Locate and expand the specific Entity (or table) for which the view is having issues. Then, select Views under that entity. Find and select the particular view where the column data is missing. For instance, if the issue is with the “Accounts Being Followed” view of the “Account” entity, you would navigate to Entities > Account > Views and select “Accounts Being Followed”.
3. With the view selected, access the view editing options. In the command bar at the top, select More Actions, and then choose Edit. This action opens the View editor, which provides a visual interface for modifying the view’s columns, filters, and sorting.
   
4. Within the View editor, identify the column that is not displaying data correctly. Click on the header of this column to select it. Once selected, click the Remove button in the command bar. Confirm the removal if prompted. This step deletes the current, potentially corrupted, definition of the column within the view’s layout.
5. After removing the column, you need to add it back. Click the Add Columns button located in the right panel or command bar. Search for the same field that you just removed. Select the field from the list of available columns and click OK or Done to add it back to the view. You can reposition the column by dragging its header if necessary. This process reintegrates the column with a fresh, correctly generated definition.
   
6. Save the changes to the view by clicking Save in the command bar. It is crucial to also Publish the entity (or all customizations) for the changes to take effect for all users. Navigate back to the Solution Explorer and select Publish All Customizations or select the specific entity and click Publish. Once published, refresh the Dynamics 365 interface where the view is used. The data in the previously blank column should now display correctly, as the layoutxml and fetchxml for the column are now aligned.

This procedure effectively resets the column’s definition within the view, resolving the underlying technical mismatch that prevented the data from being displayed.

Issue 2: Can’t See Some Records in the Table Views¶

Users might observe that a view appears to be missing certain records that they know exist and should logically be included based on the entity type. For example, a view of ‘Active Accounts’ might not show an account that is clearly marked as active. This issue points towards limitations or misconfigurations in the data filtering applied to the view.

Cause¶

The primary cause for records being absent from a view is the filtering applied to that view. Views in Dynamics 365 are defined not only by the columns they display but also by specific criteria that filter the records to be included. If the filter criteria are too restrictive, incorrectly configured, or exclude certain records unintentionally, those records will not appear in the view, regardless of whether they exist in the system.

Resolution¶

To ensure that all intended records are displayed, you must review and potentially edit or remove the filter criteria applied to the view. Modifying the filters allows you to widen the scope or correct any errors that might be inadvertently excluding records. This process requires understanding the desired record set for the view and adjusting the filter logic accordingly.

As with the previous issue, make sure you have identified the specific view that is not displaying all expected records before starting.

Follow these steps to adjust the view’s filter criteria:

1. Access the customization area by going to Settings (gear icon) > Advanced Settings > Settings > Customizations > Customize the System.
2. In the Solution Explorer, expand Entities, locate the relevant Entity, and select Views. Select the specific view that is missing records. Using the example from Issue 1, this could be Entities > Account > Views and selecting a view like “Active Accounts”.
3. In the command bar of the View editor, select More Actions, and then choose Edit. This opens the View editor.
4. Within the View editor interface, locate the Edit Filter Criteria button, often found in the command bar or a dedicated section. Click this button. This action opens a dialog box or a dedicated pane where you can see and modify the filter conditions applied to the view.
   
5. Carefully review the existing filter conditions. Each condition specifies a field, an operator (e.g., ‘Equals’, ‘Does Not Equal’, ‘Contains Data’), and a value or comparison. Analyze the logic to determine if any condition is too strict or incorrectly configured, leading to the exclusion of records. You can update the values or operators, add new conditions, group conditions using AND/OR logic, or remove conditions entirely if they are unnecessary or incorrect. For example, if an ‘Active Accounts’ view has a filter for ‘Status Reason Equals Inactive’, this would incorrectly exclude active accounts. You would need to change the condition to ‘Status Reason Equals Active’ or ‘Status Equals Active’.
6. After making the necessary adjustments to the filter criteria, click OK or Apply in the filter editor to save the filter changes.
7. Save the changes to the view in the View editor’s command bar by clicking Save. Then, publish the entity or all customizations via the Solution Explorer (Publish All Customizations or select entity and Publish). Once published, refresh the Dynamics 365 interface. The view should now display the records that were previously missing, assuming the filter criteria correctly define the desired record set.

Regularly reviewing and testing view filters is essential, especially after system updates or customizations, to ensure they align with business requirements and display the expected data.

Issue 3: Can’t See Some Records in Opportunity, Quote, Order, or Invoice Subgrids¶

When working with forms for sales entities like Opportunity, Quote, Order, or Invoice, users might notice that subgrids displaying related records (e.g., Opportunity Products, Quote Products, Order Products, Invoice Products) are missing some expected items. This problem is specific to the context of a form and the related records shown in an embedded list (subgrid).

Cause¶

Missing records in subgrids on these specific sales entity forms are often caused by errors or incorrect configurations within the customization of the subgrid itself. Subgrids are configurable controls on a form, and their properties, including the view they use and specific settings related to data display (especially for features like editable grids or bundled products), must be set correctly. A common issue arises when the subgrid control properties, particularly for the ‘Editable Grid’ control, are not configured to correctly display all items, including nested ones like product bundles.

Resolution¶

To fix records missing from these sales subgrids, you need to access the form customization and verify that the subgrid control properties are set up correctly. This involves checking which control is used for the subgrid and ensuring its configuration, including the views specified for the main grid and any nested grids, is accurate.

Here’s how to correct the subgrid configuration:

1. Access Advanced Settings by clicking the Settings icon (gear) on the navigation bar and selecting Advanced Settings. This opens the Business Management settings page in a new tab.
   
2. On the navigation bar within the Advanced Settings page, select Settings. Under the Customization section, choose Customizations.
3. Select Customize the System to open the Solution Explorer.
4. In the Solution Explorer under Components, expand Entities. Expand the specific entity whose form contains the problematic subgrid (e.g., Opportunity). Expand Forms under that entity.
5. Open the Main form of the entity where the subgrid issue occurs. For example, open the Opportunity form of type Main. This will open the form editor.
6. Within the form editor, locate the section containing the subgrid that is not displaying all records. For Opportunity forms, this is often the ‘Product Line Items’ section containing the ‘Opportunity Products’ subgrid. Double-click on the subgrid control itself (or the section header, depending on how the subgrid is embedded) to open its properties dialog box. In older interfaces, you might double-click the Connections section within ‘Product Line Items’ if that’s where the subgrid is placed. The Set Properties dialog box for the subgrid will open.
   
7. In the Set Properties dialog, navigate to the Controls tab. If the ‘Editable Grid’ control is added and set as the default for web, phone, or tablet, double-click to select Editable Grid. This opens the configuration options for the editable grid control on this subgrid.
   
8. Carefully review the settings for the Editable Grid control. Ensure that all values are configured correctly according to best practices or your specific requirements. Pay close attention to the following properties:
   • Grid View: Verify that the correct view is selected for the main level of the subgrid (e.g., “Opportunity Product Inline Edit View”).
   • Nested Grid View: If your subgrid displays nested records (like bundled products within a product bundle item), click the pencil icon next to this property. Ensure the correct Table (e.g., Opportunity Products) and View (e.g., Opportunity Product Inline Edit View: Bundle Products) are specified for the nested items. This is crucial for displaying contents of bundles.
     
   • Nested grid parent ID: This field links the nested grid items back to their parent item in the main grid. Ensure the correct lookup field is specified (e.g., parentbundleidref for product bundles).
   • Group by Column: This should typically be set to Enabled (Enum) if you want items to be grouped, for example, by product bundle.
   • Allow filtering: This should typically be set to Enabled (Enum) to allow users to filter the subgrid data.
   • Hide nested grid column header: This setting controls whether the headers for columns within a nested grid are shown. Make sure this is configured appropriately. Note: If you are using product bundles and need to edit the line items within these bundles directly in the product grid, you should select Show Column for this setting. Having it hidden can sometimes impact functionality related to editing bundled items.
9. After verifying and correcting these settings, click OK on the Configure Property dialogs and then OK on the Set Properties dialog for the subgrid.
10. Save the form by clicking the Save icon in the form editor’s command bar. Finally, Publish the entity (or all customizations) to make the changes live for users.

By ensuring the subgrid control properties, especially for editable grids and nested views, are accurately configured, you resolve issues that prevent related records from appearing correctly on the form.

Issue 4: Can’t Set a Custom View as the Default View for the Existing Products Field in Add Products Dialog¶

When adding products to an Opportunity, Quote, Order, or Invoice, users interact with an ‘Add Products’ dialog. Within this dialog, they select products using a lookup field, often labeled “Existing Product”. Users might attempt to change the default view for this lookup field to a custom view they’ve created, but find that it consistently reverts to a specific system view and doesn’t display products from their desired custom view.

Cause¶

This behavior is by design within Dynamics 365. To facilitate the process of adding products and ensuring that users select products that are available for the selected price list on the document (Opportunity, Quote, etc.), the lookup field for ‘Existing Product’ in the ‘Add Products’ dialog box always defaults to a system view specifically designed for this purpose. This view is typically named Products in Parent Price List. This default behavior is hardcoded to prioritize showing only products relevant to the current transaction’s price list, preventing the addition of incompatible products.

Resolution¶

This scenario is not a bug but intended system behavior. You cannot permanently change the default view for the ‘Existing Products’ lookup field in the ‘Add Products’ dialog from the Products in Parent Price List view through standard customization. The system will always revert to this specific view when the dialog is opened.

Although you cannot set a custom view as the default, users can manually switch the view within the lookup dialog itself. When the lookup dialog opens, there is typically a view selector control (often labeled with the current view name) that users can click to choose from other available public views for the Product entity.

Users will need to manually select their preferred custom view each time they open the ‘Existing Product’ lookup from the Add Products dialog if they require a view other than the default Products in Parent Price List. While this requires an extra step, it allows users to access and utilize other views for selecting products when needed.

Issue 5: Save Icon Disabled When Updating Nested Bundle Items on Opportunity Product Tab¶

Users editing nested product bundle items directly within the editable grid on the ‘Product’ tab of an Opportunity form might find that the ‘Save’ icon or button becomes disabled, preventing them from saving their changes. This issue specifically affects the ability to modify and save details for components within a product bundle when using the editable grid control.

Cause¶

This problem occurs when the header for the nested grid columns is hidden within the configuration of the ‘Editable Grid’ control applied to the Opportunity Products subgrid. Hiding the nested grid column header, while sometimes desired for a cleaner visual appearance, can interfere with the functionality required for editing and saving changes to nested items, particularly within the context of product bundles. The system’s editing mechanism for nested rows seems to rely on the presence or visibility of these headers.

Resolution¶

To resolve this issue, you need to modify the configuration of the ‘Editable Grid’ control on the Opportunity form to ensure that the header for nested grid columns is shown.

Follow these steps to show the nested grid column header:

1. Access Advanced Settings via the Settings icon (gear) on the nav bar, then select Advanced Settings. This opens the Business Management settings page in a new browser tab.
2. On the navigation bar of the Advanced Settings page, select Settings, then under Customization, select Customizations.
   
3. Select Customize the System to open the Solution Explorer.
4. In the Solution Explorer under Components, expand Entities, expand Opportunity, and then select Forms.
5. Open the Opportunity form of form type Main.
6. In the form editor, locate the ‘Product Line Items’ section. Double-click on the Opportunity products subgrid control within this section. This will open the Set Properties dialog box for the subgrid.
7. In the Set Properties dialog, go to the Controls tab. Double-click to select the Editable Grid control configuration.
8. In the Editable Grid configuration section, find the property labeled Hide nested grid column header. Click the pencil icon next to this property to configure its setting.
   
9. In the Configure Property dialog box, under the Bind to static options section, select the option Show column header. This explicitely tells the editable grid to display the headers for columns within the nested grid rows.
10. Click OK on the Configure Property dialog, then OK on the Set Properties dialog for the subgrid.
11. Save the form in the form editor.
12. Publish the entity or all customizations. Once published, refresh the Opportunity form. You should now be able to edit nested bundle items in the subgrid, and the ‘Save’ icon should be enabled, allowing you to save your changes successfully.

This adjustment ensures that the necessary interface elements (the nested grid headers) are present, which seems to be required for the editable grid control’s save functionality to work correctly for nested records.

Issue 6: Can’t See Opportunity Records in the Legacy Web Client When Selecting Opportunities from the Site Map, But Can See Them in Unified Interface¶

Users working with Dynamics 365 might encounter a situation where navigating to a specific entity’s view (like Opportunities) from the site map in the older, legacy web client interface shows no records, or an incorrect view, while accessing the same entity in the newer Unified Interface displays records correctly using the expected default view.

Cause¶

This discrepancy between the legacy web client and Unified Interface often occurs because the legacy web client relies heavily on a ‘default’ public view being explicitly set for an entity. If no public view is marked as the default for a table, the legacy web client may fail to load any view or load an arbitrary view incorrectly when the entity is accessed via the site map. The Unified Interface is more resilient and can often determine a suitable view even if a default isn’t explicitly set, or it might handle views differently.

Resolution¶

To resolve this issue and ensure that records are displayed correctly when navigating to the entity from the site map in the legacy web client, you must explicitly set one of the public views for that entity as the default view. This provides the legacy interface with the necessary instruction on which view to load initially.

Here’s how to set a default view for an entity:

1. Access customizations via Settings (gear) > Advanced Settings > Settings > Customizations > Customize the System.
   
2. In the Solution Explorer, expand Entities, find and expand the specific entity having the issue (e.g., Opportunity), and select Views.
3. In the list of views, identify the public view you want to set as the default. Public views are those available to all users (as opposed to personal views).
4. Select the desired public view. In the command bar, you should see an option like More Actions. Click this and look for an option to Set as Default View. Click this option. Alternatively, depending on the version and interface, you might right-click the view and select “Set as Default View”.
   
5. Confirm the action if prompted. Once set, the chosen view will be indicated as the default view for that entity in the list of views.
6. Save the customizations by clicking Save in the command bar of the Solution Explorer.
7. Publish the entity or all customizations.

After publishing, refresh the legacy web client interface. Navigating to the entity (e.g., Opportunities) from the site map should now correctly load the view you designated as the default, and records should be displayed. While the Unified Interface handles views more flexibly, explicitly setting a default public view is a best practice, especially if users still access the legacy client or if you need consistent behavior across different interfaces.

Summary Table of Issues and Resolutions:

Issue	Cause	Resolution
Data missing in certain columns in views	Mismatch between layoutxml and fetchxml for the column	Remove and re-add the problematic column in the View editor.
Some records missing in views	Incorrect or overly restrictive filter criteria applied to the view	Edit or remove filter criteria for the view in the View editor.
Some records missing in Opportunity/Quote/Order/Invoice subgrids	Incorrect subgrid control customization (e.g., Editable Grid properties)	Verify and correct the subgrid’s Editable Grid control properties, especially Nested Grid View and Nested grid parent ID.
Cannot set custom view as default for ‘Existing products’ lookup	System defaults to ‘Products in Parent Price List’ view to ensure price list compatibility	This is by design; users must manually switch views in the lookup dialog.
Save icon disabled editing nested bundle items in subgrid Editable Grid	‘Hide nested grid column header’ is enabled for the Editable Grid control	Set the ‘Hide nested grid column header’ property for the Editable Grid control to ‘Show column header’.
Cannot see records in legacy web client site map (but visible in UI)	No public view is set as the default view for the entity	Set one of the public views for the entity as the default view in customizations.

These troubleshooting steps cover several common issues encountered with views and subgrids in Dynamics 365 Sales. By systematically checking view configurations, filter criteria, and subgrid properties, you can often resolve these display problems.

Do you have further questions about troubleshooting views or subgrids in Dynamics 365 Sales? Share your experience or ask for clarification in the comments below!