This message was deleted.
# secoda-support
w
This message was deleted.
l
@careful-application-95617 I know you’re working on Sigma. Can you confirm if datasets are pulled in?
e
@busy-fireman-86564 we do not currently pull in datasets, but we have a ticket to update the integration to do so. The only issue with Sigma’s APIs is the dataset information is very limited. They don’t include columns or lineage information from the dataset, i.e, which workbooks use the dataset.
b
ooh ... hmm. So many (most) of our users will only have access to datasets that are curated in Sigma. Giving them visibility into what a table is/is not used for and the definitions of the columns is a major use case for us. Dashboards is good too, but datasets is really the primary use case.
Any idea when that might be? Is it high on the roadmap?
Oh geez no wait, we just read Sigma's API docs. We'll complain to them! 🤷
👍 1
l
Yeah, Sigma’s API could be more detailed lol
💯 1
b
@elegant-house-93198 can I manually add a table to the resource list? (in a perfect world assigning the source to Sigma) Otherwise where's the best place to hack missing Sigma datasets do you recon? We were messing around with creating a collection called Sigma Datasets and manually writing in important column names. Open to suggestions here!
e
Hey @busy-fireman-86564 would you be ok with having the datasets without the columns? We can push a quick update to the Sigma integration for that.
b
Yeah, I think so? I can perhaps type the important column definitions in the description
Sorry, I'm actually far more enthusiastic about trying this out than that sounded, slack multitasking 🤪 Yes please! I'd love to try that!
😂 1
👍 1