Hey Fabricator! It’s another tuesday and WE (aka the whole community! ) are curious to know : - What are you working on? - Any blockers or challenges you’re up against? These could be in a project at work, a pet project, or something in your learning journey. There’s a good chance someone in the community has tackled something similar or has a fresh perspective. So don’t hesitate to share in the comments, or feel free to make a separate post if you’d like more focused feedback. No blocker is too small to ask for advice on, so FEEL FREE TO SHARE ! Looking forward to hearing what you are up to!

Hi everyone! Is it possible to access a keyvault secret using a workspace identity from which the notebook is executed? I mean, a WS identity has access to the AKV, which I know is possible, but will the notebook that runs from the same WS inherit its access? Should I do that, develop using a service account that has a individual access or use a managed identity? I'm a bit lost on this one What would be a good practice here? Thanks!

Have you used "Taskflow" feature to build the medallion based data pipeline? Taskflow supports several templates and testing "medallion" template... Would be great if you share your experiences on this feature...

Hi! Maybe it's a silly question, but I can't get around this issue. When I add a new table to a semantic model (data source: Lakehouse - Create new model) using the web experience (Open data model), the configured fields done via Tabular Editor 2 break its naming (they reset to field name = field source), and I want the name changes to persist This is what I mean: DW: [dbo].[dim_employee].[employee_name] | V SM: 'dim_employee'.['Employee Name'] If I add [dbo].[dim_company], then dim_employee resets and looks like this again, 'dim_employee'.[employee_name] Is this a bug? It seems like a semantic model rollback

Hi everyone! How would capacity consumption (due to interactive queries) work in a scenario like this: - Report is in shared capacity, semantic model in Fabric capacity - Report is in Fabric capacity, semantic model in shared capacity My guess is since first option queries a Fabric capacity via Live Connection it would use its CUs, and in the second one it wouldn't For users to be able to use both reports (let's assume less than F64) they would have to have at least Pro license, right? Thanks!