Electronic reporting (GER) framework allows to design an abstract data model describing certain business domain. A new GER data model element can be created as inheriting the structure from another model’s element via reference to a parent element. This inheritance includes the re-usage of multi-lingual labels and descriptions of referenced element. For instance, the new Vendor element can refer to the Party element to re-use the structure that has been initially designed when the Customer element has been introduced. Model designer of GER framework validates the created model to prevent situations when a model element is finally referenced to itself to avoid the appearance of endless loops while model’s elements and corresponding artifacts are loading to the Dynamics 365 for Operations application. For instance, when GER model labels are loading individually for each model’s element of importing GER data model.
However, since the created data model can be exported from GER framework as XML document representing a GER data model configuration that can be manually adjusted, the self-referencing loop situation can be met when such GER configuration is imported from XML file to the Dynamics 365 for Operations application. In such case self-referencing loop can be detected and you may get the unexpected stack overflow error message accordingly.
To work around this issue, consider the usage of GER framework only for editing GER data models.