Hello Petrika,

Unfortunately, It is not possible to change the text in the error message. The problem here is that the schema that defines it is very hardcoded in the application core. It is not possible to replace and modify it. 

Best regards,

Bogdan

Thank you Bogdan ! Best regards

Petrika,

Assuming the field is a text field, you can try the following custom approach in client page schema.

1. Make the field not required in the section wizard.

2. In the client page schema, add the following code in the methods:

methods: {
	// Redefining the base method initiating custom validators.
	setValidationConfig: function() {
		this.callParent(arguments);
		this.addColumnValidator("UsrProductTerms", this.ProductTermsValidator);
	},
	ProductTermsValidator: function(){
		var invalidMessage ="";
		var ProductTerms = this.get("UsrProductTerms");
		if(ProductTerms.length != 0){
			invalidMessage ="";
		}else{
			invalidMessage = "Product Term is required in order to proceed"; //Put your custom message
		}
		return {
			invalidMessage : invalidMessage
		};
	},
},

Now you can see your custom validation message. Similar approach can also be used for fields of type Lookup, Date, Integer etc.

Regards,

Sourav Kumar Samal

Hello,

Hope you're doing well.

We tried to reproduce the behavior you have described for different types of DB (PostgreSQL and MSSQL) in two ways:

1. Create a column via Page Designer.

2. Create the column in Object Designer.

At first, we have set the string length 250 for the 1st column, then changed it to 50 in the Object Designer and published the object:

As a result we could see that the data type has been changed from varchar(250) to varchar(50):

Then we have repeated the same actions for another test column (added via Object designer) and result was the same:

That's why it would be really helpful if you could confirm if we were doing the reproducing correctly (maybe we should use another version or another product). Also, we can provide you with a fresh installation files so you can try to re-check it from your side once again (for that just contact our support team via this email: support@creatio.com).

About the second question: in general, we do not recommend to change field types. The system can transfer data type from one char to another when you need to change the length of the field. But it may behave unpredictably when the type is changed from one object to another.

Alos you can find some addtional information about data types in the links below:

• https://community.creatio.com/questions/it-possible-change-base-object-…
• https://community.creatio.com/questions/convert-lookup-value-string

Best regards,

Roman

Roman Rak,

Hi Roman, Appreciate your effort in trying to reproduce this.



Your steps does look right - 

1. Create as 250 in Object designer. Publish and check if the DB shows nvarchar(250).

2. Change to 50 in Object designer. Publish and check if the DB has changed to nvarchar(50).



I have verified this on 2 Creatio versions - 7.15.2 Studio and 7.16.3 CustomerCenter (Both MS SQL). Is is possible that this got fixed/changed in the latest 7.17 release?? Il also reach out to Creatio support ato replicate this in the latest release.

M Shrikanth,

As for your question - no, it was not changed in the latest versions.



Best Regards,

Ivanna Yatsura

Roman Rak,

Hi Roman. Checked this use case once again. The behavior I have stated in my question is correct. I have used a on-premises Creatio sales v7.17 on MSSQL. The datatype does change if you increase the length (Eg 50 to 250) but not from 250 to 50.



Have you checked this on an on-premises or trial instance??

I've used the following: 

string.IsNullOrEmpty([#MyStringParameter#])

However, I believe I've used what you're using as well (but might have wrapped it in parentheses)

Ryan Farley,

String.IsNullOrEmpty([#MyStringParameter#]) works.  Thanks!

Dear Fulgen,

See this example to find out how to create a method that watch for changes in some fields. In simple words, you will need creating an attribute, that will have dependencies on needed columns and fires a method. You can see many examples in the configuration like this one:

attributes: {

                    "Status": {

                        "lookupListConfig": {

                            "orders": [{columnPath: "Position"}]

                        },

                        "dependencies": [

                            {

                                "columns": ["Status"],

                                "methodName": "onOrderStatusChanged"

                            }

                        ]

                    },

...

where:

"columns": ["Status"] - list of columns where you watch for changes

"methodName": "onOrderStatusChanged" - method that fires when "Status" column is changed

Dear Fulgen,

I have answered here how to watch for changes in a field. Pressing Enter fires the changing event. If you need more complex logic, you may need to create your own controls. Follow this link to see how.