You may encounter an issue when converting a detail into a section, where the pages do not change as expected. In the wizard, it appears as if it's a section, but the actual page that opens is the details page.

The issue was caused by the feature of the architecture of interaction of schemes in the application. The object will be able to contain one Edit page or more if the page type is enabled (different pages are designed for different use cases based on the information that is filled in while creating a record). The current configuration only permits the addition of one page to both a section and a detail of an object. The described situation arose because the detail page was created before the added section. As a result of creating a section, two pages were added for the object in the system tables.

Upon opening the wizard, the system returns the first random page from the select query. This is why you may not see the correct page in the wizard.



For the solution, I recommend saving one page for the detail and for the section.

To achieve this, you should delete the record from the system tables and then re-save the edit page:

1) Find all edit pages for the problem object using this script:

select * from "SysModuleEdit"
where "SysModuleEntityId" in (
select "Id" from "SysModuleEntity"
where "SysEntitySchemaUId" in (
select "UId" from "SysSchema"
where "Name" = 'objec_code'));

2) Find and delete the detail edit page:

delete from "SysModuleEdit" where "Id" = 'id_detail_schema';

Before deleting, make sure to save the value from the 'SysEntitySchemaUId' column.

3) Delete the record in the table that connects the edit page and detail itself:

delete from "SysModuleEntity" where "Id" = 'id_SysEntitySchemaUId_step_2';

4)  Re-save the edit page using the section wizard.

As a result, you will be left with one edit page for detail and section.

You can face the issue when some changes that you made in the section wizard aren't displayed on the page.

This can occur if the package set in the 'Current Package' system setting is not the last one in the hierarchy (typically 'Custom'), and changes have been made in packages lower in the hierarchy.

The Section Wizard displays the content of all the schemas till the package is indicated in the "Current package" system setting.

However, UI displays the content and logic from all the schemas of all the packages.

To confirm this, you can change the value of the "Current package" system setting to the "Custom" package.

The "Custom" package contains all dependencies of all packages of the application. All columns are the same and are visible both on UI and in the Section wizard once it's set as the current package.

Let's consider this in the example of the package dependency schema and how it will affect the display when setting a package different from the Custom Package:

​

In the provided schema, the Custom package is at the bottom and contains all of the dependencies from the schemas above it. However, if a different package is specified in the Current Package system setting, then it will be higher in the hierarchy and will not include any changes from the schemas below it. As a result, these changes (fields, details, etc.) will not be displayed in the section master but will be visible in the interface.

To resolve this issue, I recommend reviewing the dependencies of packages, establishing the correct hierarchy, and adjusting the 'Current Package' system setting as needed.



You can learn about package dependencies and hierarchy in this article on the Creatio Academy: 

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…