lindsay_gillespie Member

We were able to achieve this using Domo Workflows a CodeEngine script to update dynamically based off of specific criteria and by grabbing a distinct list from a dataset. Lindsay Gillespie Analytics Practice Manager | Graphable | lindsay@graphable.ai 💡 Need expert help? Let’s connect!…

@MarkSnodgrass we were able to achieve this using a Domo Workflow but I agree, this should be an automatic feature of variables. Lindsay Gillespie Analytics Practice Manager | Graphable | lindsay@graphable.ai 💡 Need expert help? Let’s connect! https://www.linkedin.com/in/lindsay-gillespie/ Say thanks by clicking 👍 on…

We've achieved this and other dynamic solutions with variables through Workflows and I've also added the suggestion to the Ideas Exchange if you want to upvote it here: Lindsay Gillespie Analytics Practice Manager | Graphable | lindsay@graphable.ai 💡 Need expert help? Let’s connect!…

@brycec thanks so much for the response but unfortunately, is not applicable in this scenario as I must be able to select from any combination of about 10 filters on the dashboard and so none of this can be done on the ETL level.

Right but then I have a value of N/A on my chart that I can't get rid of without filtering out those rows.

Thank you for your help!

Looks like the ReportDate just needed to be sorted by Ascending, not Descending.

@MarkSnodgrass I made this change and my value changed from 790 to 792 with a value change of +2. 790 was the accurate count for yesterday's subscribers. So, I'm not sure where I'm going wrong now.

Also, I have ensured that there is, in fact, a value change between yesterday and the day before yesterday

@MichelleH yes, I did verify that both of those are set up correctly:

@MichelleH thank you. I'm no longer getting an error on the attachment name but now it's saying the file found is the wrong type. This is likely due to the fact that the pdf file attachment has the same name? Any idea on how to fix this?

@JohnMiller Thank you for your response. The only option available to the subscribers with the published dataset is to Open With Analyzer. The screenshot below shows a published dataset in the Subscriber instance that is originally an excel uploaded dataset in the main instance.

@MarkSnodgrass @GrantSmith We can't be the only use case for this. Does anyone have an idea for a work around? Our subscribers need to be able to use these datasets in an ETL or else we don't really have use for Domo Everywhere…