video1.0<iframe src="https://www.loom.com/embed/059ce1e196834fc6a427de071fb9cc24" frameborder="0" width="1280" height="960" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>9601280Loomhttps://www.loom.com9601280https://cdn.loom.com/sessions/thumbnails/059ce1e196834fc6a427de071fb9cc24-8cb15ba006357633.gif308.4374In this Loom, I discuss two methods for establishing global lineage across bi-directional DBT projects using Dagster. The first method involves linking assets across two DBT projects—analytics and operations—by ensuring that asset keys match, allowing for seamless execution of DBT commands in the correct order. The second method introduces the use of the DBT loom config for cross-project references, which is a bit more complex but aligns with a mesh architecture. I encourage you to explore these approaches and implement them in your projects to enhance data lineage and execution efficiency. Let me know if you have any questions or need further clarification!