Concurrent Git Branching in Fabric Workarounds for Data Rehydration?
Hi Fabric Community, We're looking for recommendations on Git branching strategies for multi-developer teams in Fabric. The Challenge: In Synapse, developer branch selection was independent per user. In Fabric, changing the workspace Git branch alters the branch for all users in that workspace, making concurrent development on separate branches difficult. Current Workaround & Pain Point: Fabric documentation recommends creating a new workspace per feature branch. Issue: Rehydrating data for every feature workspace is time-consuming and something we want to avoid. Questions: What is the recommended best practice for isolated concurrent feature branching in Fabric? Are there established patterns (e.g., using shortcuts, thin reports, or shared lakehouses across dev workspaces) to avoid rehydrating data for each feature workspace? Appreciate any insights!
Rayfin/Fabric Apps: support for mapping @entity() to a non-dbo SQL schema
Hello, We are developing a Microsoft Fabric App using Fabric Apps / Rayfin SDK version 1.33.1. We need to organize the physical SQL tables by application module using custom schemas, for example: - schema_1.table_1 - schema_2.table_1 However, the current Rayfin code-first generation appears to use the default dbo schema and generates unqualified table sources. We would like to confirm whether Rayfin supports mapping an @entity() to a table in a non-dbo schema. Is using a non-dbo SQL schema supported by Rayfin/Fabric Apps? If supported, what is the exact decorator, configuration, or rayfin.yml syntax? Regards,
How to deploy OrgApp and OrgAppAudience from one workspace to another workspace using GitHub Actions
Hi Team - I was looking to achieve the CI/CD for OrgApp and OrgAppAudience. I have a workspace-Dev which is Git Integrated and has the OrgApp and OrgAppAudience in below structure format. Sales Results.OrgApp ├── .platform ├── definition └── .children └── Sales Results.OrgAppAudience ├── .platform └── definition I'm trying with to achieve this deployment automation with GitHub actions. Steps performed are 1. Install fabric-cli 2. Login using Managed Identoty to fabric CLI 3. Deploy using fab deploy with config file with Items in scope as "OrgApp" and "OrgAppAudience" Observation Error - It looks the Fabcric CLI does not support this type of deployment. Please let me know the possibilities to achieve this deployment using GitHub actions only. FAQ on the Fabric User GroupsConcurrent Git Branching in Fabric Workarounds for Data Rehydration?
Hi Fabric Community, We're looking for recommendations on Git branching strategies for multi-developer teams in Fabric. The Challenge: In Synapse, developer branch selection was independent per user. In Fabric, changing the workspace Git branch alters the branch for all users in that workspace, making concurrent development on separate branches difficult. Current Workaround & Pain Point: Fabric documentation recommends creating a new workspace per feature branch. Issue: Rehydrating data for every feature workspace is time-consuming and something we want to avoid. Questions: What is the recommended best practice for isolated concurrent feature branching in Fabric? Are there established patterns (e.g., using shortcuts, thin reports, or shared lakehouses across dev workspaces) to avoid rehydrating data for each feature workspace? Appreciate any insights!
Workspace Git Sync Error - Unable to initialize your workspace
I currently cannot sync from git into our central DEV-workspace anymore. I have tryed syncing the git-branch into a different workspace and it works. When trying to sync the DEV-workspace, I instantly get an error "Unable to initialize your workspace". Syncing is not even tried. Please note that to fix a syncing error, we already detached and reattached the git-branch from the workspace.Prepping for DP-700 in ~18 days — what should I prioritize, and where?
I'm sitting the DP-700 exam in about two and a half weeks. I've already been through Aleksi Partanen's 11-hour video course and hold DP-600, so I have the Fabric fundamentals down — workspaces, OneLake, general security concepts, etc. I've also worked through the official Microsoft Learn paths for Ingest Data, Implement a Lakehouse, and Real-Time Intelligence, plus the official DP-700 study guide as my checklist. What I'm trying to figure out is where the real gaps are likely to be for someone in my position, and which resources are actually worth the time versus which ones just repeat what a DP-600 holder already knows. A few specific things I'd love input on: Which parts of the exam tend to catch DP-600 holders off guard — is it mostly the streaming/Real-Time Intelligence side, the monitoring and optimization domain, or something else entirely? For anyone who's taken it recently: were there topics that came up on the exam that aren't well covered by the official Learn paths above? Any specific resource — a course, blog, practice test, or lab — that made a real difference for you beyond the standard Learn paths? Happy to hear about paid resources too if they were worth it. Any recommendations on how much weight to put on hands-on PySpark/KQL practice versus reading — did the exam lean more toward code recognition or conceptual/scenario questions? Appreciate any pointers, especially from people who've taken it in the last month or two given the exam content gets refreshed periodically.Refresh SQL Endpoint activity is not saving Workspace ID in pipeline JSON
Hi Team, I'm facing an issue with the Refresh SQL Endpoint (Preview) activity in Microsoft Fabric Data Pipelines. Previously, when this activity was added to a pipeline, the generated pipeline JSON included the WorkspaceId associated with the selected workspace. However, with the current implementation, although the UI still requires selecting a Workspace, the generated JSON no longer contains any WorkspaceId property. For example, the activity is configured in the UI with: Connection: FABRIC_SQLENDPOINT Workspace: WS_DEV_ABC SQL Endpoint: LH_ABC However, the generated JSON only contains: There is no WorkspaceId or equivalent workspace reference present in the JSON. This becomes a problem when using Git integration and CI/CD. During our pull request from a feature branch to the Dev branch, update workspace from git fails with below error within workspace : Cluster URI https://wabi-us-north-central-l-primary-redirect.analysis.windows.net/ Activity ID xxxxxx-3e44-4124-b273-xxxxxxxx Request ID xxxxxx-94e3-c4a6-1cfd-xxxxxxxxx Workload Error Code RequestValidationFailed Workload Error Message An internal error happened due to failed runtime assertion: ActivityName RefreshSqlEndpoint contains an invalid WorkspaceId <null>.. Artifacts [Display Name: 'dp_execute_master_daily' Type: 'Pipeline' ObjectId: '00000000-0000-0000-0000-000000000000' LogicalId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx'] GitErrorDetails {"artifactType":"Pipeline","artifactDisplayName":"dp_execute_master_daily","artifactLogicalId":"44a1a4aa-366f-ae86-4920-e6cef697746c","rootActivityId":"ba601bfc-94e3-c4a6-1cfd-69b83db2216f","httpStatus":0,"errorType":null,"errorCode":null,"errorSource":1,"targetCommit":null,"artifacts":null,"errorDetails":{"ErrorCode":"RequestValidationFailed","ErrorMessage":"An internal error happened due to failed runtime assertion: ActivityName RefreshSqlEndpoint contains an invalid WorkspaceId <null>..","ErrorParameters":null,"ErrorCategory":null,"IsTransient":false,"AdditionalParameters":null,"ErrorSource":1,"UserInteractionRequest":null},"clientErrorParameters":null,"gitProviderErrorResponse":null,"culprit":1} Time Mon Jul 20 2026 14:24:41 GMT+0530 (India Standard Time) This behavior did not occur previously because the WorkspaceId was present in the serialized JSON. Could someone please confirm: Is the removal of WorkspaceId from the pipeline JSON an intentional product change? If so, how is the deployment service expected to resolve the workspace during Git-based deployments? Is this a known issue with the Refresh SQL Endpoint (Preview) activity? Is there any recommended workaround until this is resolved? Any guidance would be greatly appreciated. Thank you!
