{"title":"Analyzing web service publish failure telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-webservices-publish-failure-trace/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-webservices-publish-failure-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-webservices-publish-failure-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze web service publish failure telemetry in Business Central to investigate metadata generation errors and identify affected pages, controls, and fields.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing web service publish failure telemetry","slug":"analyzing-web-service-publish-failure-telemetry","at":0,"chars":8275},{"level":2,"title":"Web service metadata error: Name for subpage of parent page '{parentPageName}' is missing. Subpage is skipped.","slug":"web-service-metadata-error-name-for-subpage-of-parent-page-parentpagename-is-missing-subpage-is-skipped","at":656,"chars":1179},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":770,"chars":189},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":959,"chars":876},{"level":2,"title":"Web service metadata error: Control element with id '{metadataObjectName}' has a missing name. The page with the control was skipped.","slug":"web-service-metadata-error-control-element-with-id-metadataobjectname-has-a-missing-name-the-page-with-the-control-was-skipped","at":1835,"chars":1183},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":1972,"chars":210},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":2182,"chars":836},{"level":2,"title":"Web service metadata error: The record with name '{webserviceRecordName}' was skipped.","slug":"web-service-metadata-error-the-record-with-name-webservicerecordname-was-skipped","at":3018,"chars":1095},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":3108,"chars":165},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":3273,"chars":840},{"level":2,"title":"Web service metadata error: Table field name error, the page containing the field with caption '{metaFieldCaption}' was skipped.","slug":"web-service-metadata-error-table-field-name-error-the-page-containing-the-field-with-caption-metafieldcaption-was-skipped","at":4113,"chars":1152},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":4245,"chars":206},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":4451,"chars":814},{"level":2,"title":"Web service metadata warning: Multiple options while generation navigation property for tablerelation.","slug":"web-service-metadata-warning-multiple-options-while-generation-navigation-property-for-tablerelation","at":5265,"chars":1156},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":5371,"chars":181},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":5552,"chars":869},{"level":2,"title":"Web service metadata error: The record with name '{entityName}' was skipped.","slug":"web-service-metadata-error-the-record-with-name-entityname-was-skipped","at":6421,"chars":1038},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":6501,"chars":155},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":6656,"chars":803},{"level":2,"title":"Sample KQL code","slug":"sample-kql-code","at":7459,"chars":671},{"level":2,"title":"Related information","slug":"related-information","at":8130,"chars":145}],"text":"# Analyzing web service publish failure telemetry\n> APPLIES TO: Business Central 2023 release wave 1 and later\nWeb service publish failure telemetry gathers data when a web service couldn't be published or a published web service isn't working correctly due to an error in creating metadata for the web service. As a partner, the data gives you the ability to investigate and fix potential problems that are preventing a web service from working correctly.\nThe following sections explain the different events emitted during web service metadata generation, along with their dimensions. The tables list the dimensions that are specific to Business Central.\n## Web service metadata error: Name for subpage of parent page '{parentPageName}' is missing. Subpage is skipped.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata error: Name for subpage of parent page '{parentPageName}' is missing. Subpage is skipped.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0033\nmetadataStack|Specifies the entity where the error or warning has occurred.\nparentPageId|The ID of the parent entity object.\nparentPageName|The name of the parent entity object.\nsubPageEntity|The ID of the subpage entity.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Web service metadata error: Control element with id '{metadataObjectName}' has a missing name. The page with the control was skipped.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata error: Control element with id {metadataObjectName} has a missing name. The page with the control was skipped.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0034\nmetadataObjectId|The ID of the metadata entity\nmetadataObjectName|The name of the metadata entity object.\nmetadataStack|Specifies the entity where the error or warning has occurred.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Web service metadata error: The record with name '{webserviceRecordName}' was skipped.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata error: The record with name '{webserviceRecordName}' was skipped.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0035\nmetadataStack|Specifies the entity where the error or warning has occurred.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\nwebServiceRecordId|The ID of the web service record.\nwebServiceRecordName|The name of the web service record.\n## Web service metadata error: Table field name error, the page containing the field with caption '{metaFieldCaption}' was skipped.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata error: Table field name error, the page contaning the field with caption '{metafieldCaption}' was skipped.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0036\nmetafieldCaption|The caption of the metafield.\nmetaFieldId|The ID of the metafield.\nmetadataStack|Specifies the entity where the error or warning has occurred.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Web service metadata warning: Multiple options while generation navigation property for tablerelation.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata warning: Multiple options while generation navigation property for tablerelation.\nseverityLevel|2\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0038\nmetadataStack|Specifies the entity where the error or warning has occurred.\notherNavigationProperties|The list of all possible navigation properties.\npickedNavigationPropertyType|The final navigation property type.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Web service metadata error: The record with name '{entityName}' was skipped.\n### General dimensions\nDimension|Description or value\nmessage|Web service metadata error: The record with name '{entityName}' was skipped.\nseverityLevel|3\n### Custom dimensions\nDimension|Description or value\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\ncomponent|Dynamics 365 Business Central Server\ncomponentVersion|Specifies the version number of the component that emits telemetry. See the component dimension.\nerrorDetails|Details about the error.\nentityName|The name of the entity.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\neventId|RT0039\nmetadataStack|Specifies the entity where the error or warning has occurred.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Sample KQL code\nThis KQL code can help you get started analyzing and alerting on web service metadata errors.\n```kql\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId in ('RT0033','RT0034','RT0035','RT0036','RT0038','RT0039')\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, eventId = customDimensions.eventId\n, metadataStack = customDimensions.metadataStack\n, errorDetails = customDimensions.errorDetails\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Related information\ntelemetry-overview\nEnable sending telemetry to Application Insights<telemetry-enable-application-insights>\ntelemetry-alert"}