Question

Http failure response for https://1*****62-demo.creatio.com/0/rest/RightsService/GetCanEdit: 400 OK

Hi All,

May I ask: Have you ever experienced a 400 error like this?

This appears when we save data in a form. And the data won't saved.

And after this error appears, AI Chat Creatio immediately stops working.

I also tried running Creatio in Firefox, Chrome, and other browsers in Incognito mode, but not fix the error. And this issue is intermittent but I can say 95% frequent showed up.

Need advice please, thank you.

Like 0

Like

1 comments

Hello.

The GetCanEdit 400 error is most commonly related to how the page's data source is configured, particularly when it comes to the relation criteria used to resolve a specific record.

When the relation criteria on a page are set up incorrectly, or point to a relationship that cannot be properly resolved at runtime, Creatio is unable to determine a valid related record for the given context. As a result, the value primaryColumnValue is passed as null when the request is sent to RightsService/GetCanEdit. Since this service expects a valid GUID value in order to perform the permission check, receiving a null value instead leads to a GUID deserialization error, which in turn causes the request to fail with a 400 status code.

To resolve this, we recommend reviewing the relation criteria configured on the page. Please verify whether these criteria correctly reference the intended relationship, and whether the referenced relationship is expected to always resolve to a valid record in your specific business scenario. If the relation criteria are not required for the page to function correctly, or if they are pointing to an incorrect or unnecessary relationship, we would recommend removing them.

If reviewing the relation criteria does not resolve the issue, this behavior may alternatively be caused by a duplication of the data source on the page. In such cases, having more than one data source referencing the same entity schema on a single page can also lead to similar permission-check errors, and this would need to be reviewed separately as a possible root cause.

Best regards,
Antonii

Show all comments