13 Mart 2012 Salı 11:41
Can someone tell me please why MS has decided to allow setting only filed properties on the left side of a filter expression, while on its right side you can set literals and parameters as well? What is/are the reason(s) for this limitation?
For example, I would like to select Orders using a criteria like this:
where Orders.CustomerID = @p1 OR @p1=0
- @p1 is a parameter bounded to Customers.CustomerID.
- There is a (fictitious) customer record in Customers table with CustomerID = 0 and ContactName = “All”, so if this (first) record is selected, all Orders from all customers are returned.
I know there are options to modify the "where" clause within a preprocess event, but why should I bother with this if I could make the job in Query Designer?
13 Mart 2012 Salı 14:21
This was something we wanted to support but it was tough cut as part of a scoping decision in LightSwitch. If you have not done so already, please log this as a feature request on the Connect Website.
14 Mart 2012 Çarşamba 22:08
Thank you Snomis,
I have followed you advice and refered this question to the link you provided.
I would really appreciate to see this feature made in the future releases.
16 Mart 2012 Cuma 02:58
Thank you for posting this suggestion. I responded to your Connect Bug that while we would certainly like to include this feature in our LightSwitch VS11 release, it is not possible at this time. However, we have added your suggestion for consideration in a future release.
Andrew Lader, LightSwitch PM