Hello!

You can use the filtersConfig parameter to filter records, as mentioned in the article.

Or you can use the option selectionState to predefine selected rows, which will be pre-selected when the lookup page is opened.

Example of selected records:

{
	type: "crt.OpenLookupPageRequest",
	...
	selectionState: {
		type: 'specific',
		selected: [
			'00000000-0000-0000-0000-000000000000',
			'11111111-1111-1111-1111-111111111111',
		]
	}
}

An example of pre-filtering records:

{
	type: "crt.OpenLookupPageRequest",
	...
	filtersConfig: {
		filterAttributes: [
			{
				name: 'MyFilter',
				loadOnChange: false
			}
		],
		attributesConfig: {
			MyFilter: {
				value: {
					"items": {
						"29e16d42-36f1-4e04-9029-4321cbb2494d": {
							"filterType": 1,
							"comparisonType": 11,
							"isEnabled": true,
							"trimDateTimeParameterToDate": false,
							"leftExpression": {
								"expressionType": 0,
								"columnPath": "Name"
							},
							"isAggregative": false,
							"dataValueType": 1,
							"rightExpression": {
								"expressionType": 2,
								"parameter": {
									"dataValueType": 1,
									"value": "Super"
								}
							}
						}
					},
					"logicalOperation": 0,
					"isEnabled": true,
					"filterType": 6,
					"rootSchemaName": "Contact"
				}
			}
		}
	}
}

It is still the same since the Lookups area is still classic UI.

Also, BTW I have the instructions with Postgresql instructions here, if interested/needed: https://customerfx.com/article/creating-an-edit-page-for-a-lookup-in-cr…

Hello Harvey,

It's not possible for now, but we've registered it in our R&D team backlog for consideration and implementation in future application releases.

Thank you for helping us to improve our product. 

Hi!



Unfortunately, there is no such possibility now. We have registered a request for the development team to consider adding this option in future updates. 



Best regards, 

Anton

Hello!

Unfortunately, there are no approximate timelines for implementing the functionality. 
However, you might be interested to know that we have the functionality to change DCM conditions on the pages.

We would also appreciate it if you could provide more details about the business task you plan to implement.

First read the record using whatever Identifier you have on it from the source data. If the record exists the Id value will be a Guid and if it doesn't exist the Id of the record will be Guid.Empty.

So the condition for the update will look like: 

[Id from the Read] != Guid.Empty (this means the Read found the record)

The "else" will proceed to the Add, just make sure you populate some identifying value from the API call that you'll use when you read if the record exists next time.

Ryan

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,



For a more detailed analysis of the problem, please contact support via email: support@creatio.com.

Hi Raul Mendizabal,



The Activity section is named as "Tasks" in Freedom UI latest versions. You can try to search for tasks section in the frontend.

Dear Kumaran,

Thank you for your question!

Allow me to clarify how the import process works. When importing data into Creatio, you are essentially transferring the information from your Excel file into the corresponding database table. Each detail in Creatio corresponds to a different object or database table. Therefore, during an import, data can be inserted into one table or object at a time.

Import to Contact/Accounts have custom core logic applied, but all other objects work with logic described above.

You can read more about Excel import on Creatio Academy: https://academy.creatio.com/docs/8.x/creatio-apps/creatio-basics/busine…

Have a great day!

Hi,



I recommend you check your Redis settings.



https://academy.creatio.com/docs/8.x/setup-and-administration/category/…

Hello,

Currently there is no basic functionality to setup access rights for users dynamically within the import process itself. However, you can use the following alternatives to achieve your business task:

Set up record permissions for the needed object based on the record author and then import the records under different users in separate batches based on the role.

For example, import a batch of records that only the role A should get access rights for under user1. Setup the record permissions this way:

If record author is user1, then give access rights to role A.

Then import the next batch of records under user2 and setup the record permissions as:

If record author is user2, then give access rights to role B.

Another option is to create a business process that would read data (read a collection of records) and then transfer the data from the records to a subprocess. The subprocesses will then process each record separately (1 subprocess will run for 1 record) and change the access rights (with the help of Access rights element) for these records. However, in such case you need to have a field in this object that would signify what role should get the access rights for which record, based on which the process will determine what rights to give to which record.