I'm trying to use the Manage Rules in a warehouse (or lakehouse) and test the activator, but after trying many selects, the result is always the same, the select is not recognized by the activator.
My guess is the activator is "looking for something" and these selects "don't match", but I don't know what I'm missing.
⊕ Your Fabric notebook shouldn't know your password.
Video: https://www.youtube.com/watch?v=qjUa_gyBAeM
Hardcoding credentials in notebook code is a risk hiding in plain sight.
Anyone with access to the notebook can read them.
Connection Objects solve this. ✓
Authentication lives inside the Connection Object — not in your code.
The notebook uses the connection. It never sees the credentials.
In this week's Fabric Monday, I show how to wire notebooks to Connection Objects
and why this is the right way to handle authentication in Fabric. ▶
⊕ OneLake security roles can have members nobody explicitly added.
That's not a bug. That's Virtual Members. ⚇
Video: https://www.youtube.com/watch?v=GPI50TzJNCs
In Microsoft Fabric, workspace roles and item permissions don't just control the workspace.
They automatically map into OneLake security roles inside a Lakehouse.
▦ Assign someone as a Workspace Viewer.
⌂ They land in the matching OneLake role — automatically, without a separate step.
Most teams don't know this exists and end up managing two layers of security separately.
You don't have to. ✓
In this week's Fabric Monday, I walk through how Virtual Members work,
how the mapping is structured, and what it means for your Lakehouse security model. ▶
★ Stop hardcoding credentials in your Fabric notebooks
Video: https://www.youtube.com/watch?v=aDZoobJvF1k
Running a notebook with your own identity works in dev.
In production, it's a liability.
★ This week's Fabric Monday covers the tricks you need to know to run notebooks securely using Workspace Identity — through Connection Objects.
It's not just "enable workspace identity and done."
There are steps that must happen in the right order,
settings that can only be configured at creation time,
and permission assignments most people miss the first time.
Watch the full video to avoid the pitfalls before they hit you in prod.
Hi,
I'm trying to learn more about the plans, is there a how to or step by step that we could follow and that correctly illustrate what we can do with it?
I started with a pre-defined idea: To make a forecast for future years.
What challenges I faced:
- "Future years" would be new values in an already existing column in the semantic model. The plan allows to create new columns or rows, but not a value in a new column.
- There is an explicit forecast feature for this. But the maximum the forecast feature reaches is to copy the original value of an existing year to all future years. I can't define a formula (for example, add 10% increase in each year - it doesn't work).
Yes, there is a space for formulas, in the default value definition, which is only processed if the source is empty.
In the end, the forecast only creates the space for the values, any calculation would need to be manual.
I don't see a space/how to create a custom variable (percentage variance) to control the forecast.
Am I asking for too much ?
I believe I may have the wrong point of view, I would like to understand the good sides of the "plan", what we can already achieve with it, considering my initial idea of forecastign "underperformed".
Thank you in advance!
