Last post Nov 05, 2010 11:26 AM by sjnaughton
Nov 04, 2010 06:17 PM|gijigae|LINK
Is "View" the only option to have multiple List screens for one table?
For example, I would like to have multiple Orders screens in Northwind DB per product and show a particular product order screen to a certain user group.
Each screen should be updeatable.
I checked a Link, which Steve suggested for a Updateable view.
Is it the only option?
Nov 05, 2010 02:36 AM|snuggles|LINK
to be honest this is also something that has troubled me a bit as well.
if and when i come up against this, i might treat this as a special case and use a static page or similar as the idea of munging the xml is not the way i would like to go.
i have read though that you could have a view, then also use stored procedures (functions) to do the updates.
Nov 05, 2010 08:06 AM|sjnaughton|LINK
That all depends how far down the rabbit hole you want to go, it's certanly an easy way only give access to certan roles to each view.
You could also have some custom route handler, that changes which page template to use based on roles, but that required going much futher down the rabbit hole than the previous solution.
See my article
Custom Entity Templates – Dynamic Data 4 and Page Action Mapping in Dynamic Data either could be adapted to do whay you want bu mixing it with a custom route handler
Like in my Securing Dynamic Data 4 (Replay) article.
Dynamic Data 4
Nov 05, 2010 11:03 AM|gijigae|LINK
Thanks for sharing your thoughts on this topic.
In my case, screens generated from view will have very limited editable fields and thus I will first try the "view" option.
Nov 05, 2010 11:07 AM|gijigae|LINK
As you may know, I am using DD1 and custom entity templates are not on the horizon yet.
However, when time comes, I will refer to your post for custom entity templates and routing implementation.
Nov 05, 2010 11:26 AM|sjnaughton|LINK
You may find
Page Action Mapping in Dynamic Data (DD1 or DD4) either could be adapted to do whay you want bu mixing it with a custom route handler Like in my Securing Dynamic Data 4
(Replay) (DD1 or DD4 at least the routing part) article.