Hello,
 

In version 8.1.1, the base page Calendar_FormPage was renamed to Calendar_ListPage in the product. 

If you had overrides for this page in your custom packages, the override will not be renamed, which will cause a structure generation error, as the schema inheriting from another schema will now have a different name.
 

You need to check if there is a schema named Calendar_FormPage in your system. If such a schema exists, rename it to Calendar_ListPage and also update the Define block in the page code accordingly.

Example:
Before

After


(Before this changes you need temporary clead SchemaNamePrefix system setting)
 

If the issue is not related to this, please contact our support team for assistance - support@creatio.com

Best regards,
Pavlo!

Hello, it works! Thank you very much :)
Is there any way to stay informed about such changes to avoid similar problems in the future? I didn’t find anything about this in the release notes.

Hi!

Please contact our support team at support@creatio.com and describe your situation to us. We will be happy to help you. 

Best regards,
Anton

Hello,

In this article, you can find the description of the page, on which the button component should be added.

Hello,

In Creatio, you can access the Schema details and make edits in the Configuration section

Hi community!

Any update on this issue ?

Sasori

Hello Sasori,



When dashboards are added to an edit page, the corresponding records are created in SysWidgetDashboard and SysWidgetDashboardLcz tables.



If a dashboard is added not to an edit page but to the "Dashboards" tab, then records will be added in the SysDashboard and SysDashboardLcz tables, respectively.

.

Also, there is also a corresponding binding of these data to the package which was set as a current package when the dashboards were created.



The thing is that dashboards are localizable system objects. When a dashboard is created, records are created in two tables:

- a record about a dashboard created in the localization, which corresponds to the base culture of the system, is created in the [SysWidgetDashboard]/[SysDashboard] table;

-records about dashboards of all other localizations are created in the [SysWidgetDashboardLcz]/[SysDashboardLcz] table and are linked to a record in the [SysWidgetDashboard]/[SysDashboard] table by the [RecordId] column.



So basically, all you need to do is to prepare a package which will contain all the needed data bindings and SQL scenarios which will perform the records' entry to the tables mentioned above.



More information on data binding is on our academy.

Also, knowledge of SQL might be needed in order to find the needed dashboard in the database, although you can always create a lookup and search via UI. 

If you think of it this way, which schemas are "text" that are easily understood by any 3rd party text editor? Client schemas are Javascript and source code schemas are C#. Both easily understood and editable by a text editor and can be edited by a 3rd party editor. However, object schemas in Creatio use a UI to add columns etc, it isn't just text. Also processes in Creatio have a complete UI process designer, it is not just text. Both objects and processes cannot be edited by a 3rd party editor since it wouldn't understand all the rest of the stuff the designer UIs in Creatio do. 

Ryan

Hello Sasori,

In order to deactive the filter based on employee it is just needed to click on the cross sign, and you will see all the accounts.

Alternatively you can create a replacing view model for the schema PlanningAccountDetailV2 and modify the method getFilters according to your needs.

 define("PlanningAccountDetailV2", [],

    function() {

        return {

            entitySchemaName: "Account",

            attributes: {},

            methods: {

                getFilters: function() {

                     this.callParent(arguments);

                    var filters = this.sandbox.publish("GetSectionFilters");

                    if (!this.Ext.isEmpty(filters.filtersValue)) {

                        this.setFilter(filters.key, filters.filtersValue);

                    }

                }},

            diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/

        };

    }

);

As for the section wizard, this whole detail was created with code, so it would be not possible to enable it. But the first option by clicking the cross sign would be the more simple one.

Best regards,

Dariy

 

Thank you very much Dariy.

Hello Pascal,

unfortunately this is not quite possible.

The thing is that you can export the DB in such way, but you will not have any objects in the system.

So we would recommend sticking to the standard way. Also, we will register this option as a wish for the dev team to implement it in the future.

Regards,

Gleb.

Hello,

You can check the LocalizableStrings in the config section.

To do this, you need to open your schema and check the Localizable strings tab:

Cherednichenko Nikita,

Hello, I understand how to check the LocalizableStrings in the schema.



But there are a lot of them. So, how to find, which one was changed?



Thank you.

Vladimir