Skip to content

fix: include extension fields in Invoke-D365GenerateReportDataEntityField (#649 follow-up) - #915

Open
pavankadabala-png wants to merge 1 commit into
d365collaborative:masterfrom
pavankadabala-png:fix/649-report-data-entity-field-extension-fields
Open

fix: include extension fields in Invoke-D365GenerateReportDataEntityField (#649 follow-up)#915
pavankadabala-png wants to merge 1 commit into
d365collaborative:masterfrom
pavankadabala-png:fix/649-report-data-entity-field-extension-fields

Conversation

@pavankadabala-png

Copy link
Copy Markdown
Contributor

Follow-up to #910 (issue #649), per @FH-Inway's request to also cover Invoke-D365GenerateReportDataEntityField / Get-AxDataEntities.

Invoke-D365GenerateReportDataEntityField builds its report through the internal Get-AxDataEntities, which still read each entity with DataEntityViews.Read($elementName), so fields added to an entity via extensions were omitted from the field-level report. This applies the same fix #910 made to Invoke-D365GenerateReportDataEntity, switching the read to the extension-aware ReadDataEntityViewWithExtensions call.

ExtensionMethods lives in the Microsoft.Dynamics.AX.Metadata.Storage assembly already loaded by Import-GenerateReportAssemblies, so no new dependency is introduced. This is an internal-helper change only, with no public parameter or help changes. (The diff also normalizes a missing end-of-file newline that the web editor added automatically.)

Refs #649, #910

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants