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

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested answer

In-App Notification - Dismiss All

(2) ShareShare
ReportReport
Posted on by 9

Hello

Problem when users get in-app notification and then press "dismiss all" button.

After clicking button, notifications disappearing as it needed, but some seconds after all notifications are coming back.

What may be wrong ? 

We do not get replicated this issue on our dev environment, but it happens in Production.

I have the same question (0)
  • kar424 Profile Picture
    5 on at
    RE: In-App Notification - Dismiss All

    Hey AllarS , I'm running into the same issue. Were you able to resolve this?

  • HectorMeneses Profile Picture
    30 on at
    RE: In-App Notification - Dismiss All

    Hi AllarS,

    We are facing this issue as well. We noticed that if you click the x button for each notification that a call to delete the notification is generated. We found that because our users did not have the prvDeleteappnotifications permission and an error was being reported in the browser's developer tool console. Once we added the permission we stopped seeing the error in developer tools.

    However, we still getting the notifications back as you are reporting. So, it looks like something in the backend data source for in app notifications is not working as expected. In App Notifications are virtual entities so we were also not able to see any audit logging for them. 

    I hope this can help to get closer to the source of this issue.

  • Suggested answer
    Joost vL Profile Picture
    on at
    RE: In-App Notification - Dismiss All

    Hi AllarS,

    With help of the console app in the browser I came across a permission error.

    The dimiss all button triggers the: "model-driven app user setting" table.

    If you copy these permissions users will be able to dismiss all notifications at once!

    Happy building,

    Joost

  • MM-02040739-0 Profile Picture
    8 on at
    In-App Notification - Dismiss All
    I am getting the same error and its been 2 years since this was reported. Was this resolved? What was the solution?
  • Suggested answer
    Daivat Vartak (v-9davar) Profile Picture
    7,835 Super User 2025 Season 2 on at
    In-App Notification - Dismiss All
    Hello AllarS,
     

    This is a frustrating issue, especially when it only occurs in your production environment. Here's a breakdown of potential causes and troubleshooting steps for notifications reappearing after dismissing all in Dynamics 365:

    Likely Causes:

    1. Asynchronous Processes (Workflows, Power Automate Flows): This is a very common culprit. You might have a background process that is:

      • Re-triggering the notifications: Even after they are dismissed, a workflow or flow might be evaluating conditions and re-creating or re-displaying the same notifications.

      • Updating a record that triggers the notifications again: If the notifications are tied to specific record changes, a background process running shortly after dismissal might be modifying those records, causing the notification rules to fire again. 

    2. Client-Side Scripting (JavaScript on Forms or Web Resources): Custom JavaScript code running on forms or within web resources might be interfering with the notification dismissal process or inadvertently re-fetching and displaying them.

    3. Incorrect Configuration of Notification Rules: Review the configuration of your in-app notification rules. Ensure the triggering conditions are specific enough and that there isn't a broad rule that gets re-evaluated and re-fires quickly after dismissal.

    4. Caching Issues (Less Likely but Possible): While less common for this specific behavior, there could be some form of client-side or server-side caching that is temporarily hiding the dismissed notifications and then refreshing with the old state.

    5. Intermittent Network Issues: Unstable network connectivity could potentially cause the dismissal action to not fully propagate or a delayed re-sync of notification status. However, this is less likely to cause a consistent reappearance after a few seconds.

    6. Conflicting Solutions or Customizations: If you have multiple solutions or significant unmanaged customizations in your production environment that are not present in development, there might be a conflict causing this behavior.

       


    7.  

    Troubleshooting Steps:

    1. Focus on Asynchronous Processes:

      • Review Background Workflows: Go to Settings > Processes and examine all active workflows, especially those related to the entities for which users are receiving notifications. Pay close attention to workflows that run on record creation, update, or on a schedule. Deactivate any non-essential workflows temporarily in production (with proper change management) to see if the issue resolves.

      • Examine Power Automate Flows: Check your Power Automate flows (both in "My flows" and "Team flows" if applicable) for any flows that might be creating or interacting with in-app notifications or the data that triggers them. Monitor the run history of relevant flows in production.

      • Check for Recurring Jobs/System Jobs: Look in Settings > System Jobs for any recurring system jobs that might be related to notification generation or data updates. 

    2. Investigate Client-Side Scripting:

      • Review Form Customizations: Open the forms where users are likely seeing these notifications and examine any associated JavaScript web resources. Comment out custom JavaScript code (again, with proper change management in production) temporarily to see if it's the cause.

      • Check Web Resources: Review any other JavaScript web resources that might be running globally or on specific events and could be related to notifications. 

    3. Analyze Notification Rule Configuration:

      • Go to Settings > Customizations > Customize the System > Entities > [Relevant Entity] > Business Rules. Look for any business rules that create or display in-app notifications. Review their conditions and actions carefully.

      • Go to Settings > Customizations > Customize the System > Entities > [Relevant Entity] > Processes. Look for real-time workflows that create notifications. 

    4. Compare Production and Development Environments:

      • Solution Differences: List the managed and unmanaged solutions present in production that are not in your development environment. There might be a customization in one of these solutions causing the issue.

      • Data Differences: While the issue isn't data-specific in its manifestation, significant data volume or specific data patterns in production could be triggering a process differently than in your smaller dev environment. 

    5. Enable Auditing (If Not Already Enabled): Turn on auditing for the relevant entities and fields involved in the notifications. This can help you track data changes that might be triggering the notifications. Review the audit logs after the notifications reappear.

    6. Monitor System Jobs and Background Processes: Use the System Jobs area to monitor the status and details of background processes running in production around the time the notifications reappear. Look for any failed or unusually long-running jobs.

    7. Isolate the Triggering Entity/Scenario: Try to identify if the reappearing notifications are related to a specific entity or a particular user action. This can help narrow down the area to investigate.

       


    8.  

    Steps to Take in Production (Be Cautious):

    • Implement Changes During Off-Peak Hours: Any deactivations or code modifications should be done when users are least active.

    • Back Up Your Production Environment: Before making any significant changes, ensure you have a recent backup of your production environment.

    • Communicate with Users: Inform users that you are investigating the issue and might be making temporary changes.

    •  

    Debugging in Production (More Complex):

    • Plugin Profiler: If you suspect a plugin is involved (though less likely for in-app notifications directly), you could try using the Plugin Profiler in production (with extreme caution and for a limited time) to trace the execution of plugins related to the notification entities.

    • Monitoring Tools: Utilize any monitoring tools you have for your Dynamics 365 environment to track performance and potential errors around the time the notifications reappear.

    •  

    By systematically investigating these potential causes in your production environment, you should be able to identify the process or customization that is causing the dismissed notifications to reappear. Start with the asynchronous processes as they are the most frequent culprits for this type of behavior. Good luck!

     
    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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 117

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 117 Super User 2025 Season 2

#3
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 83

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans