Dashboard and Current/Active Contact Interaction - Is there a Dashboard macro in order to use the current active contact record's ACCOUNTNO value as a runtime parameter?

Version 1

    Details

    Is there a Dashboard macro in order to use the current active contact record's ACCOUNTNO value as a runtime parameter, similar to the macro <<~CURRENT_USER>> for the current logged in user?


    Resolution

    - There is no Dashboard macro available for the current active contact record's ACCOUNTNO as a runtime parameter

    - All available macros are documented in the  Online help via Help >> GoldMine Help >> GoldMine  Administrator Guide > Dashboards Management > Data Source  Management > Dashboard Macros

    - Following is a list of supported Macros that can be used when creating SQL query statements for a New Data Source.

    Date Macros - This group can be used only with date/datetime fields (OnDate, CREATED, etc.)
     
    <<~CURRENT_YEAR>> = current year
    <<~CURRENT_MONTH>> = current month
    <<~CURRENT_QUARTER>> = current quarter
    <<~CURRENT_DAY>> = current day
    <<~CURRENT_DATE>> = current date

    <<~LAST_YEAR>> = last (previous) year
    <<~LAST_MONTH>> = last month
    <<~LAST_QUARTER>> = last quarter
    <<~LAST_DAY>> = last day
     
    <<~FY_END>>  = when fiscal year ends (month) (this is set in the Tools >>  Configure >> System Settings >> Tab Advanced >> Fiscal  year end


    User Macros

    <<~CURRENT_USER>> = logged/current user
    <<~IS_CURRENT_USER_MASTER>> = does current user have master rights
    <<~USER_GROUP_MEMBERS>> = user group’s name, replaced by group’s members list (“, ‘USER1’, ‘USER2’)

     
    Contact Macros

     
    <<~CONTACT_FILTER>> = contact filter
    <<~CONTACT_GROUP>> = contact group


    Runtime Filters


    <<__INACTIVE_STATE__>> = ignore runtime filter (by default value will be placed)
    <<__IGNORE_STATE__>> = ignore runtime filter and its default value
    <<VALUE>> = shows place where value from part will be replaced
    <<VALUES>>  = the same as <<VALUE>>, but several values can be replaced  (our grid supports multi selection)