Skip to main content

I would like to pass the value in a dashboard parameter to a generic Inquiry parameter using the Link Widget.

Can this be done? If so, what is the proper syntax?

I have tried the following:

GIParameter = DashboardParameter results in the GI parameter populated with the string DashboardParameter not the value of the DashboardParameter.

GIParameter = DashboardParameter] results in the GI parameter populated with the string DashboardParameter] not the value of the DashboardParameter.

GIParameter = @DashboardParameter results in the GI parameter populated with the string @DashboardParameter not the value of the DashboardParameter.

 

Hi @pkohler91 In this case the Link Widget is used for Forms (Customer entry, Vendor entry), Reports, and Dashboards, but from what I can tell GIs are not included in that.

It seems to work better with Selector type parameters but I was able to use the following to populate the AR Invoice report:

Let me know if this helps


Hi @BenjaminCrisman ,

In your example the parameter is static. I’m not sure if the original poster @pkohler91 had this in mind or not, but I’m curious if there’s a way to pass the parameter dynamically.  For example on the Customer View dashboard there’s a dashboard parameter to filter that dashboard by customer.  Is it possible to configure a Link widget on a dashboard that would open the Customer screen and pass in the Customer parameter from the dashboard?

Laura


@BenjaminCrisman and @lauraj46.

Laura is correct, I am looking for a way to pass a parameter dynamically from a dashboard to the Link widget.


@pkohler91 @lauraj46 At this time there isn’t a way to have a dashboard parameter get inserted into the link widget type parameter, at least currently.

Other widget types have the option in the Filter Settings to check the box for ‘Use Parameter’, telling the widget to also consider the added dashboard parameter, but Link type widget does not have this consideration.

I think it could help the functionality of the widget type though so I would recommend adding this to the ideas to get the Dev team to consider it as well as show interest in supporting this from other users


Any updated functionality on this limitation? 


@asmith50 - Doesn’t seem to of had any movement. Hoping to see traction on this idea since to help with larger data set processing. As mentioned by other users, the Condition Filter burdens a much larger resource pool than Parameters and greatly slows the Dashboard loading time.

 


Reply