Hi again,

Thanks for the example file. However, the WebTab has AutoPostBackFlags set to on, as opposed to Async. Setting it to Async stops it from working. I suspect this is because the updatepanel requires a proper post back to be triggered?

This is why we used JS in our scenario, to trigger an Async postback on the client event SelectedIndexChanged, but this is the point where we run into errors. Looking online suggests we might have incorrexy AJAX assemblies, but all looks in place from what I can see

Thanks again for your continued support!

From the looks of it though, that button still causes a full postback? I need the WebDropDown to be updated WITHOUT full postback, and I need it updated after a partial postback from the WebTab. Also note that we have the EnableLoadOnDemand set to true, which seems to cause issues with this. 

I'll double check the sample with out project, but from what I can see, it's still doing a full postback

EDIT: this is also being done within an ASP:content page, which inherits from a Master page. Does that change the setup? Still getting a null reference javascript error after implementing your solution into our project

ANOTHER EDIT: seems having AJAX enabled for the WebTab is causing issues also

Main problem is that we need to have AJAX enabled, otherwise the WebDataGridView loses it's content after loading another tab. The problem with having the client side selectedindexchanged is that it seems to do the postback before the server side, which results in no data being loaded. Is there any way to say in the javascript, "Wait until the server side SelectedIndexChanged event has finished doing it's processing, THEN do some stuff"?

Hello Alex,

Currently there Is no way to achieve the mention events order, The reason is that the client side is the one that requests some job to be done on the server. This is the reason why client side events are fired before the server side events.

However, I modified the sample project in order to achieve only async postbacks . What I am doing is to call __doPostBack for the WebDropDown using __doPostBacks function`s parameters. With setting WebDropown as __EVENTTARGET I am causing async postback for the WebdropDown respectively for the updatePanel. Some further reference about __doPostBack function and its parameters could be found at:

http://aspalliance.com/articleViewer.aspx?aId=895&pId=-1

Now in my scenario async postback is triggered when ActiveTabChange event is fired and WebDropDown`s selected index is changed. For example:

Client side:
 <script type="text/javascript" id="igClientScript1">
 function causePostBack() {
 __doPostBack('WebDropDown1', ' ');
}

 function WebTab1_ActiveTabChange(sender, eventArgs) {
causePostBack();

}
 </script>
Server side:
 protected void WebTab1_SelectedIndexChanged(object sender, TabSelectedIndexChangedEventArgs e)
{

 int index = e.NewIndex;
 this.WebDropDown1.SelectedItemIndex = index; 
}

I hope you find this information helpful.

Please let me know if you need any further assistance with this matter.

Again, I can't thank you enough!

I think I've drilled down to the root of the issue. Having a WebDataGrid in one of the ContentTabs seems to be causing the issue.

Even just putting an empty WebDataGrid into a ContentTabItem, then clicking that tab, causes the following error:

Line: 4620
Error: Sys.ArgumentUndefinedException: Value cannot be undefined.
Parameter name: type

Again, this WebDataGrid is completely empty, and has been dragged and dropped from the toolbox and nothing else.

Without the WebDataGrid, everything works fine. Is this an issue with the WebDataGrid, or is there some underlying problem in our code? Again, the given WebTab options work fine without the WebDataGrid, so I'm assuming it's something wrong with how the WebDataGrid is set up.

Thanks again for all your help!

Just to add further to this, I've noticed that the WebDataGrid is always null when I'm debugging. For instance, in the Page_Load event, the WebDataGrid is null.

EDIT: Looks like the WebDataGrid only loads if it is in the initial selected tab. Any other tabs with a webdatagrid that aren't selected on start up don't seem to get instantiated (using the above WebTab properties). Is the proper behaviour? If it is, is there a way I can force them to be loaded so that I can keep in place the WebTab options we have?

Hi again,

Thanks for the example file.