We're having some issues interacting with the Slack integration.
Created app successfully and it is able to send dashboard subscriptions fine - but after adding it to channels it doesn't seem to respond to @Metabase help or metabot help etc. Any ideas? Potentially a network permissions issue on our side - but since it can post subscriptions fine, seems unlikely?
I'm unable to reproduce on that database, but i did find the reason of breaking.
The error was always pointing to a specific field missing.
""ERROR: column source.betaalmiddel does not exist Position: 2836""
So i checked the datamodel and it was set at 'Category' and show values: use custom mapping.
When i disabled the custom mapping and recreated the model, i got the same error on an other field with the same field settings.
I also removed the custom mapping, recreated the model and i was able to do it.
I tried to break it in the sample databases, but i did not succeed.
Important to know, i had to create the model over and over again. If i used a model i created before the 'fix' , it was still broken.
Hey ! May I kindly ask why ? It looked like a cool feature to me. Also, I thought migrating to a slack app would bring more capabilities... but I can't see (yet) the advantages.
@mazzma12 It was legacy code, so it would need a full re-write to work correctly without all the known problems, and too few people were using it and was difficult to manage permissions for.
There's no real advantages to the shift to App - which is also why we kept using the Bot implementation.
I have a question regardin those 'Models' and Dashboard filters:
Is it correct, that you are now able -->to write a native sql question --> convert it to a model --> and using any field in a Dashboard as a filter without setting a parameter within the sql code ?
If this is correct, what do we have to consider to make it work?
Thank you for your kind explanation @flamber I understand the motivation behind.
But I am not sure to grab the last part. Do you hint that we can still use the metabot on Slack ? It looks like it is disabled since the migration to version 0.42
We also ran into some issues with the new Slack App. Maybe someone can help us on that:
It seems that new private channels don't appear in the channel search when creating Alerts or Dashboard Subscriptions. There are some old private ones from our previous slack bot integration. However, new ones don't show up. We tried adding the App to the channel as well as the old Slack bot.
Did someone encounter similar issues or is there a solution for it?
I am assuming that it has to do something with the permission scope. We added group:read but that also did not fix it.
Let me take that on the old channels back actually. I miss interpreted one channel name. In our case it was actually nice to be able to use private channels as well in the past. Haven't done a lot of clojure yet, but I would be happy to contribute in case that is an easy thing.
@Somtom I don't know what it would take, but likely including private channels in the filter, but also permissions, so they're even retrieved from Slack. Then I don't know what would be required beyond that. In other words, I don't think it would be simple and there's several caveats and would require tests too.
Guys, I'm using Metabase Cloud and my account seems not upgrade to the latest version. In "Setting > About Metabase" it says that I'm on version 1.41.6