This project is read-only.

Date as a Conditional variable filter


Thank you so much for your solution. I have a couple of questions about how to properly construct the XML configuration: I can get my custom entity to load properly if I add the filter without the condition variable but cannot for the life of me get it to work once I add the variable. I value types of String, Enumeration, DateTime -- what could it be?

Please tell me where I am going wrong?

  <mapcondition text="Pickup Dates Since: ">
    <condition attribute="new_pickupdate" operator="on-or-after" value="%{0}%" />
    <value type="Date" default=""></value>


atulcrm wrote Oct 10, 2012 at 6:25 AM

You need to treat data or any other types as string only. Other types are not implemented yet. Change the value type to string. I agree that it is limiting the filter's user experience and functionality. It needs some good amount of work from my side to implement it and will do once I get enought time for the same.


mlachance wrote Oct 10, 2012 at 4:40 PM

I did exactly that yesterday as a work around.  
-- now I have 12 Filter variables which all appear to work great !

Unfortunately, there isn't enough room on the filter bar and there isn't a scroll to get to the filters
-- Any suggestion for that

atulcrm wrote Oct 11, 2012 at 9:27 AM

I didn't antcipate 12 filters while I was developing this solution.. IMO, you should try to reduce them in favor of usability as well..