This post is more than 5 years old
9 Posts
0
139373
January 5th, 2012 20:00
vFoglight Table Flows - Passing cell value to pop view input
Hi all,
Sorry if this sounds silly, I'm a relative newbie to creating reports/dashboards and I've not been able to work this one out.
I would like to create a flow based on a table row, specifically one cell in the row which provides a pop based on a cell dwell. The parent table is show datastore summary information, see attached file DataStoerSummary.jpg. I would like to show what VMs are running on the selected datastore.
I thought I'd setup up the properties of the flow correctly: however, when I go to select the view to use as the pop-up it does not appear in available list. I assume this is because the base inputs requirements have not been met, therefore it doe not appear
The view I wish to use essentially requires a datastore as the input, see attached view inputs.jpg. I thought I have supplied this information via the flow however it is not working
Help, any assistance would be appreciated.
Thanks,
DELL-Brian W
59 Posts
1
January 5th, 2012 22:00
Hi mrs,
You've gone down a path to specify a popup for a specific column in the table, which is a bit different from "create a flow based on a table row".
You define the former using the “Cell Dwell” flow and the latter using the “Row Dwell” flow.
In order to enable the flow to the target view, you need to match the input context of the view which is named “VMWDatastore”.
Assuming you want to carry on with the “Cell Dwell”configuration, you need to change cell dwell.JPG so that:
SelectedRow: VMWDatastore
SelectedColumnId: SelectedColumnId
Cell Value:
Context Key: SelectedColumnId
Setting the SelectedRow to “VMWDatastore” matches the context name in the target popup view.
Then to define the dwell action for the column that shows the names of the datastores, you need to set cell dwell - popup.JPG so that the Case Value matches the ID of the datastore name column in the Column definition.
Regards,
Brian Wheeldon
mrs1
9 Posts
0
January 6th, 2012 00:00
Brian,
That fixed it, thanks again for your prompt assistance!