web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Kanban View does not s...
Customer experience | Sales, Customer Insights,...
Suggested Answer

Kanban View does not show all open Opportunities. what's happening

(2) ShareShare
ReportReport
Posted on by Rais 9

The Kanban view does not show all open opportunities visible in Read Only View. the numbers don't add up

  • Qualify (shows 4/4) for 4 opportunities in that stage
  • Develop (shows 4/4) there are 10 opportunity in that stage
  • Propose (shows 3/3) there are 12 opportunity in that stage
  • Close (shows 10/98) and shows all scrolled down) for 98 opportunities in that stage
I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi Rais,

    Through my test, i found that the opportunity created from the lead can't appear in the kanban view.

    pastedimage1656656499910v1.png

    You can check related lead of these opportunities that not appear in the kanban view, check status of them.

  • Inogic Profile Picture
    Inogic 760 on at
    Hello there,

    The reason you’re facing this issue is that when you qualify a lead into an opportunity, the record remains associated with the Lead to Opportunity Sales Process Business Process Flow (BPF).
    Since the record is tied to this BPF, it does not appear under the Sales Process BPF for opportunities. Additionally, the Lead to Opportunity BPF does not show in the dropdown because Microsoft’s out-of-the-box Kanban view does not support multi-entity BPFs.
    However, there are third-party solutions available, like Kanban Board. It integrates seamlessly with Dynamics 365, supporting multi-entity BPFs, including those that span across entities.

    This means that once a lead is qualified, it will appear in the correct stage on the Kanban board, no matter which BPF the record belongs to.
    It ensures that all opportunities, regardless of their origin, are displayed correctly in your Kanban view, making it a more versatile and user-friendly tool for managing your records.
     
    Thanks,
    Sam
     
  • Suggested answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,841 Moderator on at
    Hello Rais,
     

    That discrepancy between the Kanban view counts and the actual number of open opportunities in the Read-Only view is a common issue with a few potential causes. Here's a breakdown of what might be happening and how to troubleshoot it:

    Possible Causes:

    1. View Configuration Differences:

       

      • Underlying FetchXML: The Kanban view relies on a specific underlying FetchXML query to retrieve the data. This FetchXML might be different from the FetchXML used by the Read-Only view, even if they appear to be based on the same "Open Opportunities" system view. There could be subtle differences in the filtering criteria, linked entities, or sorting.

      • Kanban Column Mapping: The Kanban view is configured to group opportunities by a specific field (likely "Sales Stage" or a similar status field). If the mapping of the values in this field to the Kanban columns is incomplete or incorrect, some opportunities might not fall into any of the defined columns.

      • Status Reason Filtering: The Kanban view might have an implicit or explicit filter on the "Status Reason" field within each stage. For example, in the "Develop" stage, it might only show opportunities with specific status reasons relevant to that stage, even if their overall "Status" is "Open."

    2. User-Specific Views:

      • Personal Views: If the Read-Only view you're comparing against is a personal view, it might have different filtering criteria applied that you're not aware of when looking at the system Kanban view. Ensure you are comparing against the same system "Open Opportunities" view in both formats. 

    3. Filtering Applied in the Kanban View:

      • Manual Filters: Users can apply temporary filters directly within the Kanban view. Check if any filters are currently active that might be excluding some opportunities. Look for filter icons or dropdowns at the top of the Kanban view. 

    4. Sorting Differences:

       

       

      • While sorting wouldn't cause opportunities to disappear, it could affect your perception if you're expecting them to appear in a specific order while scrolling. The Kanban view has its own sorting order, which might be different from the Read-Only view.

    5. Performance Limits/Row Limits:

      • Client-Side Rendering Limits: In very large datasets, the Kanban view might have client-side rendering limitations that prevent it from displaying all records at once, especially in stages with a high number of opportunities like "Close." The "(shows 10/98) and shows all scrolled down)" for the Close stage suggests it is loading all 98, but the initial counts for other stages being lower than expected points to a filtering issue. 

    6. Customizations and Extensions:

      • Plugins or Client-Side Code: Custom plugins or client-side JavaScript running on the Opportunity entity or the Kanban view might be inadvertently filtering or modifying the data displayed. 

    7. Data Integrity Issues:

      • Inconsistent Data: While less likely to cause this specific behavior, inconsistencies in the "Sales Stage" or related status fields could lead to opportunities not being correctly categorized in the Kanban view.


        •  

      8.  

    Troubleshooting Steps:

    1. Verify the Underlying Views:

       

      • Identify the View Used by the Kanban: Determine the exact system view that the Kanban view is configured to use. You can usually find this in the customization settings for the entity's controls.

      • Compare FetchXML: Use the XrmToolBox (with a tool like "FetchXML Builder") to retrieve the FetchXML for both the Kanban view and the Read-Only view you're comparing against (ensure it's the same system "Open Opportunities" view). Compare the <filter> and <link-entity> elements for any differences in criteria.

    2. Examine Kanban Column Mapping:

      • Go to the customization settings for the Opportunity entity's controls and find the configuration for the Kanban control. Review how the "Status Field" (likely "Sales Stage") is mapped to the different Kanban columns. Ensure all relevant values from the "Sales Stage" option set are correctly mapped. 

    3. Check Status Reason Mapping (within Kanban Configuration):

       

      • Some Kanban configurations allow you to further filter by "Status Reason" within each lane. Verify if any such filters are applied that might be excluding opportunities.

    4. Review Any Applied Filters in the Kanban View:

      • Look for any active filter icons or dropdowns at the top of the Kanban view and clear them to see if all opportunities then appear. 

    5. Test with a System Administrator Role:

      • Log in as a System Administrator to rule out any potential security role or user-specific view issues. If the counts match for the administrator, then the problem might lie in view sharing or user-specific customizations. 

    6. Inspect Customizations (Plugins, JavaScript):

       

      • If you have any custom plugins registered on the RetrieveMultiple or Retrieve messages for the Opportunity entity, or any client-side JavaScript running on the Opportunity forms or views, temporarily disable them (in a non-production environment first!) to see if they are interfering with the data retrieval for the Kanban view.

    7. Analyze Data:

      • Run an Advanced Find query for all "Open" opportunities and include the "Sales Stage" and "Status Reason" fields in the results. Compare this list with what you see in the Kanban view for each stage to identify any patterns in the missing records. 

    8. Consider the "Close" Stage Behavior:

      • The "Close" stage showing all 98 when scrolled down suggests the data is being retrieved. This reinforces the idea that the issue in the other stages is likely a filtering or mapping problem, not a fundamental data access issue.


        •  

    In Summary:

    The most likely culprits are differences in the underlying FetchXML queries between the Kanban view and the Read-Only view, or incorrect mapping of "Sales Stage" values to the Kanban columns, or filtering applied within the Kanban configuration or manually by users. Start by carefully comparing the view configurations and FetchXML. If customizations are present, investigate them as potential sources of the discrepancy.

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
11manish Profile Picture

11manish 153

#2
ManoVerse Profile Picture

ManoVerse 147 Super User 2026 Season 1

#3
Jimmy Passeti Profile Picture

Jimmy Passeti 66 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans