https://linen.dev logo
Join Slack
Powered by
Hi team! Me again :slightly_smiling_face: I just w...
# secoda-support
f
Hi team! Me again 🙂 I just want to check one thing with you which does not look logical to me
We have strict Access control
image.png
There is Team having access only to this one Collection Export: Operative
They do not see it in Collections list
If they want to have it available in the Collection list, we need to give them access also to the parent Collections, like Exports and Apps
And that is something we don't want
But we want that they see their Collection which they have access to in the Collection list
What do you think about this?
b
Hey Sinisa, hope you're well! Just looking into this for us.
Appreciate your patience here Sinisa! Just confirming that at the moment, this is expected behaviour. For context, a child resource needs to be associated with the parent resource, which is standard across all tooling. What I would recommend here is un-nesting that specific collection, which should allow you to have it shared between teams and it will then also show up within the collections list.
f
Hi @best-answer-87711. I understand, even though not liking. Another thing: Did you change something on your end? Now our structure look flatten and without hierarchies and we did not do that. It looks to me that parent field got messed up
Also, now the Redshift sync is failing
Can you check why it is failing?
b
Just looking into the sync failure for us Sinisa! I’ll be sharing the feedback regarding the collection permissions with the team as well. In terms of the hierarchy, would you be able to share an example of what looks different?
Following up! I've created a ticket with the development team to get the issue with the redshift integration resolved for us. Will keep you posted on any updates.
f
The answer for the folders: We had a hierarchy, e.g. folder DWH is root folder for all subfolders starting with DWH:, similar to Sources folder etc. It should look like it looks in the main screen, not like it looks on the left screen
👀 1
Hi @best-answer-87711 There are two things in today's status: • Redshift sync is now working. So this is checked • Folder hierarchy in Collections in the left pane is still wrong and not respecting parent-child relationship
b
Hey Sinisa! I was actually able to replicate this on my end as well. The team is looking into this for and I have created a ticket for it. In terms of the redshift sync, I do see it completed successfully on my end as well. We'll be keeping an eye out in case that error occurs again.
f
yes, I meant that, Redshift sync is working, that is why it is checked
ping as soon as you have something for the Collection issue
unfortunately, there is also another (third) thing to report: • When inputting the content, there is Secoda refresh every half the second, so text is saved only if managed to be entered before two subsequent refreshes
b
Will do Sinisa! For this third issue, where specifically are you inputting content?
f
in Collections
👀 1
b
Thanks for flagging this Sinisa, I was able to replicate this in our test workspace as well. I've created a ticket with the development team to look further into this. Looks like it's specific to the documentation tab in Collections only.
f
HI. Any news for this Collection hierarchy? Users are complaining. I hope it can be fixed soon.
b
Hi Sinisa, hope you're well! Got some updates for us here. The PR to resolve this issue is currently in review. Once I have confirmation that it has been approved and deployed, will follow up here.
The issue with the documentation tab refreshing before the text can be saved has been resolved and you should no longer see the page refresh before text is saved.
✅ 1
Hi Sinisa, hope you're well! Reaching out to confirm the issue with the collections hierarchy should now be resolved. Please let us know if you're still seeing any issues on your end.
f
Happy to hear. Looks good now. Thanks
🙌🏽 1
Open in Slack
PreviousNext
Powered by