Cascading Attributes

Scott Wallace

CS10 2014-12 update, MSSQL 2012

I've uploaded  a table called XClassificationSched and have setup three table key lookup attributes.   Select distinct BusinessUnit from XClassificationSched order by BusinessUnit
The attribute opperates correctly, when I click on it, I get the pick list I expect, however when I attempt to select any of the entries I get the following error

Content Server Error:

[Error executing an Sql statement.]

 Does anyone have any suggestions ?

Appu_Nair1

Usually in a typical cascade implementation when you select a attribute through a select,it is temporarily kept in a variable like <MyFirstValue>.If the <MyFirstValue> can produce changes in say another attribute down the line the the javascript/oscript combination will send that as a request to the LLserver perhaps that might look like select somethingelse from another table where value=<MyFirstValue> that is probably bombing on a sqlerror.So either you can work through what succesive queries it may try to run or you can put thread and connect logs on this server(debug=2,wantlogs=true).Sometimes reading 8/16/24/32 threadlogs may not be a viable option so try to reduce your debugging to say 5 threads or so or even one.You might be able to see the passed in params then to make sense of it.If you put builder and know how to go about it it can help as well.Also try a different class of browser like if you were using IE go with FF or Chrome.

That is what I would have done.I would also scour the entire patches area to see if attribute extensions have every patch that is needed Most A D N code and AttrExtenions have similar things so if AttrExtensions don't jive and if you have A D N that is another option.