Skip to content

🌿 Microsoft Fabric E2E Tutorial: 🌊Lakehouse | 💙Data Science | ⚡Real-Time Intelligence | 🪣Data warehouse

Notifications You must be signed in to change notification settings

kimtth/ms-fabric-e2e-tutorial

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🚀 Microsoft Fabric metadata created by E2E tutorials

This repository demonstrates how resources are created in a Git repository when Git integration is activated with a Fabric workspace created by following the E2E tutorials.

Tip

A workspace admin can connect a workspace to a Git repository. Using these resources can simplify resource creation in the end-to-end tutorial by minimizing manual steps.

📚 Documentation and Tutorial

📋 Resource Description

1. 🎯 Hands-on by end to end tutorials

2. 📝 Supplement

  • Semantic Link
    • Semantic Link all-in-one demo.ipynb

3. ⚙️ Environment setup

  • Fabric stores metadata only. Actual data (OneLake files, table contents) and connection secrets/credentials are not stored in Git. After a fresh sync/clone into another workspace, you'll typically need to recreate or rebind connections and re-enter credentials.
  • Manually fix a failed update
  • Re-deploy the semantic model:
    1. Copy the SQL connection string from the SQL analytics endpoint settings.
    2. Copy the Lakehouse analytics GUID from the Fabric URL. Lakehouse analytics GUID: Copy the second GUID from the Fabric URL
      (e.g. https://app.fabric.microsoft.com/groups/<group-id>/lakehouses/<lakehouse-id>?experience=fabric-developer)
    3. Update these values in Fabric_artifacts/agentic_semantic_model.SemanticModel/definition/expressions.tmdl, commit, and push.
    4. Trigger a Source Control update in Fabric and wait for completion.
  • Re-deploy the metadata
    1. Modify the datawarehouse endpoint in part5_Load Customer Data.DataPipeline\pipeline-content.json
    2. Modify the kusto endpoint in part4_eventhouse_tutorial.KQLDatabase\EmbeddedRealTimeQueryset.json

Trouble shooting

Troubleshooting GitHub sync issues, especially when syncing data to another tenant.

  1. Set the value to null to resolve the “connection not found” issue during synchronization with the GitHub repository.

    • part2_IngestDataFromSourceToLakehouse.DataPipeline/pipeline-content.json
    • part5_Load Customer Data.DataPipeline/pipeline-content.json
    "externalReferences": {
        "connection": ""
    },
  2. The email address in the Fabric Event Alert Tutorial should be replaced with your own email address. The placeholder is set to [email protected].

    • part4_WorkspaceItemChange.Reflex/ReflexEntities.json
    "definition": {
    "type": "Rule",
    "instance": "[email protected].."

    Set your tenant id and workspace id in the json.

    "tenantId": "...", // Get this from Azure Portal
    "workspaceId": "..." // Get from your Microsoft Fabric URL. https://app.fabric.microsoft.com/groups/YOUR_WORKSPACE_ID
  3. Recreate connection for DataPipeline

    • part2_IngestDataFromSourceToLakehouse.DataPipeline: see this tutorial
    • part5_Load Customer Data.DataPipeline: see this tutorial

Resource list

image

Reference

About

🌿 Microsoft Fabric E2E Tutorial: 🌊Lakehouse | 💙Data Science | ⚡Real-Time Intelligence | 🪣Data warehouse

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published