Atul,
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?
<Conditions>
<mapcondition text="Pickup Dates Since: ">
<condition attribute="new_pickupdate" operator="on-or-after" value="%{0}%" />
<value type="Date" default=""></value>
</mapcondition>
</Conditions>
Comments: 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. Thanks, Atul
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?
<Conditions>
<mapcondition text="Pickup Dates Since: ">
<condition attribute="new_pickupdate" operator="on-or-after" value="%{0}%" />
<value type="Date" default=""></value>
</mapcondition>
</Conditions>
Comments: 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. Thanks, Atul