How to disable back end field validation to avoid the "Field Validation" error

[item]

Hi Telecastg,

found-it
As reminder is a entity.. so this work in entityDefs meeting.json
I have leave out-of-box validatorMaxCount, i will copy-past the other valid in custom folder.

{
    "fields": {
        "reminders": {
            "validatorClassNameList": [
                "Espo\\Modules\\Crm\\Classes\\FieldValidators\\Event\\Reminders\\MaxCount"
            ]
        },​ 

And in entityDefs reminder.jon :

{
    "fields": {
        "type": {
            "options": [
                "__APPEND__",
                "Sms"
            ]
        }
    }
}​ 

Regards

[telecastg]

Hello @item

Easiest solution is to write this:

{
"fields": {
"type": {
"type": "enum",
"options": [
"__APPEND__",
"Sms"
],
"validationList": [],
"mandatoryValidationList": []
}
}
}

The above will tell the system to ignore the hard coded validation rules.

[item]

Hi telecastg

i have a question for you :
i have create a custom entityDefs reminder.json

{
    "fields": {
        "type": {
          "type": "enum",
            "options": [
                "__APPEND__",
                "Sms"
            ]
        }
    }
}​ 

I see Sms in reminder->type... but validation issue.
Error 400: Bad request
Backend validation failure.

Field: reminders
Validation: valid


I have seach but it's hard code TYPE_EMAIL, TYPE_EMAIL on field Validator.
Where do i have put for disable validator and create my own field validator who are just a copy past out-of-box validator and add 'Sms'

Thanks

[abisbe]

I had the same issue Upgrading to 7.3.4, this solved my issue, as we probably had some misadjustment from the people that developed the site we use for the payments, but the update really meant that for 3 days until we noticed, no payments were being registered into the system, because the policy of field validation changed.

I had the same issue too when copying the solution, it added an extra character, but thanks to that you posted the solution here it was solved quickly too.

Thank you all!

[shalmaxb]

item and telecastg

Great! That did it. The shown characters, which are not visible in the editor I use (Notepad++) is the so called "zero width space" (I think the 0x200b ist the HEX code for that character). In another discussion I found the reason: This character is inserted by Google Chrome (don`t know if in other browsers too) and you see them as soon as you open the browser tools pointing to the code inserted in the first thread, see photo.
As soon as I typed the code instead of copying, it worked.
Thank you for your efforts and hints!

[item]

i have just copy past .. in "sublime text" editor :
i don't know what's is "<0x200b>" .. it's maybe invaders ..

[telecastg]

I I see the same red dot in shalmaxb code when I run it through https://jsonlint.com/ as item suggested, and it throws an error, but if I simply remove the red dot it works fine.

I suggest trying that and then copy and paste the "clean" code into your json file

[item]

Hello @telecastg
Yes red point

https://jsonlint.com/

I have just add 2 braket and copy/past the code between braket

Results

Error: Parse error on line 8:
...yValidationList": [] }}
-----------------------^
Expecting 'EOF', '}', ',', ']', got 'undefined'

My experiment, each time you have error json and not see nothing anything, the json have special encoding bad caractère

You then do not copy/past but write manually the 2 lines

[telecastg]

Is that the red dot item ? How did you find it ?

I checked shalmaxb posted code with Notepad++ and could not reproduce the error

I also checked on my installation and I have an entityDefs file like this, working without any problems

"startingDate": {
"type": "datetime",
"validationList": [],
"mandatoryValidationList": []
},
"endingDate": {
"type": "datetime",
"validationList": [],
"mandatoryValidationList": []
},
"firstExecutionDate": {
"type": "datetime",
"validationList": [],
"mandatoryValidationList": []
},

[item]

special caractere at the end !

[shalmaxb]

Hi,
thank you for your offer telecastg.
Here is the field, that needs to bypass the validation:

"shippingCost": {
"tooltip": true,
"default": 10,
"onlyDefaultCurrency": false,
"conversionDisabled": false,
"validationList": [],
"mandatoryValidationList": []​
},​

but still on rebuild I get a json code error, which is not there, when I rebuild without the two lines. Version espoCRM is now 7.3.4

[telecastg]

If it doesn't work, try checking the entitDefs custom script with your development platform/ editor to see if it detects any json structure errors. I use Eclipse from Apache and it will highlight json structure errors.


Another option (just for you friend, because you always help everyone), post the code from 'custom/Espo/Custom/Resources/metadata/entityDefs/Quote.json' and I will take a look too.

[shalmaxb]

Thank you, then that is, why it does not work here, my client uses 7.3.2. Will recommend to him to update and then try again.

[rabii]

i think since version 7.3.3

[shalmaxb]

Since which version does this work?