Hello all,
I am repeatedly running into an issue where the Creatio Freedom UI page designer is showing a field under Data model attributes that is from a higher package in the hierarchy. The page I am working on does not depend on the page where the field is added but the page designer still thinks the field exists which is causing cyclical dependency errors every time I try to save the page even if I don't do anything to add the erroneous field to my page.
My page is properly placed in the lower package and connected with the version of the object within the same lower package. Why is Creatio disregarding my package structure and showing the field from a higher package? It's impossible to proceed when Creatio keeps making problems I'm trying to avoid.
Like
Hello,
The issue you are facing is related to how Creatio manages package dependencies automatically.
When you use elements from another package, Creatio adds dependencies which can sometimes lead to cyclic dependencies.
To resolve this:
-Review package dependencies - make sure your package does not depend (directly or indirectly) on a package that also depends on yours, creating a cycle.
-Adjust dependencies if needed - remove or rearrange package dependencies
-Verify current package setting - ensure you are working in the correct package and saving changes there.
-Refactor functionality if necessary — if the problematic field/functionality is not required in your package, consider moving it to a package where it won’t cause cycles.
Proper management of package dependencies and settings should help you avoid these cyclic dependency errors in Creatio.