I don't have a "good" answer for you, as I'd like to know if there's a more practical way to do this than what I'm about to share. However, as a "worst case" answer:
If each GM login ID was configured to use a SQL login by the SAME NAME (vs. all GM users sharing the same SQL login as MOST of our clients are setup to do), then you could...
Within the actual SQL query itself, for any applicable DATA SOURCE used in the dashboard in question, you could simply have the where clause of the SQL Query say something like this (note ca is an alias for the CAL table, in this example):
AND ca.userid = system_user
system_user is a special SQL function that returns the SQL login currently in use. We only have a small # of GoldMine clients that assign distinct SQL logins (matching their GM user ID) to each GM user ID, but this would work very well for any of THOSE particular GoldMine clients.
Again, far from ideal and probably NOT what you're looking for, but I thought I'd share on the off chance it proved to meet the need.
Hope this feedback helps.
Thanks for the option!
1 of 1 people found this helpful
It would be very useful if GoldMine had a <<CURRENT_USER>> type of macro. As someone who designs dashboards for my customers, I get asked about this a lot. Thanks John for your solution, at least there is a workaround.
While we are at it, I wish there were a similar macro that could "get" the accountno of the current contact record being displayed in the background, to be used as a dashboard parameter.