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 :
Small and medium business | Business Central, N...
Suggested Answer

Custom Telemetry not working properly since latest update

(2) ShareShare
ReportReport
Posted on by 45
Hi
 
Since the Platform update 24.0.25684.0, the custom telemetry is not storing the values sent in the CustomDimensions list, I can see the message and the eventid but not the ones in the customDimensions list.
Has it changed the way we must send this information or is it some kind of bug?
 
regards
I have the same question (0)
  • Khushbu Rajvi. Profile Picture
    22,435 Super User 2026 Season 1 on at
  • Suggested answer
    DAnny3211 Profile Picture
    11,421 Super User 2026 Season 1 on at

     

    Hi Oscar,

    Thanks for raising this — you're not alone in noticing changes in custom telemetry behavior after the Platform update 24.0.25684.0.

    Here's what you can check:

    1. Telemetry Schema Changes:

      • Microsoft occasionally updates the Application Insights schema or how customDimensions are handled.
      • Review the latest telemetry documentation to confirm if any changes were introduced in this platform version.
    2. Payload Format:

      • Ensure that your telemetry payload still conforms to the expected structure:
    Telemetry.Trace('YourEventId', 'Your message', customDimensions);
      • The customDimensions dictionary must contain string key-value pairs only.
    1. Instrumentation Key vs. Connection String:

      • If you recently switched from using an Instrumentation Key to a Connection String, ensure the configuration is still valid and supports custom dimensions.
    2. Application Insights Configuration:

      • Check if your Application Insights resource has any filters or sampling rules that might be excluding customDimensions.
    3. Known Issues or Bugs:

      • If everything appears correct, this could be a regression or bug introduced in the platform update. Consider opening a support ticket with Microsoft or checking the Business Central release notes for any known issues.

    Let me know if you'd like help reviewing your telemetry code or setting up a test trace!

    Please verify if this response was helpful.

    Best regards!

  • Suggested answer
    YUN ZHU Profile Picture
    101,202 Super User 2026 Season 1 on at
    Hi, As far as I know this is a standard issue and has been fixed in 24.0.25791. You can download the latest CU and try again.
    More details:
     
    Thanks
    ZHU

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 April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,233 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,360 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,216

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans