Wanted to throw this out. We need the ability to say one field is equal to the value of another field, and more specifically we want to make pages custom to the user logged in. So for example we want a shot page to be pre filtered to a users location so they are only looking at shot that are designated for LA production. This functionality could also apply to so many other things. Take a look at the attachment.
-Romey
We've also been talking about dedicated dashboards (my pages wrapped up into a single page) that can be assigned to people by group. You could then save a dash for the LA folks with the LA filter in there explicitly. Same for Vancouver. Think that will address your need? If not, can you provide another example or two that helps me understand a bit better?
A dedicate dashboard might create a temporay fix but the truth is we have a few dozen non dashboard pages that need to be prefiltered and having a different dashboard doesn't necessarily address our custom pages.
Having general ability to say one field value is equal to the value of another field from a different entity is the long and short of my request. I can come up with countless uses for this functionality aside from our specific request. Per my specific request, I added a spin that said I want to find all fields who's values are equal to the value of a field in my person page ("Me"). This would make it possible to customize all of our pages with prefilters that are speicific to the current user "Me".
-Romey
-Romey
Hey Mike:
" I can come up with countless uses for this functionality aside from our specific request."
Cool, can you list some here? I'm looking for specific examples of real queries you'd need to support. Hook me up.
Maybe the ability to display, for a given Entity, a field from another linked Entity would be another way to address the same problem...
Alex
Must have been fixed in the mean time as we have been using this for a long time to only display tickets / timelogs for the branch of the logged in users.
Best,
Patrick
PS: Might be good to close this feature request to reduce clutter