Forum Discussion
Deneb - How to add measures on another dataset
A couple things:
- You're missing the parent column. I created one based on the numbering of your IDs, although if you are going to stick with this type of hierarchy and eventually add more nodes, I'd consider handling the parent column separately. If you don't need this parent-child relationship visualized, feel free to delete the formula transform that I added to create the parent column.
- I moved all encodings to the update channel and that seemed to get the colors and tooltips working. Unless I want encodings to change in a particular way due to data binding changes, I'll usually always have everything in update.
AlexandreCoutoB, at first glance, nothing jumps out as being off with what you've posted. I took my best guess at creating a spec somewhat similar to what you have (minus having multiple datasets).
Check out this gist. Maybe you can look at it against your spec and figure out where the disconnect is. If this doesn't help, then sharing a .pbix may be the best way forward.
Hi giammariam ,
I did this test too, and it works on Vega editor with a pre-built dataset, my problem is how to create this dataset on Deneb. It seems like it cannot get the field values after a lookup.
As Deneb brings me the measures in this format, I need to do all those transformations on the data until I get the final format required by Vega.
Take a look at my spec here, it's very close to what I did and didn't work on Deneb. I'm creating a sanitized .pbix in the meanwhile.
Hi, here is the .pbix file with the same spec I did on the Vega editor and not working on Deneb.
A couple things:
- You're missing the parent column. I created one based on the numbering of your IDs, although if you are going to stick with this type of hierarchy and eventually add more nodes, I'd consider handling the parent column separately. If you don't need this parent-child relationship visualized, feel free to delete the formula transform that I added to create the parent column.
- I moved all encodings to the update channel and that seemed to get the colors and tooltips working. Unless I want encodings to change in a particular way due to data binding changes, I'll usually always have everything in update.
Hi giammariam ,
It worked now! Sorry for the silly mistake of the missing column, and the encoding approach works for me.
Just an additional quick question, do you know how I can configure a custom linear gradient with the following config? I want to ensure that the color #FF1414 is for calc=0, not the lowest value of calc.
if calc = 0.0, then color = #FF1414
if calc = 0.5, then color = #FFDF4B
if calc = 1.0, then color = #00FFCD
Solution: