Comments
-
@trafalger I cannot quite picture how this would work. Would you have a simple example for it?
-
That is how I would like it to look (see below), we found a workaround eventually using 2 fields for the coloring. But it would be great to have the conditional coloring in one and as a reference to a field, like in this example. When it hits the 205 Target it becomes green and when it is under, it is red. But again, this…
-
This is just an example, where the intermediate steps are vizualized in blue. This vizualizations was not created in Domo due to restrictions of the Waterfall Graph.
-
@GrantSmith I was playing around with the searchable filter you suggest - but it doesn't pick up any values from the dataset I am connecting it to; but I might have configured it wrongly (not really familiar with javascript, html or css) What I am looking for is basically this, as a card:
-
Is there any update on this topic - would be great to have some kind of version control to view the changes etc in a more dynamic flow. Can we maybe connect DomoDataflows to Github for version controlling and more details?
-
Hey @GrantSmith I heard about the idea exchange area before - could you please share a link to this space? Thank you :)
-
@jaeW_at_Onyx I am basically trying to get the highest rank for every id, but the rank can vary and be anything between 1 to 10 (so I cannot solve it through a where statement with rank=..). And I am looking at id and addtional id features.
-
Forgot to attach the table.
-
I recoded my Quadrant formula as you suggested, but unfortunately it is still collapsing to Q1 and the row count when just create a view that shows how many agents fall into each quadrant. I attached the table and as you can see all of my variables are created in beast mode. My question now is, is it still possible to…
-
Any Idea why this error might come up? The database reported a syntax error: FUNCTION SPLIT_PART does not exist I used exactly the same split_part logic
-
Checking Remove Hint worked for me ?
-
I tried that and it still seem not to sort the overall volume, but only by the volume of one of the items. I edited my initial post, I hope that helps?!
-
@GrantSmith The challenge is that the data is on a team and consultant level, meaning that 10 rows are not equal to 10 weeks. Can you think of any other workaround?
-
@GrantSmith That is the mysterious thing. When I am within the Analyzer there is NO option for me to select a summary number, but after I save and leave to view the card, it's there :(
-
Hi @GrantSmith , So instead of just creating case when timestamp_var::time between '07:00:00' and '08:00:00' then '7-8 AM' put a 1 infront of it? when fact.start::time between '07:00:00' and '08:00:00' then '1_7-8 AM' If that works, it's definitely an option, I just hoped there is another (easier) way ?
-
Thank you, that does solve part of the problem. Too bad it removes other number pointers on the y-scale. This way I only have 0 and 100% on the y axis. Is there a way to circumvent this?