Secoda Community

<@U01MHQR7DE2> I think we might have missed this question

Sorry about missing this <@U02K8BY6RCK>! It’s not currently possible, but we can add an additional option to use Google credentials for authentication. Let me see if I can fit that into our priorities this week since a couple of other customers have requested this as well

<@U02P9HZGUJH> this is fixed now. Let me know if you’re able to run the dbt extraction now

Thanks <@U01MHQR7DE2>!! It's fixed. Y'all are amazing.

Hey <@U02HEA5UD7F> I’m fixing this now, I’ll let you know when the fix is live.

It works, thanks Andrew :slightly_smiling_face:

Secoda documents data pipelines like Airflow. If you’re hoping to document API’s, it can get a little more tricky. Any additional detail on the structure and storage helps us understand if it’s possible with Secoda.

Screen Shot 2022-05-10 at 4.12.38 PM.png

image.png

There was a small issue with the “issue” button that we noticed today. It was creating an error that was crashing the app. We quickly removed it so we can fix it without effecting with the end result. We’re currently working on a fix.

Thanks for pointing this out <@U031Z4XUNMD> we’ll push a fix for this cc <@U02N4NXTTJR>

Have you confirmed that you are in “editor” mode? This could be happening in “viewer” mode if you don’t have access to a certain resource. This toggle is on the bottom left hand side of the application

I was in editor mode yes. I asked my other teammates to check on their end and they are seeing the same thing

I can't access any pages, even when I go to the home page I get the spinning icon with nothing else.

Hey <@U0324KSPYFR> we’re pushing a fix for this right now. Apologies about that issue

Thank you Andrew! Appreciate the quick turn around!

Everything is back up and running! Thanks again!

Thanks <@U02N4NXTTJR> for pushing the quick fix!

Hey Ryan thanks for the feedback. There’s a bug with the state of the application after adding a collection. To workaround this bug while we fix it, I’d recommend refreshing the page after adding or deleting a collection. Let me know if that works for you

Thanks <@U01MHQR7DE2>! All good - if it's a known issue, I'm happy to just wait until you get to it :slightly_smiling_face:

Thanks for bringing up this issue Ryan. While we’re fixing the bug what you can do is navigate to the docs page (<https://app.secoda.co/docs>) and re-select the document. It’s not an ideal experience but just a temporary workaround while we fix the issue

I made this quick video to help: <https://www.loom.com/share/b77d4335da0049b49a9915da7de22b1c>

Hey <@U02739P8464> this is an issue on our end. We should have fixed for the start of the next week. I’ll update you here when it’s resolved.

It seems that we still have the same issue, do you know if it’s been fixed?

Hi Kevin, please try clearing your cookies!

Hey Ryan, I’m taking a look right now. Will let you know what the issue is asap

<@U031Z4XUNMD> could you try signing out and signing back in. I think it’s a cache issue

Try deleting cookies/localstorage or opening in incognito, both did the trick for me

Hey Ryan, we’re just looking into the columns and preview not showing up. I’ll have any update for you soon

<@U031Z4XUNMD> this should be working again. Let us know if that’s the case

yeah, the preview is working now. still having trouble searching for tables and not seeing all of the tabs like lineage and columns

Could you send an example table over <@U031Z4XUNMD>

only way i got to feeder is it shows up when first going to the "Search" page

A business plan is not required. We are able to generate the ERDs off of foreign and primary keys. Do you know if those keys are defined for your database? If so it’s an issue on our end that we’ll have to look into

Ah, I don't believe we have fk's defined in the db - without these is it not possible to manually generate?

It’s not currently, but that’s a good idea for a future feature. Would you find it useful to manually specify which columns are related to each other?

<@U01MHQR7DE2> What about dbt’s relationship tests?

PKs and FKs are not universally supported by all data warehouses, and their definition,enforcement and utility varies greatly across platforms.

off the top of my head, i know Redshift and snowflake don’t enforce referential integrity. not sure about BQ.

I can use them in Postgres, but I’m just building up technical debt for my future self when I need to ugprade to a true DW

I am using <https://github.com/gouline/dbt-metabase|dbt-metabase> to carry those relations from dbt to Metabase…would be great to see simialr functionality here

That’s a good question <@U031Z8ZV249>, we only use PKs and FKs for relationship databases like Postgres, MySQL, Oracle, MS SQL which do support them. For data warehouses like Redshift, BigQuery, and Snowflake we use query parsing.

dbt provides a lot of the information in their metadata that gives context on the relationships between columns and tables, so we would use that for understanding what column a test is running against. Does that make sense?

It is possible to extract this info! You’ll have to follow the steps outlined here to get that lineage information <https://docs.secoda.co/integrations/looker#h_306dadb3b4>

Hi <@U03J1Q56MKL> I’ve sent you a DM responding to this

Hey <@U03C85WHYSX> I’m just taking a look at this now. Will have an update for you shortly

<@U03C85WHYSX> which dashboard gave you that permission error?

And to answer your first question, editors are able to delete dashboards from a collection. Is that not what you’re experiencing? If so it would be good to know which user that’s happening to

&gt; which dashboard gave you that permission error?
Any question give me this errorwhen clicking on it.
There are listed in a <https://eu.secoda.co/dashboard/> ... page, Charts view
Like when I click on this first row (see picture below)

&gt; And to answer your first question, editors are able to delete dashboards from a collection. Is that not what you’re experiencing?
Ok cool! No it's not, I tested with an editor account and it does not show the three points in the top right corner of any dashboard (see picture)

That’s good to know about the three dots. In the meantime while we fix that, an editor can add a resource directly to a collection through the “Add resource” button

I’ve also added the Metabase bug to our backlog. It appears to be an error with the extraction and how we’re building the URL

Last but not least :grin: It seems that the Secoda version of the Metabase dashboards keeps in memory all the queries that have been once on this dashboard even though they are not on the dashboard anymore.

=&gt; I would like to get a current view of the dashboard
So would it be possible to get an automatic update the dashboards? Or at least give us the possibility to delete the queries?

Thanks in advance !

Hey <@U03JFBY7CDU>, how’s the new role? Nice to see you back here. I’ll follow up in our DM message :slightly_smiling_face:

Hey <@U03JFBY7CDU> good catch. We were in the process of bringing the EU instance to v3 but we experienced some issues on the US instance last week so we decided to delay it until this week now that v3 is more stable. So v3 should be available before the end of this week for the EU

Hey Kevin, let me see which workspaces these users are a part of. If they’re invited to your workspace they should show up in your members list with an “Invited” tag beside them

If you could DM me their emails that would be helpful

the read our docs link under get help take me to a not found page.

I’m just taking a look at this <@U03H5HV3BQE>

Capture d’écran 2022-06-09 à 15.14.17.png

Capture d’écran 2022-06-09 à 15.14.25.png

Hey Alexis, I can remove these for you. I’ll let you know when they are removed shortly

<@U03JFBY7CDU> this should be fixed now, let me know if your search indexes have been updated correctly

Screen Shot 2022-06-10 at 10.38.54 AM.png

Thanks, I’ve added it to our backlog: <https://linear.app/secoda/issue/SEC-954/duplicate-collections-in-the-table-drop-down>

Looks like it re-pulled my data. So I’m good!

Hey <@U03G8FEL26P> if you ever need to re-extract manually just click run extraction on the history tab

It’s for both! There should be two options in the integrations list

Hey Ryan, we do this automatically now on the latest extractions. So if you run an extraction for Snowflake and dbt it should remove anything that Secoda does not have access to

Okay, then there's a bug somewhere. There are a lot of tables showing up in schemas that Secoda does not have access to.

For our snowflake `analytics` database, Secoda can only see `analytics_staging`, `analytics`, and the `information_schema` as shown in the integration settings. I can also show you from Snowflake's side if needed

I can see in our logs that there’s an extraction currently running, so I’ll double check once that extraction has run. If it continues to show these schemas/tables it doesn’t have access to I’ll remove them for you

Okay, sounds good. And here are the schemas in Snowflake

<@U031Z4XUNMD> it looks like those schemas are selected in your dbt integration schema list. So you’ll have to uncheck them from there

oops okay working on deleting them and rerunning now, will let you know. thanks!

hey <@U01MHQR7DE2>, we're still seeing these schemas/tables even after unchecking them in both dbt and snowflake integrations and rerunning

Hey <@U031Z4XUNMD> apologies about the delays on the response. I’ve been OOO since June 16. I’ll be looking into this issue today

hi <@U01MHQR7DE2>, great thanks! I am still seeing this issue today

Hey <@U031Z4XUNMD> it looks like our stale data detection is not working for those particular schemas. We can manually remove the tables that aren’t associated with the schemas above. I’ll just send you an excel of the list of tables so you can confirm before we remove them

Hey Ryan, could you let me know if the tables are gone now? We pushed another update that should have fixed it.