Feature Requests

Today I can choose individual users to notify when crawlers fail. It would be nice to also configure notifications to send to Slack channels.

Our sales team builds looker reports based off of salesforce data but they may not know all the objects/fields that exist within salesforce. am writing to request assistance with integrating Salesforce data into our Metaphor platform. We believe that this integration would greatly benefit our sales team, analysts, and BI teams by providing them with enhanced visibility and accessibility to Salesforce data within the Metaphor environment. Here are the key points regarding our request: Salesforce Metadata Reporting Challenges: Our sales team currently works with Salesforce and builds reports based on Salesforce tables. However, they may not have comprehensive knowledge of all the objects and fields within Salesforce, and they lack visibility into the metadata associated with these tables and fields. Salesforce Integration: Salesforce serves as the source of many tables within our Snowflake data warehouse. Therefore, after the integration, we expected to see these connections reflected in the lineage within Metaphor. This visibility into the lineage would significantly benefit our analysts and BI teams in their data exploration and analysis processes. Potential Impact and Benefits: Salesforce is the primary tool utilized by our sales department, and integrating its data into Metaphor would unlock a wealth of new possibilities and insights. By bridging this gap and providing visibility into Salesforce tables and field descriptions within Metaphor, we anticipate a substantial improvement in our ability to generate the reports and insights needed to drive business success. Salesforce Metadata- https://help.salesforce.com/s/articleView?id=sf.data_classification_metadata_fields.htm&type=5 Example of the lineage in Salesforce and the main entities is attached Thanks!

Instead of just applying the column description to every column that matches the pattern, allow applying the description only to tables downstream of a particular one.

This way we can: a. make our user happy by providing him with a an answer b. effortfully add content to the model

import the meta dictionary from dbt models into metaphor. ideally display those meta tags as custom metadata on the materialized dataset sample meta tag : config: meta: { "owner": "owner name", "email": "owner email", "Last Author": "author name", "Owning Team": "BI", "Business owner": "business owner name", "Domain": "HR", "Sub domain": "Employee managememt", "Data freshness": "Daily", --Live, Hourly, every X min,custom "Aggregation level": "<field_name> , <field_name>", "Tags":"ab_test, multiproducts" }

In contrast to the lineage, the ERD will display the possible linking between the table entities and not the actual data flow. This will help the user to understand how he can use a table rather how it was built

instead of having a user go to the dbt model everytime, show the dbt compiled code for the model next to the columns on the materialized table

Search results should be easily exportable to a spreadsheet to help sharing/collaborating etc outside of Metaphor