dbt is a popular data transformation tool that data teams use to pre-transform data inside data warehouses before pushing to the BI layer. However, a common problem data teams face is: dbt and BI tools don’t talk to each other. This leads to problems like:
Disconnected metadata at BI layer: The table fields’ descriptions defined in dbt are not exposed to business users in the BI interface.
Discontinuous Data flow trigger (Stale data in BI reports when data refreshes) : when underlying data tables get rebuilt by dbt, the BI reports might still be using the cached, stale version.
Holistics supports “dbt integration” that solves the above 2 problems.
Synchronisation of multiple manifest.json could be useful (in order to deal with dev/test/prod versions).
And, it is not directly associated to DBT but our dbt docs use markdown extensively. As Holistics does not interpret markdown for data descriptions in reporting view, we tend to change the descriptions in Holistics in order to provide a better user experience, which kind of defeats the purpose of dbt integration .
Interesting, I see why you want this option because you have separate schema for dev/test/prod version.
I guess this is something that has been mentioned in this thread (Development workflow//testing).
This is an important and useful feedback for our team @dacou.
I do agree that to make the experience with dbt more seamless, supporting markdown in reporting would be crucial.
I will add this to our backlog for future improvement. Thanks, Damien.