erikjamesmason Contributor

hey @vaibhavb226 - can't promise i know the answer but could you add some more details to help me or someone else be able to answer? like, when you say you are unable to do so - are you getting a specific error? does the workflow fail? does anything happen at all /or it just results with no indication of anything?

yay! scheduled on roadmap! * sobs joyously *

wow golly gee! thanks @GrantStowell and everyone! and big congrats to @ArborRose, @ColemenWilson, and @MarkSnodgrass for doing the actual hard stuff around here so i can just glean freely :D

no thank you, @ArborRose - i definitely read all your responses to others questions and all! well deserved winning!

squeak squeaker squeak squeakin!

okay so some progress, i can make tables and add them to the app BUT no so much with charts quite yet - i have the TOE for the error but not sure if i should send the entire error response here?

ooh thank you that is helpful - i can be patient haha

awesome! thank you @rolaveson! i didn't know if it would mix up beta opt-ins that we already have so i just reinput the instances for some that we already have plus the other ones

hey @rolaveson - apologies, i should have updated. we reached out to Preferred and within a few days FileSets was back. it does seem like some unexpected resetting occurred, but from what i can tell, we were in FileSets Beta and it was enabled in our instance, but some other GA features were still not enabled - when i…

i've not had that issue, sorry to hear it though!

big agree, this would be huge - especially as we're deciding on "conventions" to somewhat standardize the information kept there as a team

i definitely do this by default in any software i use, despite if i should know better - this would be a great feature for Magic ETL

big fat agree with both @MarkSnodgrass and @akeating - this section from mark stands out to me as something that would greatly enhance our creation process: Also, the designer of the dashboard has no way to quickly look at a dashboard and know what will happen with each card on the dashboard unless they edit the dashboard…

i just wanna say that @mschmidt posted this idea way before me but mine included smiley faces in the title sooooooooooooooo who's the real hero here

my team members ask for this all the time and would be a great addition for when we only need it for reporting and not at the dataset level

@matthewpinson thank you kind stranger whom i've never met before

we're currently in a situation where this would greatly improve our governance. please make this a thing, Domo!

wow, just imagine not having to rework something that you THOUGHT would work but didn't then wishing you never started since you can't just go back a step or two

basically, just add whatever metadata we can get please!

totally agreed!

this is so challenging to get around and find my workflow again. this would be a great improvement

this 100%

absolutely. at least, make it a setting option

we had a big ruckus from our end users on this issue, which is understandable as this should be a standard feature. When we contacted support, we were told that this is expected functionality and that there was no intention to develop anything to accommodate this feature. This is a highly unfavorable response to a request…

I just had this discussion with my team in an attempt to use tags for governance and discoverability. if we could tag all objects, this would create a cohesive centralization solution. i wish I could vote it up a hundred more times

so... this isn't closed, so i'm just gonna add: this is an enhancement that would be a huge win. is there any update on this or even on the roadmap?