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.

You can lock the fields in the editable detail using business rules on the page for the detail, rather than in code. On the page for the detail, add a business rule to make the field not editable. Something like 
Condition: Boolean true = Boolean false (something that is never true)

Then: Make field editable (the condition is never true, so field is never editable)

The business rule will apply to the detail list and the fields will not be editable in the detail list.

Ryan

Hi Ryan,
I'm actually working with the BaseGridDetail so I can't lock it with a business rule... do you have any other idea?

Thanks anyway.

Luca

Luca Tavasanis,

IIRC to do it in code I usually do it like this (but unable to verify if this is correct at the moment)

getCellControlsConfig: function(entitySchemaColumn) {
    // get config from base 
    var config = this.callParent(arguments);
    var columnName = entitySchemaColumn.name;
 
    // if this is the column I want to disable
    if (columnName === "UsrMyColumn") {
        Ext.apply(config, {
            enabled: false
        });
    }
 
    return config;
}

Hopefully that gets you closer, of course, if you're wanting to disable all, you could just remove the if to check the column it's for.

Ryan

Ryan Farley,

I just tried what you suggested but unfortunately it's not working... it returns an error when I use this.callParent(arguments);.
Thank you anyway.

Luca

Luca Tavasanis,

While I was debugging I have noticed that the properties of the labelConfig that enabled some of the fields where added in the method: "applyBusinessRulesForActiveRow: function(id, gridLayoutItems)" and to fix the issue I just added this method in the client module.

Hi,

There is an easier way to achieve a custom precision for the column: in the grid detail schema you need to override the getGridRowViewModelConfig method. For example I've created a replacing view model for the OrderProductDetailV2 and specified the following code there:

define("OrderProductDetailV2", ["MoneyModule", "css!OrderPageV2Styles", "css!SummaryModuleV2"], function(MoneyModule) {
	return {
		entitySchemaName: "OrderProduct",
		messages: {},
		attributes: {},
		methods: {
			getGridRowViewModelConfig: function(config) {
				var gridRowViewModelConfig = this.callParent(arguments);
				gridRowViewModelConfig.rowConfig.UsrDecForTests.precision=6;
				return gridRowViewModelConfig;
			}
		},
		diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/
	};
});

In this case all the values in the precision for the "UsrDecForTests" decimal column (that is Decimal (0.00000001) data type) in the "Products" detail on the order page will be set to 6:

and

and

So you can try the following approach on your end.

Best regards,

Oscar

That's exactly what I needed. Thank you, Oscar!

Dear Marcin,

As for now, there is no workaround to increase the number of columns in grid view. I recommend using the tile view. For this view, it`s possible to more flexibly adjust the number of displayed columns and their size.

Best regards,
Angela

Hi Angela,

Angela Reyes writes:

Dear Marcin,

As for now, there is no workaround to increase the number of columns in grid view. I recommend using the tile view. For this view, it`s possible to more flexibly adjust the number of displayed columns and their size.

Best regards,
Angela

MoreLess

1 page only 2 records (if you have more than 50 fields, 1 record in 1 page)

24 fields list view, cannot see any things - cannot remove field after add 24 fields in settings

Hope that Creatio improve horizon scroll for list view, and user can adjust wide column without open list setup page.

Regards,

Akira Nguyen

Hi,

Yes, You have a right but for this i have solution (even two or both of):

- in case of horizontal scrolling have a look how to achive this on grid

https://community.creatio.com/ideas/horizontal-view-section-and-detail

- in case of expand visibility of grid You may use add'on

https://marketplace.creatio.com/app/expandable-details-creatio

So only what i'm looking for is the possibility to increase list view column limitation.

Regards,

Marcin

Hi Ramnath.

You can change the font size by adding a custom css style to the schema you need and in such a way override the system font-size. Please refer to this article on our community: https://community.bpmonline.com/questions/how-add-custom-style-control-page-based-condition
I recommend you change a font-size first for any page in the system to check if it looks fine as we do not guarantee that all objects, labels, and containers will be displayed correctly. 

Thank you.

Bohdan Zdor,

I have tried this before but I could only make it work on the page of arecord. I need to edit the page where all the records are shown. I could not find the module which has the code for the list of records.

Ramnath

RAMNATH SHARMA,

Unfortunately, there is no option to change the section list font size in the current version of the system. I have registered your suggestion, though. It was passed to our R&D team to be considered for further releases.

Thank you.