How to Resolve “Form Model Parent Reference” Error During Dynamics 365 Finance and Supply Chain Management Upgrade
Recently, our team was helping a client update to Dynamics 365 Finance and Supply Chain Management version 10.0.42 when the following error came up with an ISV they were using.
The initial developer investigating this issue had encountered this error before, and it is usually resolved by re-creating the form extension. They tried that method, but it didn't address the error. Upon further investigation, they found that they didn't need to add any controls to the form extension; they just needed to create the form extension and build the project to receive the error.
Our Dynamics 365 Finance and Supply Chain Management support team tried everything to resolve the error, but nothing worked. After finding no documentation about the error online, I submitted a support ticket to Microsoft, hoping they had seen this issue previously.
The Fix: Working Alongside Microsoft
Our team worked with the Microsoft support engineer to condense the issues down to the following scenario:
- Model A – extends SalesTable adding a button group
- Model B – References Model A – extends SalesTable by adding a button in the button group from Model A.
- Model C – References Model B – build throws the error
The support engineer created the scenario and tried to fix it by adding a reference in Model C to Model A. This method, however, did not resolve the issue when applied to the client's environment.
We spent more time troubleshooting with the client's models metadata, including the ID, the Layer, and what models were referenced by the models involved with the error. Ultimately, Microsoft could only reproduce the issue with the client's models.
For reference, the IDs for the three models were the following:
- Model A Id: 995983529
- Model B Id: 995983528
- Model C Id: 896000508
Follow These Steps to Resolve the "Form Model Parent Reference" Error
The Microsoft support agent provided the following method to help us fix the issue for our client.
- Stop all services for D365 on the box and IIS
- Delete the BIN folder from inside the Model A and Model B models in packageslocaldirectory folder
- Change the model ID on the Model B model to a larger number:
- In Visual Studio, build the Model B model by itself
- Then, build the Mold A model by itself
- After that, you should be able to build the projects in the Model C mode
Seeing as there is no documentation online about this error, I hope this can guide anyone who encounters this error in the future so they can save themselves some time.
Get in Touch with Stoneridge Today to Learn More About Addressing Software Errors
Software bugs and errors during implementation or upgrades are expected, and working with a trusted partner can help you address these issues quickly. Talk to the Stoneridge team today to learn more about how our experts can support you.
Under the terms of this license, you are authorized to share and redistribute the content across various mediums, subject to adherence to the specified conditions: you must provide proper attribution to Stoneridge as the original creator in a manner that does not imply their endorsement of your use, the material is to be utilized solely for non-commercial purposes, and alterations, modifications, or derivative works based on the original material are strictly prohibited.
Responsibility rests with the licensee to ensure that their use of the material does not violate any other rights.