Hello!

Could you please specify the issue you are facing?

Additionally, we were unable to view the picture you provided. Could you kindly resend it for us to review?

Thank you in advance, and we look forward to your reply!

Hello,

The checkbox becomes disabled when any modifications are applied to the detail schema in configurations, such as comments, custom methods, attributes, etc. This behavior is determined by the _canChangeType method in the DetailDesignerUtils module. The logic ensures that when the checkbox is disabled, the wizard does not save modifications applied to the base detail with a list schema, preventing any loss of changes.

This logic cannot be overridden, which is why the detail cannot be switched from an editable list detail to a standard detail if schema modifications are present.

To address this issue, you can choose one of the following approaches:

1. Remove the custom code, including comments, and save the changes. This will make the checkbox available again in the detail wizard.

2. Delete all methods and values associated with the edited detail's features from the detail schema. This will make the detail non-editable.

    

We would also like to highlight that this logic has been improved in the new FreedomUI designer. The updated designer addresses these nuances, allowing you to modify the attribute of the edited pattern with a single setting, without requiring additional code changes.

Hello,

You can create a metric in Freedom UI, and set up filtering on the Status-"New" column as well as Created on and specify the value you want. You can learn more about this using the articles below:
https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/ui-and-business-logic-customization/set-up-dashboards#title-184-4
https://academy.creatio.com/docs/8.x/creatio-apps/creatio-basics/view-analytics


Best regards,
Malika

Hello, 

Please note, that logging into Word Plugin with 2-factor authentication turned on is disabled for now, so please make sure it's turned off. Also make sure if the appropriate plugin version has been installed, verify if your System type is in compliance with plugin version 64 bit. 


Instruction for proper installation is available with this link: https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/print-ready-reports/install-creatio-plug-in-for-ms-word

Also use this insttuction to disactivate 2-FA, go to point 3 and instead of enabling it, please disactivate it: https://academy.creatio.com/docs/8.x/setup-and-administration/administration/user-and-access-management/authentication/set-up-two-factor-authentication

Thank you !

Hello,

The mentioned error indicates that the application cannot access the DB. 

Please double-check the access parameters specified in ConnectionStrings.config file. 

Best regards,

Arsenii

Hi,

To solve this business problem, you can implement validation before saving the page. You can read more about this solution in the articles:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/platform-customization/freedom-ui/customize-page-fields/examples/implement-the-field-value-validation

https://academy.creatio.com/documents/technic-sdk/7-16/how-add-field-va…

Hi Jacek,

The "Bubble map" type is available for only the Map chart. We will add this note to the listing description.

Olena Sidko,

Hi Olena,

Thanks for getting back on this. 

The thing is that when I add a new dashboard, I cannot see this 'Map chart' dashboard type. Would you know what could be causing this? 

All the nest in 2025! :-)
Jacek 

Hello! Would anyone have any idea why the 'Map chart' dashboard type is not listed? Thanks!

Jacek Harlejczyk,

Sorry for the delayed reply. The solution is now compatible with all Creatio products. Please install the updated version from the Marketplace and let me know if everything works as expected.

Have a good one!

Olena Sidko,

Thank you for your help. It's working now. 
Best!
Jacek

Hello,

You can try setting up a business rule in the mobile application to achieve the required functionality. Business rules allow you to dynamically populate the value for the Event field in the Lead object based on the specific user.

For guidance on how to create and implement business rules in the mobile app, refer to the following articles:

Mobile app business rules.
Custom business rules of the mobile application.

Alternatively, you can design a business process to achieve the same goal. A business process can calculate the appropriate value for the Event field and populate it when a record is created or updated in the mobile app.

More information regarding business processes is available here:

BPM tools.

Best regards,
Antonii.

Antonii Viazovskyi,

thank you for your answer.

Seems, it works only for Classic UI, but doesn't work for Freedom UI. We have tried to switch this checkbox on and off and found that.

If the fields were added in the designer, open the case object directly and do a publish and you’ll likely see the fields via the API. 
Ryan

Hello,

This error occurs because the data is not bound to the shown in the screenshot objects: "SysModuleEntity". Please follow the described steps to bind data and solve the error:

1. Create a "Data" element in your package. Example in screenshot below.

2. Select the SysModuleEntity object. Example in screenshot below.

3. On the "Bound Data" tab, add the id specified in the error. Example in screenshot below.


4. Save changes


Best regards,
Malika
 

Malika,

Thank you for your help!

Hello!

Thank you for the detailed description of the problem. The implementation you described assumes the use of a many-to-many relationship, which cannot be supported directly in the relational database structure.

Please note that in relational databases, the many-to-many relationship cannot be directly implemented because it violates the principles of the relational model, which is based on atomic data and normalization. Instead, such relationships are resolved using an intermediate (junction) table.

These are tables that reference two other tables and define the relationships between them. For instance, if we have Table 1 and Table 2, and we need to establish a multi-relationship between them (e.g., linking a record in Table 1 to multiple records in Table 2), we would create a junction table. This table would contain references to both tables and define the dependencies.

This approach allows us to implement a multi-selection mechanism, such as associating a product with multiple brands or categories (e.g., one product having three or more associated brands).

Here’s an example of how the table could look:

CompatibilityID    ProductID    BrandID
1                             101                1
2                             102                1

3                             101                2

Thank you Arsenii Ostapyk, that seems like it may be the solution to my problem. I have done a search through Creatio Academy for "junction" or "junction table". Can you point me in the right direction on where I can find information on how I go setting this up?

Julia Molnar,

Please note that we do not have any instructions or examples for this, since the question relates to the general Database structure principles, rather than to the Creatio system functionality. However, you are welcome to use the public open sources for more in-depth details on the subject.