Microsoft Dynamics CRM (Archived)

Use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

(0) Share

Report

Posted on by Summer Garg

585

Getting below error during creation of case :

Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (0)

Suggested answer

Dmytro Rutkovskyi 1,835 on at

Like (0)

Report

Are you receiving this error every time you trying to submit the case form ?
Have you use standard (OOB entity case form) or you customized it with Javascript or other data-manipulations? Its better to not add any new inputs, as they anyway will not be counted by Portal Entity Form server side.

In rear cases that error can mean that you try to create case with unsafe symbols like < or > in the Case Description fields. This can be fixed by setting DisableValidationWebTemplate site setting to True.

Was this reply helpful? Yes No
Summer Garg 585 on at

Like (0)

Report

Yes, I have one lookup field on case form which I then converted into drop-down and apply some filter on this drop-down using JS.

One thing to note : if I removed this JS on field which filtered the drop-down then it's working fine

But my JS is also right. It's just filtered the drop-down on load of case form.

Seems this is some kind of security issue.

Was this reply helpful? Yes No
RaviKashyap 55,410 Moderator on at

Like (0)

Report

Can you share you js please? It looks like your js is making a page refresh which is not acceptable by portal.

Was this reply helpful? Yes No
RaviKashyap 55,410 Moderator on at

Like (0)

Report

Also, try setting the key shared above "DisableValidationWebTemplate"

Was this reply helpful? Yes No
Summer Garg 585 on at

Like (0)

Report

Yes, i also tried this key but again getting same error

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Can, you try the below setting on your web page and see if it helps?

Was this reply helpful? Yes No
Schjoermann 20 on at

Like (0)

Report

Did anyone come with a solution for this issue? I have exact same issue, have a JS that filters a lookup rendered as a dropdown.

If I select some of the records from the dropdown I get exact same error as describe above, for others I don't get any error.

How to stop the error?

Was this reply helpful? Yes No
Nicolas FLEURENT 5 on at

Like (0)

Report

Hello,

I have exactly the same issue. Dis you find a fix ?

I tried the solution proposed by Ravi Kashyap but it doesn't fix.

Thanks,

Nicolas

Was this reply helpful? Yes No
Suggested answer

Schjoermann 20 on at

Like (0)

Report

Hi Nicolas,

I came to the conclusion that this is a limitation of lookup fields rendered as dropdowns in the portal.

The dropdown list will only show the first 5000 records.

So if you have 7500 records in the entity you are looking up, and you filter the list to only show 7. If the one you then select from the 7, is not part of the first 5000 in the original list you will get the above error.

I created a case for Microsoft on this issue, and they say that this is by design.

Best Regards,

Nicolai

Was this reply helpful? Yes No
TomV05 5 on at

Like (0)

Report

Nicolai - did you ever hear anything from Microsoft or find a fix?

Tom

Was this reply helpful? Yes No