That's exactly how I got it to work but its probably not the right solution.
Thanks, -Kiran On Sat, 2010-11-13 at 09:39 +0000, Nelson Ndegwa wrote: > Hi Kiran, > I have bumped into a similar problem before - not sure my fix is the > recomended solution but it seemed to work. > What i did was that in the 'tableConstraint' attribute of the filter, > instead of the 'content__dm', i replaced that with the full name of the > dimension table i.e. 'dataset__content__dm' then did as Syeid just > advised. Give it a try and see it works, then check that the returned > values on a query are indeed coming from that dimension table. Any > comments Syeid? > Nelson > > Kiran Mukhyala wrote: > > Hi Syed, > > > > I've already tried that but it didn't help. > > > > I just realized that I haven't really added a new filter but added a new > > option to an exiting filter of type id_list. The existing options in > > this filter work fine. The internal_name of the new option and attribute > > are identical. > > > > Thanks, > > > > -Kiran > > > > On Fri, 2010-11-12 at 23:21 +0000, Syed Haider wrote: > > > >> Hi Kiran, > >> > >> please make sure that an attribute with same name as of filter exists in > >> the configuration and then do File->Export (MartEditor). Once done, > >> reconfigure (perl bin/configure.pl..... --clean) and restart apache. It > >> should be fixed. > >> > >> Best, > >> Syed > >> > >> On 12/11/2010 22:29, Kiran Mukhyala wrote: > >> > >>> I have added a new filter based on a newly added dimension table to my > >>> mart. > >>> The query generated is using the table name of the form content_type__dm > >>> instead of the form dataset__content_type__dm and so throws the error: > >>> table does not exist. > >>> How do I specify the dataset name with my new filter? > >>> > >>> Thanks, > >>> > >>> -Kiran > >>> > >>> >
