It turns out the problem was that I did not publish the new object before compilation. After publishing and compiling once more the lookup works correctly with the new column!

Hello,

You need to create one-to-many relations between these objects. To do this, you need to create a lookup column in each object that will refer to another object. After that, you will be able to use filters and relationships to display and customize the necessary lists.
You can't do it using no-code elements because this connection is set up at the object level.

Dear Andreas,

For the grid container, the size of one column will always depend on the size of the grid. For example, you have a 100x100 px grid with 2 columns, the grid will be divided into 2, each column taking a half of the space (with spacing specified in settings). You can of course take up a whole space with the element if needed.

You can modify the column set up in the grid container with system definer sizes like "small", "medium", "large" in the column spacing for example:

You can read more about the grid container set up on Creatio Academy: https://academy.creatio.com/docs/8.x/no-code-customization/customizatio…

You can also use a flex container for a more flexible set up: https://academy.creatio.com/docs/8.x/no-code-customization/customizatio…

Have a great day!

Alina Yakovlieva,

Hi Alina,

To clarify, my question was related to the list component, not the layout grid.

As it stands, the list component allows me to manually set the width of each column. However, this width can only be defined using a fixed size (like pixels), not percentages. This fixed sizing leads to two main issues:

1. On smaller screens: The content doesn't fit the screen width, resulting in the addition of a horizontal scrollbar.
2. On larger screens: There's excess white space to the right of the last column, as the columns do not expand to use the available width.

My goal is to have the column widths dynamically adjust to the screen size, utilizing percentages to ensure they fill the entire width of the list component, without unnecessary scrollbars or white space.

Is there a way to make the columns within the list component responsive, so that their widths adjust in proportion to the screen size, using percentages instead of fixed sizes?

Any guidance or suggestions on how to achieve this would be greatly appreciated.

Thank you!

Hello,

SQL scripts can be utilized to implement the transfer of organizational structure settings and access rights from one environment to another. To do this, insert queries need to be generated on the reference environment based on records from the following tables:

• SysAdminUnit (Administration object: users and roles)
• SysUserInRole (Direct user role assignments)
• SysFuncRoleInOrgRole (Functional role assignments to organizational roles)
• SysAdminOperation (System operations, if necessary)
• SysAdminOperationGrantee (Access to system operations, if necessary)
• SysEntitySchemaOperationRight (Access to objects)
• SysEntitySchemaRecordDefRight (Access to default records)
• SysEntitySchemaColumnRight (Access to object columns)
• SysAdminUnitGrantedRight (Delegation)
• SysWorkplace – (User workplace)
• SysAdminUnitInWorkplace – (Users in the workplace)
• SysModuleInWorkplace – (Module in the workplace)

You can use Microsoft SQL Server Database Publishing Wizard or similar tools to generate queries. The resulting SQL script should be attached to the package. If the transfer is happening to a production environment, we recommend making a backup of the data beforehand and primarily deploying the package to a test environment to verify the script execution results. These tasks should be performed outside of business hours.

Hello!

Perhaps the cache of the browser has an effect on column display.

Could you kindly verify the page in incognito mode?

To make a column mandatory in FreedomUI, you can follow these steps:

1. Identify the column you want to make mandatory in the detail view of your form.

2. Open the code or configuration file associated with your FreedomUI implementation.

3. Locate the section or code block related to the detail view of your form.

4. Find the column you want to make mandatory within the code or configuration.

5. Depending on the specific implementation of FreedomUI, you can typically add a validation rule or attribute to the column to make it mandatory.

6. Add the necessary code or configuration to enforce the mandatory requirement for the column. This may involve setting a "required" flag, adding a validation rule, or specifying a validation message.

7. Save your changes and test the form to ensure that the column is now mandatory in the detail view.

It's important to note that the exact steps may vary depending on the version and customization of FreedomUI you are using. Refer to the documentation or consult with the developers or support team of FreedomUI for specific guidance on making a column mandatory in the detail view.



More detail : https://360degreecloud.com/

Hello Oliver,

The method described in the article you mention does work for me (In fact, I just did this yesterday with no issues). 

Make sure that you've first configured the column layout and selected the "save for all users" and that you're selecting the correct row from the SysProfileData table (the one with no user in the "Contact" column.

If it's not working for you, it's likely one of the two issues listed above. 

Ryan

I appreciate the confidence in your article but I have 100% done both of these, about a thousand times, in every way possible.

Is this the only known solution/ there are no known issues with this?

Hi,

There is a script that safely removes all duplicates in the table SysProfileData, you can use it:

delete

from "SysProfileData"

where "Id" in

  (

  select uuid(min("Id"))

  from "SysProfileData" 

  where "Key"<>'' and "Key"<>'chrome'and "Key"<>'gecko'

  group by "Key","ContactId", "SysCultureId"

  having count (*) > 1

  )

Hello,

The most likely reason for such behavior is that you need to update your database structure and re-create the original business process.

To update your database you need to go into the configuration settings and click on "Update database structure where needed" under the action menu.

By re-create we meant that, unfortunately, you will have to create a new business process because the original one might still keep looking for an already deleted column.

If  you are still having issues, please feel free to contact our support by writing us an email at support@creatio.com

Thank you.

Hello Sivaranjani,

It happens because the code above returns the "Title" column caption only and if your object doesn't have the column with such a name the result is null.

You need to use something like:

var columnCaptionsArray = activityEntity.Schema.Columns;
    foreach (var columnCaption in columnCaptionsArray)
    {
    	var captionForColumn = columnCaption.Caption.Value;
    }

and use the captionForColumn in your logic furhter.

Best regards,

Oscar

Oscar Dylan,

Thanks for the reply. The above code is working.