Hi there
Smart CallBacks functionality of WebCombo v.8.2 gets frozen and generates the error: (paramater is incorrect). Debuging takes me to the following file and function:
webresource.axdparamater is incorrectigtbl_XSLTProcessor.prototype.transform=function(){ if(!this.input) return false; if(ig_csom.IsIE) { this.Processor.input=this.input; this.Processor.transform(); this.output=this.Processor.output; } else return this.outputDocument=this.Processor.transformToDocument(this.input); return true;};
Any help more than welcome
Regards
Elvis
Wish I could help you Elvis but I don't have any experience with the WebCombo. Maybe one of the developers at Infragistics could help. I am thinking it is related to the issue that I ran into. Unfortunately I did a quick check and there is no "Browser" property like the Grid. I had hoped that our two problems were the same just because it did fail with the same error message at the same point in the JavaScript.
That was another problem you sorted out, we are looking at different issues, my WebCombo is outside a grid, inside a Panel on a Web Form, I haven't change many properties on the control, as you can see down:
this.WebComboParty.Editable = true; this.WebComboParty.EnableXmlHTTP = true; this.WebComboParty.ComboTypeAhead = Infragistics.WebUI.WebCombo.TypeAhead.Suggest; this.WebComboParty.DataTextField = "ShortName"; this.WebComboParty.DataValueField = "CCode"; this.WebComboParty.InitializeLayout += new Infragistics.WebUI.WebCombo.InitializeLayoutEventHandler(WebComboParty_InitializeLayout);
No, I did NOT synchronize the files. The only thing that I did to get it to work was to change the browser attribute on the grid from "Xml" to "Auto". This allowed things to work correctly.I gave the report between the good and bad machines to assist the developers in understanding why the "Xml" setting does not work on particular machines. I did nothing to actually move files around. I don't know if it will be useful or not but it's better to have too much information instead of too little.
Thanks for looking into this.
Scott
I was able to test this on the computers that were having the issue and they are now able to display the page without any problems. As a side note to Infragistics, if it helps with tracking down the problem for a possible permenant solution (other than causing developers hours of aggrevation while tracking this down) I have attached a report on the dlls for the problem machine. This was a quickie program I put together to compare the bad machine to the good machine. It lists all the .dlls and whether there is a difference. I thought it might help in tracking down why the problem is occuring.In the report...If the line begins with a space, the file occurs on both machines.
If the line begins with a minus, the file is not on the bad machine but it is on the good machine.
If the line begins with a plus, the file is on the bad machine but it is not on the good machine.
If the line begins with an asterix, both systems have the file but the versions are different. The first version number printed is the bad machine, the second version number printed is the good machine.
Hopefully this helps...