Dear Andrii,

Unfortunately, we cannot handle exceptions with standard tools in actual versions of applications. Thank you for bringing this aspect to our attention. We will create an idea for the development team so they can consider implementing such functionality in future versions of our application.

If you're talking about custom C# code and Script tasks, you can use basic try/catch constructs there to handle exceptions.

To track errors in business processes, you can create a new business process. It is described on the Creatio Community at the following link: https://community.creatio.com/questions/exception-handlng-business-procecss.

Thank You!

Having some form of try/catch or error pathway in BPs would be very helpful, sometimes errors are "expected" especially when using the OOTB steps for things like adding data (e.g. if a unique index is violated due to the non-atomic nature of data operations in BPs) and need to be handled more nicely than just halting the BP and leaving the data in an inconsistent state. It forces many properly implemented pieces of functionality away from being built in no-code and straight back to needing to write C#.

Andrew Sheng,

Unfortunately this idea has not been put on the development Roadmap yet and therefore we cannot provide any ETA on when it can be expected within the system. However, I will add your inquiry to the registered idea in order to increase its priority.

Hello,

Unfortunately, Web service element doesn't directly expose the request body for logging within the element itself. 

Hello, 

and no hidden workaround? Or any methods, which are used from request body generation, that we could use as well?



Kind regards,

Vladimir

Hello Vladimir,



You can try to use Telerik Fiddler tool to capture requests that are being sent.

Same here in our cloud dev environment with this new 8.1.2 functionality

You are right, we do not have the problem on our production environment, only on the dev env.

Hello,

Please note that this issue is connected to the 8.1.2 release and in order to fix it you need to create a case directly for our Support team (support@creatio.com) so we could work with the site in question.

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"
				}
			}
		}
	}
}

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 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!

Hello,



To find duplicates in Freedom UI, you need to go to System Designer, then select Setup duplicates rules.



There you will be able to perform all the actions you need.

Malika,

Hi ,

Setup duplicates rules is not sowing under System setup. Is it due to the latest version??

Abhishek,

Is this a cloud or local system?

If it's local, you probably need to set up the deduplication components first to have it available.

Hello,

 

You need to remove it from the development website, install the package on the production website, and the package installation mechanism on the production site will detect the differences in objects between what exists in production and what is in the package, and drop them.



Best regards, 

Orkhan

Orkhan,

is this valid also for all references to the deleted fields like forms, lists, dashboards, reports,...?

I guess the system will not check js and cs code, so that will need to be handled manually, right?

BR

Robert Pordes,

No, system will not check. But this is not a problem to remove such fields from the code



Kind regards,

Vladimir

Finally we found the problem: the OpportunityProductPageV2 source page in the Opportunity package contains a method that calculates the price of the product including VAT: calculatePrice.

I've overridden the method and the problem is solved.

I thought that creating the OpportunityProductPageV2 page in the Custom package replaced the view model, but in fact it's an extension.

Sorry for the inconvenience.

Hello,

It depends on which column should be required here. One particular example: this method can be added to ActivityMiniPage:

save: function(callback, scope) {
				var opportunity = this.get("Opportunity");
				if (opportunity) {
					this.callParent(arguments);
				} else {
					Terrasoft.showInformation("Opportunity is required");
				}
			}

In this case saving of the mini page is not possible in case an opportunity is not connected to an activity and the information message will be shown on the page.

Hi Oleg,

Thank you, it works!