u/PoetExpert855

Hi everyone,

Is anyone else experiencing strange issues with Dataverse / Dataverse plugins since this morning?

Specifically, it looks like Dataverse may be returning or expecting the Schema Name instead of the Logical Name for some attributes inside plugins. This is breaking late-bound logic that expects column logical names.

Example:

var value = entity.GetAttributeValue<string>("new_customfield");

where new_customfield is the logical name. Since this morning, in some scenarios, it looks like something like new_CustomField — or the schema name equivalent — is being returned/required instead, causing null values, missing attributes, or unexpected plugin behavior.

This seems odd because, according to Microsoft’s Dataverse SDK documentation, late-bound code works with logical names. For example, Entity.LogicalName, AttributeCollection, GetAttributeValue<T>(), IOrganizationService.Retrieve, and metadata properties such as LogicalName are all based on logical names rather than schema names.

Context:

• Dataverse plugins in C#
• late-bound entities using Entity, Attributes, and GetAttributeValue<T>()
• attribute names no longer seem to match what the plugin expects
• no code changes on our side
• behavior appears to have changed suddenly this morning

Has anyone else seen this today?

Does anyone know whether Microsoft has rolled out an update, regression, or undocumented breaking change affecting Dataverse / Power Platform plugins?

Any workaround or confirmation would be appreciated.

Thanks!