ACCEPTED SOLUTION
Accepted Solutions
As @Yedukrishnan , described If you look at the bindings from the example. The SeriesClicked and SelectedData are passed to a service. This service then pass the updated information back to the original chart. If you want different behavior, you need to redirect the binding to another service which provides data to the new pie chart or as inputs to a mashup.
I took a look at your question. I put together an Example which does some of the issues you describe. The example was built in ThingWorx 9.4.0
The example has an infotable of raw data(Thing:Community-DropDown-Grid-V3-Thing). When you click on a pie chart segment an InfoTable is generated and used as input to a service. The InfoTable columns:
The above infotable is the output from the piechart widget. This information then becomes the input to a service which generates data for the pie chart.
The mashup Community-PieChart-Mashup:
When loaded the data displayed is Country. You can use the dropdowns to select smaller groups (country, State, County,city)
If you click on the segments the data is reloaded one level down.
The dropdown and clicking on segments do not interact.
This example uses data which has been designed to not display limits in the service. This is an example not a solution.
Regards
pehowe
As @Yedukrishnan , described If you look at the bindings from the example. The SeriesClicked and SelectedData are passed to a service. This service then pass the updated information back to the original chart. If you want different behavior, you need to redirect the binding to another service which provides data to the new pie chart or as inputs to a mashup.
.jpg){kind=link}
