Finance | Project Operations, Human Resources, ...

Model Build Error in New D365 Finance DEV Environment (10.0.47 / PU71)

(0) Share

Report

Posted on by Ashleyyri

I recently deployed a new D365 Finance Cloud-hosted DEV environment running Application Version 10.0.47 with Platform Update 71.

During environment configuration, specifically during the model build step, I am receiving the following error while selecting a customization model build.

Path: [AxFormExtension/AccountingSourceExplorer.<MyCustomModel>/Controls/FormExtensionControlwxalvytg1/PreviousSibling]:
For form extension control 'FormExtensionControlwxalvytg1', its previous sibling 'AccountingSourceExplorerFileExport' was not found as a child control of 'AccountingSourceExplorerActionButtons'.

Additional details:

Started Visual Studio on the DEV environment.
Connected to Azure DevOps and mapped the workspace.
Selected the vendor-developed customization model during environment configuration.
The model build fails with the error above.
Rebuilding a new environment did not resolve the issue.

Has anyone encountered this issue on Application Version 10.0.47 / Platform Update 71, or have any recommendations for troubleshooting form extension control references during a model build?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Subra 1,090 on at

Like (0)

Report
Copy link

Link copied!

Hi @Ashleyyri

Could you please let us know did you created any extension in your custom model. if yes, that is causing the issue. Kindly remove your control check.

I hope MS has done few changes with that form but you have to change your customization based on that. Might be MS has moved metadata or removed from the parent form.

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Ashleyyri 8 on at

Like (0)

Report
Copy link

Link copied!

Thank you, Subra!!

The extension was developed by our vendor. I reviewed the base form AccountingSourceExplorer and can see AccountingSourceExplorerFileExport under AccountingSourceExplorerActionButtons. However, the build continues to fail..

Is there a way to determine whether Microsoft changed the metadata hierarchy or control type in this form between versions, causing the PreviousSibling reference to fail even though the control is present in the base form?

Was this reply helpful? Yes No