Mar 01, 2010 12:07 AM|klca|LINK
I think that this will seem kind of silly to you but:
As I have to make my system work for continuing proper testing of it, I decided to do something trivial because I still don't get how to manage the
FilterRepeater I decided to build a new customized page in which I have declared the filter control to be not visible (even though it alwas executes its routine
on the background as I have checked while debugging) and I will build
the two required filters that I need (two DropDownLists) of which the first one has IsPostBack property set to true and in that way I can have the second datasource of the second DDL conditioned
(the where sentence) to display only those records that fit the query criteria for the "grand father entity".
The only drawback, which by the way is a HUGE one, is that I have customize every single page that must meet this kind of behaviour (which is not in accordance with the spirit of building an application based on templates and in MetaData
¡¡¡ ATTEMPT ... FAILED !!!
After reading your posts in C# Bits and others solutions in the forum I go back to my original idea that YOU MUST WRITE A BOOK ABOUT DYNAMIC DATA sponsored by Microsoft and you will both will get a lot of rewards about it.
I mentioned that because you have really worked hard in this field and sometimes we, normal programmers of the world, might be trying to find easy solutions (that by the way is the way it should have to be) and I have claimed lack of documentation on this
matter several times before ... obviously not from you ... the "Gran Guru" of this blog ... (we must reach the top of the mountain as to be able to see you and ask for your advice)
Carlos Porras (El Salvador)
P.S.: I have started reading your