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

Hello Mohammad, 

Please, try to set up the title for the button by using the code:

"caption": resources.localizableStrings.DetailsCaption

Let us know in case any additional information is required. 

Best regards,

Olga. 

Olga Avis,

Thank you so much. It worked perfectly

Hello Fulgen,

This is an out-of-the box logic of our application so that IDs of elements on the page are generated randomly when refreshing the page. Currently there is no way to modify this logic since it is set in core application schemas and binary files of the application. We already have a problem registered to our R&D team so they could add some extra logic that allows static IDs of elements on the page (since request like that was asked to integrate Creatio application with PRA tools like UiPath).

The only possible way to achieve your task is to use data-item-marker since values there are static and doesn't modify after each refresh of the page. For example data-item-marker for global search window is "command-line".

Best regards,

Oscar

Oscar Dylan,

Thanks Oscar,



I just noticed like in Product Section data item marker is the product name, if there are duplicate product name data item marker will not be unique. Is there a way I can modify the data-item-marker of each row, i will give the guid of the record instead of the name? Please give me example how to do it. Thank you so much

Hello,

It is not possible to modify "data-item-marker" of the edit page (it is being generated) and we don't have a particular example of such an implementation. 

Best regards,

Oscar

Unfortunately, there is no good way to create sticky header while scrolling through the grid. After freezing header row in the grid all other blocks on the page need to be adjusted in order the page is displayed properly.

It's a very strange idea to stop using multithreading - one of the most powerful JS features. Please make sure that you need this. 

Anyway, details are loading asynchronously and they don't have an "onDetailLoaded" event. One of the latest loading methods will be "onGridDataLoaded" in the BaseGridDetail. Please feel free to use it as an indicator of the fact that a detail was loaded. 

In order to indicate a complete loading of all details please use threading control on a page. Please find more information about threads in the article by the link below.

https://stackoverflow.com/questions/30036/javascript-and-threads

Hello Darian,



Actually, here is an article that describes how to achieve it:

https://academy.bpmonline.com/documents/technic-sdk/7-13/adding-detail-…



Also I have tested it on my local instance, here is an example how to do it with OpportunityProductDetailV2.



1. Create replacing client module for it

2. Put the code from below and save the schema.

 

define("OpportunityProductDetailV2", ["ConfigurationGrid", "ConfigurationGridGenerator",
    "ConfigurationGridUtilities"], function() {
    return {
        entitySchemaName: "OpportunityProductInterest",
        attributes: {
            
            "IsEditable": {
       
                dataValueType: Terrasoft.DataValueType.BOOLEAN,
               
                type: Terrasoft.ViewModelColumnType.VIRTUAL_COLUMN,
                value: true
            }
        },
        mixins: {
            ConfigurationGridUtilities: "Terrasoft.ConfigurationGridUtilities"
        },
        diff: /**SCHEMA_DIFF*/[
            {
                "operation": "merge",
                "name": "DataGrid",
                "values": {
                    "className": "Terrasoft.ConfigurationGrid",
                    "generator": "ConfigurationGridGenerator.generatePartial",

                    "generateControlsConfig": {"bindTo": "generateActiveRowControlsConfig"},
                    "changeRow": {"bindTo": "changeRow"},
                    "unSelectRow": {"bindTo": "unSelectRow"},
                    "onGridClick": {"bindTo": "onGridClick"},
                    "activeRowActions": [
                        {
                            "className": "Terrasoft.Button",
                            "style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
                            "tag": "save",
                            "markerValue": "save",
                            "imageConfig": {"bindTo": "Resources.Images.SaveIcon"}
                        },
                        {
                            "className": "Terrasoft.Button",
                            "style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
                            "tag": "cancel",
                            "markerValue": "cancel",
                            "imageConfig": {"bindTo": "Resources.Images.CancelIcon"}
                        },
                        {
                            "className": "Terrasoft.Button",
                            "style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
                            "tag": "remove",
                            "markerValue": "remove",
                            "imageConfig": {"bindTo": "Resources.Images.RemoveIcon"}
                        }
                    ],
                    "initActiveRowKeyMap": {"bindTo": "initActiveRowKeyMap"},
                    "activeRowAction": {"bindTo": "onActiveRowAction"},
                    "multiSelect": {"bindTo": "MultiSelect"}
                }
            }
        ]/**SCHEMA_DIFF*/
    };
});

Alex_Tim,

I have done that, but it doesn't make a difference.  It does function as expected with OpportunityProductInterest, but OrderProduct still requires using ...->New to get a new line.

REf:

