Thread
#secoda-support
    a

    acceptable-appointment-12725

    1 year ago
    Integrated Metabase but nothing shows up in History tab
    Is it supposed to appear similar to Postgres where it shows if the extraction was successful or not?
    e

    elegant-house-93198

    1 year ago
    Hi Krizi, can you refresh and try the extraction again. The most likely reason why it's failing and not showing why is because there is an invalid username and password being used, or your session token has expired on Secoda (refresh would fix this). But either way you're correct that this should be showing an error of why it's not extracting, which is a bug on our end.
    Hi Kriza, I can see some errors coming in from your extraction attempts. Our Metabase integration makes the assumption that your Metabase dashboards are organized by groups, and it looks like there's an attempt to get a dashboard without a group which is causing an error. I can fix this issue so that you're able to perform the extraction. Apologies about that problem. And I will circle back here when it's fixed
    a

    acceptable-appointment-12725

    1 year ago
    Thank you, Andrew! Is there a limitation on the Metabase user where it has to be an admin? Another possibility might be an issue with SSO. I logged in Metabase using the Gmail account to confirm I have the correct credentials and I was able to proceed. I've been trying to connect using an account with access to just a few tables, but I am unable to extract data
    e

    elegant-house-93198

    1 year ago
    Thanks for the additional info Kriza, that would be the problem. It assumes that the user is an admin and has permission to view all of the resources in Metabase. When I update the integration I'll remove that assumption so it works for users that only have a few tables
    a

    acceptable-appointment-12725

    1 year ago
    I see, got it. Thank you! Also, a suggestion for deleted integrations, can we exclude them in this view? I also tried renaming the latest integration but it still shows Postgres
    e

    elegant-house-93198

    1 year ago
    Yes that's a bug on our end. Thanks for pointing it out Kriza. We will let you know when it's been fixed