LCash Member

@Godiepi ok thank you for confirming - using multiple beastmodes is sadly what I was hoping to avoid!

@Godiepi thank you! That looks like what I need but I'm struggling to understand how you've implemented the solution. What's confusing me is what's generating the bar values as it all seems to be coming from a single table column? If that's right it doesn't quite achieve what I want as the forecast is split out as a…

Thank you @GrantSmith and @MichelleH! That's worked.

Thanks both! I will raise a support ticket. To confirm @MarkSnodgrass decimal precision is set to 6 but still some weird rounding (or something) going on. Have tried ROUND((5/4),6) as well, same result. The same beastmodes on a non-federated dataset work fine - and like I say other beastmodes on the federated set seem ok…

I'm experiencing the same issue as the op: although I'm using the Google Analytics Advanced connector, I can only access a subset of our GA properties (just GA3 ones). Unfortunately the solution suggested (to create a universal analytics property) is not an option for us as we are trying to access our app data. Domo…

Thanks @jaeW_at_Onyx. I guess the question was really 'Is this a known bug?' since it's only been happening over the last few weeks. I'll flag with support.

Thanks @MarkSnodgrass for the diagnosis, @GrantSmith for the solution, and @jaeW_at_Onyx for the recommendation!

Thanks @MarkSnodgrass and @jaeW_at_Onyx !

Thanks @swagner, that should do it!

Have tried, no joy 😭

Ok, good to know anyway. Thanks for the advice on this!

Thanks @jaeW_at_Onyx ! No luck with re applying the grouping function, but yes I do have a case statement. Could this be causing the issue?

Thanks @jaeW_at_Onyx ! No luck with re applying the grouping function, but yes I do have a case statement. Could this be causing the issue?