define("OrderProductDetailV2", ["ConfigurationGrid", "ConfigurationGridGenerator",
	"ConfigurationGridUtilities"], function() {
	return {
		entitySchemaName: "OrderProduct",
		attributes: {
			"IsEditable": {
				dataValueType: Terrasoft.DataValueType.BOOLEAN,
				type: Terrasoft.ViewModelColumnType.VIRTUAL_COLUMN,
				value: true
			}
		},
		mixins: {
			ConfigurationGridUtilities: "Terrasoft.ConfigurationGridUtilities"
		},
		details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
		diff: /**SCHEMA_DIFF*/[
			{
				"operation": "merge",
				"name": "DataGrid",
				"values": {
					"className": "Terrasoft.ConfigurationGrid",
					"generator": "ConfigurationGridGenerator.generatePartial",
					"generateControlsConfig": {"bindTo": "generateActiveRowControlsConfig"},
					"changeRow": {"bindTo": "changeRow"},
					"unSelectRow": {"bindTo": "unSelectRow"},
					"onGridClick": {"bindTo": "onGridClick"},
					"activeRowActions": [
						// [Save] action setup.
						{
							"className": "Terrasoft.Button",
							"style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
							"tag": "save",
							"markerValue": "save",
							"imageConfig": {"bindTo": "Resources.Images.SaveIcon"}
						},
						// [Cancel] action setup.
						{
							"className": "Terrasoft.Button",
							"style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
							"tag": "cancel",
							"markerValue": "cancel",
							"imageConfig": {"bindTo": "Resources.Images.CancelIcon"}
						},
						// [Delete] action setup.
						{
							"className": "Terrasoft.Button",
							"style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
							"tag": "remove",
							"markerValue": "remove",
							"imageConfig": {"bindTo": "Resources.Images.RemoveIcon"}
						}
					],
					"initActiveRowKeyMap": {"bindTo": "initActiveRowKeyMap"},
					"activeRowAction": {"bindTo": "onActiveRowAction"},
					"multiSelect": false
				}
			}
		]/**SCHEMA_DIFF*/,
		methods: {}
	};
});

Darian Lewis,

Basically, I tried to apply the code that you sent and it works in a required way if you are trying to add the product via "new" button

http://prntscr.com/mprbvm



To make "plus" button behave as "new" button you should override the logic of the plus button.



Best regards,

Alex

Alex_Tim writes:

To make "plus" button behave as "new" button you should override the logic of the plus button.

Yes, that's what I'm asking for help with - I can't find where to override the plus button.

Darian Lewis,

The logic of "plus" button lays in "BaseGridDetailV2 module. This button is binded to "addRecord" method.

The logic of "new" button lays in "ConfigurationGridUtilities" module. This button is binded to "addRow" method.



So the solution is to override "plus" button and bind it to "addRow" method.



To achieve it, new replacing client module for "OrderProductDetailV2"  should be created and

the code from below should be inserted into the module.



define("OrderProductDetailV2", ["ConfigurationGridUtilities"], function() {

    return {

        entitySchemaName: "OrderProduct",

        messages: {},

        attributes: {},

        methods: {},

        diff: /**SCHEMA_DIFF*/[

            {

                "operation": "merge",

                "name": "AddRecordButton",

                "values": {

                    "click":{"bindTo":"addRow"}

                }

            }

        ]/**SCHEMA_DIFF*/

    };

});

 

Alex_Tim,

Thank you, that did the trick.

Dear mohamad,

Where exactly do you want to add buttons and what have you already done?

Peter Vdovukhin,

Inside the row of the detail grid when , onActiveRowAction when row is active I want to show 2 buttons 

.

Where exactly do you want to add buttons?

I told you inside the row(record) of the detail grid

Like in the picture there is one button , I want to add 2 buttons along with each other

Dear mohamad,

Here is a similar question. Just follow an existing example in the configuration. 

        diff: /**SCHEMA_DIFF*/[
            {
                "operation": "insert",
                "name": "ButtonCopy",
                "parentName": "Detail",
                "propertyName": "tools",
                "values": {
                    "itemType": Terrasoft.ViewItemType.BUTTON,
                    "click": {"bindTo": "onButton1Click"},
                    "visible": true,
                    "enabled": true,
                    "style": Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
                    "caption": "Button1"
                }
            },
            {
                "operation": "insert",
                "name": "ButtonMark",
                "parentName": "Detail",
                "propertyName": "tools",
                "values": {
                    "itemType": Terrasoft.ViewItemType.BUTTON,
                    "click": {"bindTo": "onButton2Click"},
                    "visible": true,
                    "enabled": true,
                    "style": Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
                    "caption": "Button2"
                }
            }

Dear Ezequirel,

You can call initQueryColumns function in your section schema, so to load all columns. In the function, call addAllColumns you have overridden. In this case, you will be able to access not displayed column in the grid by "this.get("Column"); Please see the example below:

initQueryColumns: function(esq) {
     this.callParent(arguments);
     this.addAllColumns(esq);
},

Hope you find it helpful.

Regards,

Anastasia

Dear Federico,

If I understand you correctly, you're talking about displaying a detail on a mini page. A mini page has no functionality that operates details functionality. However, you can investigate the "BasePageV2", find all of the methods and styles that work with details and transfer them to a mini page. Then add a detail to the mini page manually and create custom styles that will display a detail on a small detail field properly.