Unfortunately, we don't have ready-made examples of implementing such filtering. However, you can build such a filter using the following code as an example:
 

"attributes": {

..
                "DataGrid_d7k1ikp": {
                    "isCollection": true,
                    "modelConfig": {
                        "path": "DataGrid_d7k1ikpDS",
                        "filterAttributes": [
                            {
                                "loadOnChange": true,
                                "name": "DataGrid_d7k1ikp_PredefinedFilter"
                            }
                        ]
                    },

DataGrid_d7k1ikp_PredefinedFilter leads us to the attributes:

"DataGrid_d7k1ikp_PredefinedFilter": {
                    "value": {
                        "items": {
                            "a2376c0c-0b3f-451a-9085-0a65ae58bab8": {
                                "filterType": 4,
                                "comparisonType": 3,
                                "isEnabled": true,
                                "trimDateTimeParameterToDate": false,
                                "leftExpression": {
                                    "expressionType": 0,
                                    "columnPath": "Account"
                                },
                                "isAggregative": false,
                                "dataValueType": 10,
                                "referenceSchemaName": "Account",
                                "rightExpressions": [
                                    {
                                        "expressionType": 2,
                                        "parameter": {
                                            "dataValueType": 10,
 

...

If you need to build a dynamic filter, you should look in this direction. Create a custom attribute, populate it when loading the record (in the LoadDataRequest handler), and use it in the code of the DataGrid_d7k1ikp_PredefinedFilter filter.

If you have doubts about how to correctly construct paths to columns, please follow these steps: navigate to the section with this list, create an advanced filter, find the SelectQuery in the browser's Network tab, and copy the filters from the request body.

Best regards, Pavlo!

Hello,

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

Hello,

If any changes should be done to the cloud-based instance, you can contact support team via support@creatio.com with detailed step by step instruction for further assistance. 

Best regards,
Anastasiia

Hello, Josh.

I think you can find an example here 

https://academy.creatio.com/docs/user/bpm_tools/process_elements_refere…

Check the example with CompositeObjectList

Hello, Josh.

Check this article 

https://academy.creatio.com/docs/user/bpm_tools/process_elements_refere…

Example you need is CompositeObjectList

I forgot to mention the 'SetDefColumnValues' method call was added after the error message appeared.

Check that your "Lead" object, where the record is modified has no duplicated columns (the error is returned from EntityColumnValueCollection, not in SetColumnValue). Also are you able to add records manually to the "Leads" section? I guess you should get some simillar error on this attempt either. Also if you are using PostgreSQL please:

1) Go to the root Web.config

2) Find the maxEntitySchemaNameLength key and modify the value to 63 there

This key controls the data reader behaviour and fixes issues of max PostgreSQL items length (table names, column names, etc.) and if your object has several columns with the lenght of name more than 63 symbols this issue can also occur.

Thank you Oleg! Another admin added a column in another package with the same name.

Hello Keerthana Yenagandhula

I made a similar webservices a few weeks ago.
Here's a Creatio article explaining how to do it:
https://academy.creatio.com/docs/7-18/developer/back_end_development/we…

And there is also the walkthrough to test it in Postmain

https://academy.creatio.com/docs/7-18/developer/back_end_development/we…

I hope this will help you.

Vincent

LAVIGNE Vincent,

LAVIGNE Vincent,

In my case, I am facing issue in Postman Issue.could please,help me I am unable to rectify this issue.

Keerthana Yenagandhula,

Hi!

Please review all the headers and ensure that the settings are configured correctly.

Here is the documentation to get acquainted with:  https://documenter.getpostman.com/view/10204500/SztHX5Qb?version=latest…

We will be glad to help with any other questions.

Hi!

Please try to run the actions 'generate all' and compile the site again.

Let us know the result, please!

Alla Blinova,

we are still getting the same error

Hi!

The issue is caused by the missing sources of the custom package object. To resolve this issue, we recommend regenerating the sources for the relevant schemas (please see the attached file) ​​​​​​​ and then performing compilation.

To investigate this behavior, we ask you to submit a request to our team via support@creatio.com or the Success Portal. 

We'll need to access the instance remotely in order to help.

Thank you for your cooperation!

Hello,
This question needs to be analyzed mo deeply, but, based on your information, the POST request isn't affected by all the DB triggers and therefore happens before the insert.
Also, a small note, if you have autonumbering both on the JS and Server side than a new number will be generated no matter what is the source of the object (data, business process, etc).

Hi Harry,

In case you doubt about the filtration on the column you can create a test list based on the object of your lookup column and specify the needed filtration there:

and

save the page and open the code. As a result you will see an autogenerated code of the working filtration that then can be applied to the column:

HI Oleg, 

Thank you. This example works well when applying a static filter. However, it seems not to work the same when trying to apply filter by page data. 

Do you have any example how to translate this same method so that I can filter a lookup column by page data? 

Thank you 

Hi Harry,

It would be easier to handle the request for when the lookup requests its data source and then add the filters to that request since you'd have access to page data.

When the lookup is activated (user clicks the dropdown) it sends a crt.LoadDataRequest. You can listen for that and then add the filters there. The request would look something like this: 

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.LoadDataRequest",
		handler: async (request, next) => {
		    // the data soruce name will be the lookup attribute name + "_List_DS"
			if (request.dataSourceName !== "LookupAttribute_46uzwvy_List_DS") {
				return await next?.handle(request);
			}
 
			// get other page values
			const compId = request.$context.UsrCompanyName.value;
 
			// add filter
			request.parameters.push({
				type: "filter",
				value: {
						"filterType": 6,
						"isEnabled": true,
						"items": {
							"CustomFilters": {
								"filterType": 6,
								"isEnabled": true,
								"items": {
									"cb855fc4-4526-475a-beea-8e41a7f5a439": {
										"comparisonType": 11,
										"filterType": 1,
										"isEnabled": true,
										"leftExpression": {
											"expressionType": 0,
											"columnPath": "Account"
										},
										"rightExpression": {
											"expressionType": 2,
											"parameter": {
												"dataValueType": 1,
												"value": compId
											}
										},
										"trimDateTimeParameterToDate": false
									}
								}
							}
						}
			});
 
			return await next?.handle(request);
		}
	}
]/**SCHEMA_HANDLERS*/,

As a side note, for the filter, I believe something along these lines should work. It's close the working, but the end result request shows in the network tab that the filter key and filter values get added separately to the filters array causing a server error. Hopefully we'll get more details on this sort of thing soon:

(Note, the below doesn't work yet, but sharing it in case someone else gets it to work)

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.LoadDataRequest",
		handler: async (request, next) => {
		    // data soruce name is lookup attribute + "_List_DS"
			if (request.dataSourceName !== "LookupAttribute_46uzwvy_List_DS") {
				return await next?.handle(request);
			}
 
			let filters = new sdk.FilterGroup();
			filters.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Type.Name", "Partner");
 
			// add filter
			request.parameters.push({
				type: sdk.ModelParameterType.Filter,
				value: filters
			});
 
			return await next?.handle(request);
		}
	}
]/**SCHEMA_HANDLERS*/,

Ryan

Thank you, Ryan. That worked perfectly. 

Hello,

If you need to hide the section for some time for a specific user or group of users/role, you can simply remove the section for the needed time from a Workplace in which the user/group of users or specific user role is working and once needed add it to the Workplace again. 
You may also consider creating a separate Workplace for this user/users so it will be easier to manage. 
However, the user will still be able to access records or a section by a direct link for example, if you need to prevent it, we'd suggest considering changing access rights for the object for the user/user role. 

If we are talking about hiding a section for a specific timeframe, for example from 4 to 5 pm each day, such implementation can be done only by means of additional development. 

Best regards,
Yuliya Gritsenko