Abby Brinks Member

I'm not very technical, I don't know how to map the inputs and outputs, or what to do with the package once it's deployed. My guess is I would add this to a workflow.

That would be amazing! Thank you!

Advanced is available for domogovernance, but not domostats. We would like to disable running on weekends to help save on credits for domostats, but right now this is not possible because only basic scheduling is allowed for this connector.

This would be great! It would be nice to see the dashboard ID from this page as well.

Are you referring to impersonation? That's different than what I'm hoping for. I'm hoping to be able to share the same access that a person has to a new user without needing to rely on groups.

It would also be nice to have different frequency options for manual refreshes vs scheduled refreshes. This would allow people to test and build while refreshing manually on a more frequent basis, but would limit them to less frequent refreshes once they set up a schedule.

I don't want two different lines to represent two different metrics. I want the lines to represent the same metric but for two different SKUs. The SKUs are determined in a column. This will also go for the bars. In the video example, He is bringing in two different fields for each bar. I want both bars in each group to be…

Yes, this would be great! It would also be nice to share filter views to specific groups as well, and to allow individuals to set their own default filter views, since right now, the only way to set a default is to set it for everyone.

Unfortunately this doesn't work for page level filtering since this is an aggregation beastmode. If you want to use this for page level filtering, you have to do this in a dataflow, then it will work.

This would be extremely helpful for tables that have several columns where most of the columns are not very wide as far as the data (like numbers), but the column name is long. This would significantly help with formatting, especially in instances where wrapping is not needed or desired for the data itself.

Above is what I have built. I put an offshoot "checkpoint" off the top rank and window, and this is what I'm seeing for one of the ANIs. For example, in the "two day range", I'm expecting to see 3 in the second row, because August 1 is outside of the 2 day range, but it's considered the previous row in the rank and window.…

Thank you! I need to have each call broken out and I believe I've figured out how to do that by doing another rank and window off another branch of the input without a grouping and to do a row number function, orderying by timestamp, and partitioning by ANI and date. I'm then joining the other grouped rank and window back…