m-kovalsky

Thanks for raising this. I'm working on an [overhaul of the ReportWrapper](https://github.com/microsoft/semantic-link-labs/pull/685) which will fix this issue.

This is fixed within [0.10.0](https://github.com/microsoft/semantic-link-labs/releases/tag/0.10.0). Please make sure to use the connect_report context manager as shown [here](https://github.com/microsoft/semantic-link-labs/wiki/Code-Examples#set-the-theme-of-a-report).

Thanks for the feedback. Added the 'shortcut_conflict_policy' parameter in a PR for the next release. Will be expanding the scope of this function to allow shortcutting to different artifacts. I...

Shortcut Conflict Policy has been added in [0.9.7](https://github.com/microsoft/semantic-link-labs/releases/tag/0.9.7).

I don't really think this warrants its own notebook. It can be done in 2 lines of code. Maybe in a script repository would be a better idea.

How are you calling the run on demand notebook api? Please share your code.

Is this semantic model using Direct Lake on OneLake or Direct Lake on SQL? When you create a semantic model using the create_blank_semantic_model it just creates a blank mode. In...

Are you using the secret name or value? You need to use the secret name. The function gets the secret value based on the secret name.

Is the secret expired? Check if this works: ```python import notebookutils tenant_id = notebookutils.credentials.getSecret( key_vault_uri, key_vault_tenant_id ) client_id = notebookutils.credentials.getSecret( key_vault_uri, key_vault_client_id ) client_secret = notebookutils.credentials.getSecret( key_vault_uri, key_vault_client_secret ) ```

It’s the name of the secret in keyvault. It’s not the value of the secret (or the actual client ID). This function gets the secret value from a given secret...