AndreaHenderson Domo Product Manager

This is a good idea. It's a relatively small thing, but can create quite a bit of friction when editing a DataFlow. I'll add this to my list of desired authoring canvas updates.

Good news - this is in beta now. Look for more info at Domopalooza!

@RobynLinden please do! And rumor has it I may or may not have some Magic ETL specific flair to pin on your lanyard, so definitely hit me up for that too. :)

This is a great callout, and one that we are in the process of resolving. We are working on including Window Functions in v2 of the SQL Tile (v1 is in a very limited beta now). I anticipate we will have Window Functions available in the SQL Tile around the end of the year.

This is such a good idea, and something I've definitely had on my personal Magic wishlist for a long time. I will be reviewing this soon with the team.

Such a good callout. I am going to review this with the team. Like Jae said - it probably makes sense to have an "add all" for any tile where you can add columns one at a time.

@trafalger Can you give me a little more detail or an example? I've definitely run into the issue with it not including all columns by default, but I'm a little unsure of the "include all rows" case. I'd like to take it to the team to review but could use a bit more detail first. Thanks!

Good idea - I get what you're saying. This is something I've run up against too. I'll review with the team.

Great idea! I'll review this with the team.

This is a great idea, and I can see it fitting in well with some of the other improvements I'm currently looking at for the Magic canvas (including commenting, more robust on-canvas markup etc). I will add it to my list for review.

Wanted to update you that we haven't lost sight of this and will be reviewing again soon.

This is a great idea! I am going to review this with the team for inclusion on the roadmap.

Good news - this is in beta now! Look for more detail at Domopalooza.

Good news - this is in beta now! Look for more detail at Domopalooza.

Good idea. I've always wondered about this feature too. I'll make sure to review it with the team.

As a Magic user myself, this is one of my most desired features as well. It was one of the first things to go on my "want it soon" backlog when I took over the Magic PM role this year. I feel like I've been seeing a lot of noise around this again recently, so I will be reviewing this again for roadmap inclusion soon.

This is an idea I've been deeply interested in as well, as a heavy Magic user myself. I do have it on my backlog, but with this additional signal, I will review this with the team again. Thank you for surfacing this! I have a lot of ideas along this vein, including better commenting in general, grouping/boxing of tiles…

This is a great idea. I have experienced this annoyance too. I'll review with the team.

Love this idea! I have it on my own "wishlist", and in the roadmap backlog. Reading all this feedback, though, I'm going to make sure to surface it during my next roadmap conversations.

Hello! I'm pleased to update you that development for an undo/redo button in Magic ETL is in progress, and we're anticipating a beta release this summer.

This is an idea I've been deeply interested in as well, as a heavy Magic user myself. I do have it on my backlog, but with this additional signal, I will review this with the team again. Thank you for surfacing this! I have a lot of ideas along this vein, including better commenting in general, grouping/boxing of tiles…

Hi @Fatias - unfortunately it's not possible to make a request outside of Domo within the scripting tiles in Magic. Doing the request outside of Domo and then loading the data to Domo is an option, like you mentioned. Another option is to do the work using a Jupyter Workspace within Domo. You can read more about Jupyter…

There aren't currently any plans on the roadmap to upgrade MySQL to future versions. They product team is prioritizing Magic v2 development and my understanding is that they will be working to add more and more features to bring it to parity with SQL features that might not currently be available (including working on…

One other thought - if the filter values are available within the dataset that the card would be built from, you could write a beast mode around the card metric(s) that would only display data when the filter criteria had been met. This can be computationally intensive and maybe a bit tricky to work out the correct logic…

You can multi-select dataflows from the Dataflows tab in the Data Center and then disable all selected dataflows at once, which is definitely quicker than doing them one by one, but I assume you would like to do it in greater bulk than that, correct? There's not a published API for disabling dataflows, but you can sniff…

A few questions: Is the Python script updating the output dataset post-Magic ETL in order to update the column to 1? Is the output then brought back into the dataflow as an input? (thus creating a recursive dataflow) How are new rows added? (Via the original raw input dataset, perhaps?) Are the new rows ever updates to…

Thanks for the reply. I understand your usecase, and the feature you're looking for is a great idea. As you've noticed, we currently do not have such an offering. Please visit the Dojo Ideas Exchange http://dojo.domo.com/t5/Ideas-Exchange-suggest-and-vote/idb-p/Ideas. You can search existing ideas and then vote for it if…

Hello and thanks for your question! It's an interesting one with a lot of different potential resolutions, depending on your usecase. From what you said, it sounds like you utilize Domo to work with many different business clients, and that some of the business clients have conflicting fiscal calendars. A couple of…

Hello! Thanks for providing a screenshot with your question. Based on the error message, it looks like there is no data available in the dataset for the filters that are applied to the card. Unfortunately, without access to the underlying data and the card features, I don't have the ability to troubleshoot the issue.…

Sorry about that, I didn't have a way to test because I'm not in your instance of Domo. There is an erroneous comma after the first instance of 'UHC'. If you remove that, I think it will work.