You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the output options of Flexibility index are: time plot, common plot, summary table (1 row per org attribute) or full data. What I think is missing and would be really helpful is output of the data used in the time trend chart (1 row per week with the average FI) to be able to recreate that chart in ppt and keep adding weeks of data - customer will do this to track this on a monthly basis as a KPI.
Describe the solution you'd like
return="table_time"
Describe alternatives you've considered
The solution now is to just save the full data (return = "data"), and do a simple summary:
which maybe is the right approach if we don't want to start creating very specific data outputs. If that's the case, I suggest to just save this approach as an FAQ. Thank you!
The text was updated successfully, but these errors were encountered:
Thanks @rosamaryo for this issue. I lean towards adding this as an extra example in the section under https://microsoft.github.io/wpa/reference/flex_index.html, because it is only a one-line code to run. Maybe good to get some thoughts from current users to see what is preferred, because keeping the return options simple would also be great
Currently, the output options of Flexibility index are: time plot, common plot, summary table (1 row per org attribute) or full data. What I think is missing and would be really helpful is output of the data used in the time trend chart (1 row per week with the average FI) to be able to recreate that chart in ppt and keep adding weeks of data - customer will do this to track this on a monthly basis as a KPI.
Describe the solution you'd like
Describe alternatives you've considered
The solution now is to just save the full data (return = "data"), and do a simple summary:
which maybe is the right approach if we don't want to start creating very specific data outputs. If that's the case, I suggest to just save this approach as an FAQ. Thank you!
The text was updated successfully, but these errors were encountered: