Hi, I have a web custom screen (ASP.NET based) which runs perfectly ok in a browser. When I added it to Tessitura as a custom screen it renders ok and can pull the details for the current constituent from the local tables without any problem but:
1. On some workstations, anytime we click on a button or list item which does a postback, we get the error shown at the bottom. Setting EnableEventValidation="false" at the page level or in the web config file stops this error on the problem machines but make some controls irresponsive.
2. Clicking on a listbox or a drop down list item doesn’t fire the associated event, we need to select an item by using the up/down arrows and then press enter to make it work. We have seen similar issues in case of some dashboard widgets.
Postback Error when called inside Tessitura as a custom screen or a report:
Sys.WebForms.PageRequestManagerServerErrorException: Invalid postback or call back argument. Event validation is enabled using <pages enableEventValidation=”true”/> in configuration or <%@ PageEnableEventValidation=”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……… Do you want to continue running scripts on the page?
I am using the execute local procedure web API to update the local tables.
Any ideas? Thanks!
Mo
National Ballet of Canada
Just to give an update:
1. The registry update as mentioned in the older post (knowledgebase article # 19336) didn’t quite work for us (in fact we had tried it before for some SSRS report widgets with a dropdown list but without any luck); even after the registry update the click event doesn’t fire when we select a list or dropdown list item of a web custom screen inside Tessitura. We had to select an item using keyboard arrow keys and then press enter to make it work.
2. I couldn’t find a suitable control in Ajax Toolkit to substitute ASP List Box control to avoid a List Box (added in a Ajax Update Panel) item’s non-responsive behavior after setting the EnableEventValidation="false".
3. Also setting EnableEventValidation="false" doesn’t seem like a good idea for security reasons; even though at this moment we are only using this custom screen internally only in the long run we have a plan to give our users access to such custom screen externally (from internet)
4. I tried by overriding the Render method to register all List Box items using Page.ClientScript.RegisterForEventValidation as suggested by some websites, but it didn’t quite work for me (for my workstation) though our users’ machines look ok now (no more “Invalid postback or call back argument” related long error message for them) other than that they still have to select a list item using keyboard which is a minor inconvenience we learnt to live with.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Mohiuddin Faruqe Sent: Tuesday, November 19, 2013 9:39 AM To: Mohiuddin Faruqe Subject: RE: [Tessitura Technical Forum] Web Custom Screen - Errors
Thanks Jon, this helps. I am also using an ASP.NET Ajax UpdatePanel as mentioned in the older post. I will follow the suggestions and see how it works for me.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jon Ballinger Sent: Monday, November 18, 2013 7:03 PM To: Mohiuddin Faruqe Subject: Re: [Tessitura Technical Forum] Web Custom Screen - Errors
Hi Mo,
I ran across this issue before. Here is an older post on this issue.
http://www.tessituranetwork.com/COMMUNITY/forums/p/6183/19615.aspx#19615
Jon
From: Mohiuddin Faruqe <bounce-mohiuddinfaruqe8297@tessituranetwork.com> Sent: 11/18/2013 9:45:59 AM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Mo, you may need to set the emulation mode for the browser control. By default it uses a lower version of IE. It can be set via a registry setting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION or I think you can try doing it thorugh an http header. The header I did not have luck with before.
Another option is to have a place holder page for this screen and its job is only to open a new browser window with the desired web page. This was my last resort for a part that i could not get to work at all inside tessitura,
We definitely updated browser emulation to get around some SSRS custom screen issues here at UMS. From my notes: