Quantcast
Channel: SharePoint 2013 - Development and Programming forum
Viewing all articles
Browse latest Browse all 25064

Wizard Control inside of Update Panel (SharePoint 2013 Web Part)

$
0
0

Hello Everyone,

I am new to SharePoint so I apologize in advance if my question is basic. I have been tasked with creating a Web Part for SharePoint 2013. On this Web Part, we have an ASP.Net Wizard control with several WizardSteps inside of it. When I deploy and test my Web Part, everything works as expected. However, clicking the "Next" button in the wizard causes a full page refresh every time you change to a new step.

To solve this issue, I put the Wizard control inside of an UpdatePanel. Here is the code I have:

<asp:UpdatePanel ID="UpdatePanel1" runat="server"><ContentTemplate><asp:Wizard ID="Wizard1" runat="server"><WizardSteps><asp:WizardStep>
                    Step 1</asp:WizardStep><asp:WizardStep>
                    Step 2</asp:WizardStep></WizardSteps></asp:Wizard></ContentTemplate></asp:UpdatePanel>

After wrapping the Wizard in an UpdatePanel, the "Next" button no longer works. I can see the post/response occur in Fiddler but the Wizard does not change steps. If I click the "Next" button a second time, it causes the following error to be thrown:

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.

Is there something special that I need to do to get an UpdatePanel working in SharePoint 2013? I have tested even simpler scenarios with just a button in an UpdatePanel and, on the second click, I get the same "Invalid postback" error. Unfortunately, Google and Bing do not turn up many results for this issue and SharePoint 2013. I have tried several proposed solutions to similar issues in SharePoint 2010 but they don't produce any different results.

Any help is greately appreciated! Thanks in advance.

Here is some additional information that might help:
I am using SharePoint 2013.
I am deploying my Web Part to a Publishing site.


Viewing all articles
Browse latest Browse all 25064

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>