Skip to main content

Tag: datatoolspro

Closing AI BI Chat Loops in Snowflake for Conversational Analytics

Posted on by
Infographic diagram of Snowflake's Cortex Agent workflow: end-user skills, cortex agent, data tools radar, observability, and analytics engineering with feedback loops.

In this article I frame and explain the processes I built around Claude and Snowflake to enable production conversational analytics. There are few if any real shortcuts to building an AI analyst agents without an existing data and analytics foundation. An existing Business Intelligence foundation already has semantics, context, lots of connections, and curated understanding. Those foundations can take years to solidify for most companies. The noise to signal in BI systems for AI to consume massive. It carries a lot of bloat, ambiguity, and bad habits that can carry over into your AI agents and produce the same traps for failure.

Starting a new semantics structure in a new platform, technology standard, or tool will yield the same result if you do not establish a strong foundation and process. In this article I provide guidance on my learnings and how I have delivered and continue to manage production AI analysts for credit risk and marketing.

In my primary production environment, I found that 70% of the BI reporting and dashboard requests went away. The remaining 30% is a new class of reporting and dashboard request, where traditional BI tools have become the largest friction point. This is one of many “loops” between analytics builders and information consumers that won’t reveal itself until you have real adoption and accelerate progress forward.

Challenges with Conversational Analytics

Challenge 1: Determining “Important” and “Correct” Context

The hardest part of producing meaningful conversational analytics is determining “important” and “correct” context from existing analytics. Some of that work to separating good / bad context is the basis for the work I started at DataTools Pro in 2023. In this case, bad is anything that introduces ambiguity that can distort descriptive statistics. I use subjective words like “important” and “correct” to highlight why it’s so important to start your AI agents with topics, semantics, and analytics use cases that already drive important decisions today. If you do not have wide adoption of analytics influencing decisions at the start for grounding, you are setting sail on your AI initiative with strong headwinds.

Some ambiguity naturally exists to interpret metrics to arrive at human understanding. How you encode that ambiguity inside of your AI / BI context can poison AI’s ability to stay on track in real world conversational analytics workflows. Evaluating single question with input / output may pass a test. Longer, multi-turn conversations where knowledge and understanding happens requires strong semantic alignment between person and machine.

Challenge 2 – Removing Ambiguity

Decoding ambiguity is a regular business activity every day when people use any business system, including BI. Objectively, the business, data, technology lexicon is a dialect that new people and new agents need to learn. To solve this problem I read a lot of recommendations to “add more context.”

Adding more layers of meta data, skills, context, and AI turns over this data will reach diminishing returns in some form (quality, cost, time). An anecdote I have experienced is business users asking for faster response time where the SQL execution time is <150MS.

My entire AI BI delivery lifecycle calls for continuous reconciliation of context, refining what is important, and removal of ambiguity and layers… This is at the expense of prioritizing correctness and impact over coverage.

As a result, when something does go wrong, rarely is it an AI black box problem.

Removing Ambiguity by removing information. A great example I use is Billing and Shipping state. The semantic meaning is clear for operations for where to bill and where to ship items. For my analytics use case, billing state covers 90% of questions for segmentation. As a result, I remove shipping state from the semantic model and that context is expressed. The alternative approach to add 2 columns and add context for which column to use feels intuitive. The reality is the LLM will at some point get it wrong.

Challenge 3: Prioritize grounding users with BI without repeating BI pitfalls

Delivery and adoption have always been a challenge and a well known black eye for Business Intelligence. The dashboard backlash we see online is a function of technology vendors new solutions to old problems, rarely anticipating some of the new problems highlighted in this article. There are many anecdotes I have experienced in my failed experiments, but the work I do at BIChart has re-taught me that 30-50% of dashboards sitting inside of BI platforms may not be relevant or un-used.

When I started building my first credit risk AI analyst, I selected a widely adopted and trusted BI dashboard for my grounding exercise. My first generations agent needed to understand how to produce and answer any question from BI. On average 30% of what existed in my BI dashboards didn’t need to exist in my AI semantic layer.

Objective – Build High Impact Conversational Analytics

Agent Objective – My approach to conversational analytics was starting with individuals in a small enterprise who directly influence 6 and 7 figure decisions. Otherwise the juice isn’t worth the squeeze. I don’t believe AI analyst agents should be built to save clicks, minutes or even hours… For those use cases there is immense value in traditional automation with AI reasoning steps.

Agent Delivery Objective – The time and cost to build conversational analytics requires lifecycle management that is different than building apps or BI dashboards. This is a CI/CD and governance exercise. The last thing anyone wants to experience is a continuation of business intelligence delivery problems: Initial excitement followed by abandonment.

Framing Real Conversations in Conversational Analytics

Due to the gravity of the decisions, my perspective is the conversation between a user and an AI agent should stay a private, user-controlled space for exploration, ideation, and iteration. Users need room to ask questions, test ideas, bring in their own data, and work through half-formed or sensitive thinking, without assuming the full history is being watched. Even worse, if that chat becomes context for someone else’s session and decision, that kind of feedback loop is dangerous. Specifically for executive users, this is tricky governance problem. An executive chat can carry strategic initiatives, partnership terms, trade secrets, and other need-to-know risk.

That underlying data fed into those conversations also needs to follow a governance policy. Access and audit trail is important for this article because it’s the basis for continuous improvement and how I monitor the system.

Delivery and Training

Participation and training information consumers (end users) how to engage with conversational analytics tool cannot be understated. For me, giving access to Claude + Snowflake required a mandatory 1-hour lab session. My first few generations of LLM was deployed with ChatGPT with over 40 hours of labs. This observation period was great for everyone in the room. I leaned more in 10 hours of labs than 10 months of building and publishing dashboards.

This was the basis for my feedback loop design. I solved for extracting the session notes for continuous improvement. I cover this in my Chat Feedback Skill below.

Closing the Decision Loop: Embedded Conversational Analytics Where Work Happens

My long running secret to BI adoption comes down to one thing: embed analytics where people already work. Logging into a BI portal is a vendor-prescribed experience. A BI portal is something I consider barely tolerable by today’s standards. At organizations that have adopted Claude for Business, I have watched the way of working shift. That will keep evolving, and Claude will likely end up as a stepping stone toward whatever comes next.

Semantics over Semantics

When I speak to different experts, a lot of disconnect exists on semantic layers. Tech vendors are solving systems problems like interoperability, standardization, and distribution without identifying what actually yields the best result. I don’t address any of these things in this article because I believe when enough semantic layers get deployed and folks find it isn’t enough, the next evolutionary step will occur.

The Outer loop: Understanding to Action

To better understand the scope of the actions and decisions I am catering to, I provide my lens on the steps toward “data influenced decisions.” This nebulous marketing headline does have real meaning at its core.

  1. Information seeking motion requires data and analysis of events, prior actions and outcomes related to established metrics.
  2. Data and analysis curated and processed to create understanding.
  3. Understanding requires context take action.
  4. If consensus or authority is needed for action, an artifact explains the new understanding.
  5. Communication and authority carries the directive and action occurs.

I have experienced AI tools like Claude accelerate decision makers ability to move through this loop faster. When the semantics and narrowly scoped along with data access, you can get incredible results. The problem shows up after that isolated conversation ends:

  • The understanding lives in AI memory / conversation
  • The data / BI platform stays disconnected from work
  • The knowledge stays with the individual and downstream communication channels.

There are approaches to integrate and productize these decision loops. There was an incredible article that touched upon capturing decision traces and processing those signals at scale. All of the “big data” hoopla re-packed is a big problem for others to tackle. For now, I consciously built my own simple tools, loops and will continue to watch innovation round robin to come back to Snowflake on a regular basis.

Closing the AI, Semantics, and Context Loop in Snowflake

Instead of framing every component in my process, here’s narrowed visual of 2 context loops. This is the contextual shape of my AI BI delivery heading into Q4 2026. It will look different again by Q1 2027 as Snowflake and Claude evolve and improve. This lens on my workflow was built with Claude and Snowflake; no third party technology required.

For these loops to work, you need

  1. Analytics competency. Part of that competency requires some level of adoption and trust with analytics / BI in your organization.
  2. Business metrics governance. This is continuous refinement, reconciliation alignment of definitions that drives acceptance and understanding how metrics are expressed and reported.
Conversational Analytics

Understanding Adoption and Utilization: The Data Loop with DataTools Radar

Snowflake ships a strong set of observability tools. Observability gives a structured, narrowly scoped replay of what happened inside Snowflake. That raw data carries real value, but not the direction needed to actually improve the conversational analytics experience. Snowflake’s foundation is flexible enough to build a bespoke layer on top, tuned and contextual. To turn that into actionable intelligence, I built a Streamlit app that runs inside of Snowflake as a simple observability layer that is built for understanding and action instead of displaying log data. It’s not a product or a service, but rather a fast way to browse my Snowflake estate. This tool was vibe coded by voice on my way to the office and it turned out to address most of my basic needs.

Automating Recommendations and Remediation

Understanding what happened is nice. Acting on it immediately is my objective. I measure success, adoption, session success rate, and remediation time.

Snowflake Cortex is earning its keep here: sifting that context and surfacing recommendations stopped me from burning time looking at chat logs. The “Profiled” questions come straight from real conversations, grouped into 48 recurring topics.

This console is my productized proactivity, something Business Intelligence never delivered.

Business Conversational Loop – Chat Feedback Skill

In my setup, Claude remains the business context and action interface. To close this loop, I created a Chat Feedback Skill. Back to my original objective of removing noise and focusing on what is important, I train users to control the feedback loop and submit feedback when:

  1. They have to re-direct the agent because information is “wrong”
  2. They feel the response is not credible.
  3. Information is missing from available data
  4. Errors / disconnects and other issues

The Snowflake agent receives a request to a Chat Feedback Tool . Cortex processes that feedback using a stored procedure. The skill itself shares back to the Claude user exactly what is being prepared as immediate feedback loop. That preserves psychological safety and governance that only the issue itself is captured. I have 100% participation because everyone understands this is a structured way for continuous improvement.

In my multi-agent setup, the business conversation happens in Claude, because that’s where the work already happens. The analytics + governance is designed to protect that flow for accuracy and governance purposes.

As you can see, the output of this skill gives the analytics engineer in Snowflake actionable guidance directly. On average 8 out of 10 logs are fed into Claude Code / Cursor and result in immediate remediation with no adjustments before landing in my CI process. I have been experimenting how to deliver full remediation loops, but I prefer to have full control and enough observations before automating.

Building Conversational Analytics on an Agile AI BI Foundation

BI architects build durable systems meant to answer a wide range of questions, including ones not yet asked. Semantic models give builders, and now LLMs, coverage, context, and a declarative path into governed data. All of that work is extremely important. A dimensional model should exist for foundational metrics around which an enterprise is built.

From that foundation is a need for business events and dynamics that influence those metrics. Sometimes at the speed of business (same day) and sometimes retrospectively when enough time passes. That tension between a tightly governed structure and a continuously evolving business is imperfect by nature. Trying to perfect it is defying nature. Adapting to what is most important and predictive is where progress happens. I see the new wave of vendors tackling these problems with a deep understanding of what plagued BI and am always on the lookout for those that actually address what happens when AI Analysts are the norm.

The data platform I choose first remains Snowflake. It remains my preference for now because it works for both small, medium and large enterprises. For my initiative I already had a DBT repo that evolved into a mono-repo that holds:

  • dbt transformation pipelines / process
  • dbt models (fact and dimension tables, business views / marts)
  • snowflake semantic models
  • tests / validation
  • artifacts for skills
  • a version controlled metrics glossary (managed from DataTools Pro)
  • docs
  • continuous integration code

I do however, use and integrate multiple data platforms, including PostHog (runs on Clickhouse) into my agent deployment approach. I reject the idea that all data and semantics need to exist in one place with one standard to reach a fictious point of clarity and understanding.

Evolving that Foundation with Snowflake Semantic Layer

My early success using AI to do descriptive statistics work didn’t require a semantic layer. I simply converted and refined my BI semantic layer into a highly detailed metrics glossary, that was originally built to automatically extract and govern metrics that originate in Salesforce. Here is the natural evolution for context curation that started 18 months ago and reached production in June of 2026.

Gen 1- Claude + CSV files (from Snowflake export) and metrics glossary and prompt
Gen 2 – Claude + CSV files (from Snowflake export) metrics glossary, ontology (entities), information categories and analysis
Gen 3 – Claude + Agent Skill (industry summary) + CSV + (from Snowflake export)
Gen 4 – Claude + Agent Skill + Cortex Skill + Snowflake Semantic Layer + CI-CD + first evaluation
Gen 5 – This article covers where I landed in my Gen 5 configuration as I work on the next evolution.

What I Learned Building Conversation Analytics?

Traditional BI and and semantic layers is not enough to deliver conversational analytics at the speed business leaders want to move.

  1. Semantic layers offered across most platforms still don’t have the depth, curation and governance to scale conversational analytics agents beyond simple foundations.
  2. Understanding conversations require capturing the entire context of a conversation without storing the entire conversation itself. This is occurring outside of the data platform. Convincing an executive that has adopted Claude or Chat GPT better be an order of magnitude better.
  3. Delivery and training of agents is not the same as apps and BI dashboards.
  4. The best early adopters of conversational analytics need to have a higher than average data literacy

Distribution
Vertical integration with embedding agents inside of Slack and Teams is one tactic that I think will play a big part to activate consensus based decisions. That is more relevant in larger enterprises. My experiments operationalizing agents in Slack have not gone so well.

Business Context Curation
Building conversational analytics is an exercise of curating context, packaging the collective knowhow and continuously improving and refining that process along.

What’s Next?

There are other skills listed in my diagram that I will cover in future articles and a whitepaper I wrote in June when we reached production readiness. Hopefully this lengthy retrospective had some nuggets of knowledge for folks working through the same challenges. I am not available for consulting / services but always happy to hop on a quick chat with anyone working on these same problems.

Testing Salesforce External Client App with our DataTools Portal

Posted on by
AI Assistant

This week, I had a chance to update documentation and explore Salesforce External Client App configuration. There have been so many changes to Salesforce connected apps in terms of integration and commercial requirements. It is daunting for customers and partners.

What is Changing from Salesforce

  1. 3rd party tools that use the deprecated “Connected App” functionality will no longer gain the ability to connect to new Salesforce orgs in Spring 2026. Partners will need to upgrade, or get left behind. We are going to fork DataTools Pro app to no longer use Salesforce for federated access to DataTools Pro.
  2. Integrated apps will need to join Salesforce App Exchange where fees are collected. This is going to cause a ton of friction and headache for vendors. DataTools Pro is already integrated into the AppExchange so this does not impact us.

What about Internal Built Apps?

This is an area that’s genuinely confusing and murky, so I decided to jump right into it by building our new customer and partner portal. It sets me up where Salesforce the system of record for customers, but events and activity related data are linked only by a single external UID.

The portal integrates with our support Slack, Salesforce, OpenAI, Stripe, and the DataTools Pro app. After running this experiment, it’s easy to see why Salesforce is scrambling to control and monetize the data within Salesforce.

When you build a portal / community in Salesforce, you are building for a point in time that has passed. We have opened up our portal for anyone to login via magic link to poke around and will rollout our new DataTools Shop in 2026!

https://portal.datatoolspro.com

We are moving to a more traditional federated login configuration with Google and Microsoft / Entra, and expanding our enterprise-specific SSO support.

Learn how to Setup Salesforce External Client Apps

If you are interested in the nitty gritty details of configuring Oauth for External Client APps, I have updated our Azure DataFactory tutorial to explain the process

Worksheet User Alternatives to Snowflake Workspaces

Posted on by

For the last 5 years, I have enjoyed deploying Snowflake workheets to data workers who wanted quick, secure access to curated data assets. I was recently sent scrambling to find alternatives to Snowflake workspaces for data worker roles who are not engineers by trade.

Worksheets were a quick and easy way to access data, administer Snowflake, and share SQL. Recently, Snowflake rolled out its next-generation Snowsight experience. The default SQL authoring experience shifted from a minimalistic editor to a IDE (integrated development environment) user experience.

Why are our users looking for an alternative to Snowflake Workspaces?

There are 3 reasons why customers have immediately asked me for an alternative to Snowflake Workspaces.

  1. Confusing and overwhelming user experience – My users are using words like “hate” and “complex” to describe their experience. After a few weeks, some have adapted but I have seen usage plummet.
  2. Sharing – The previous snowflake worksheets function had a native sharing function, allowing users to start with templates that were run-only. Overnight, users’ worksheets are fragmented and no longer shared.
  3. Errors and settings– A lot of worksheets that ran stopped when a worksheet database and schema were either deselected.

Shifting Dataworkers to Notebooks

The easiest path for data workers is to shift to Notebooks, which provides a clean and minimalist experience, with a linear, guided path through data / analysis. I personally love working in notebooks. The added benefit of source control with GitHub makes it a viable solution to control and share, but requires access control across tools.

As of Nov 2025, similar to Workspaces, there is no Snowflake-managed “sharing” function.

Marketplace: Streamlit App

I searched the marketplace looking for a solution and came up short. As a result, we built our own solution called DataTools Pro Explorer. We went the low-code route and created a point-and-click exploration tool to quickly access and refine data to the right grain and cut, allowing users to save and then modify the SQL as needed. We kept it very simple and released early. The feedback has been amazing, and we continue to improve and refine DataTools Pro Explorer every two weeks.

View and Install DataTools Pro Explorer in Snowflake Marketplace – It’s free! | View Documentation

Moving from Cloud Themed IDE to Real IDE

We trust that Snowflake had plenty of data and interviews to support building a browser IDE UX for technical users vs the classic minimalistic SQL worksheet editor. DBT Cloud has a proven and battle-tested cloud experience. Frankly, we struggled getting it working for multiple clients. Now, we use DBT natively with Snowflake with clients.

Most of the engineers and data scientists we work with already use their preferred IDE to work with Snowflake. The DataTools Pro team officially moved from VS Code to Cursor as our standard IDE setup. That move with built-in AI co-pilot and agents has been a wonderful move.

Moving Data Work out of Snowflake: Modern Data Delivery & BI Tools

There is no shortage of BI tools purposely built for data workers to access, slice, and dice data. The reality is that Excel is the number 1, ubiquitous data tool for data workers. Modern BI platforms built for cloud lean in heavily and provide very powerful spreadsheet abilities. For data wrangling use cases, I am lucky enough to have Datameer at my disposal. lt remains our top data tool for end-to-end data delivery.

Datameer

We use traditional enterprise-grade BI Platforms like Tableau and Power BI.. There is a wide range of modern analytics platforms like Sigma, Hex, and many others that were purposely built for cloud data platforms like Snowflake.

What about AI?

If you got to the end of this article wondering, “what about an AI chatbots”? I do believe there will be a time and place but I am cautiously optimistic.

Snowflake listens and evaluates its users and has already buttoned up some loose ends, navigating between Snowflake Horizon Catalogue and workspaces. I anticipate worksheets continuously improving. If you need help getting higher adoption from Snowflake, we are happy to help! Check out DataTools Pro Explorer in Snowflake Marketplace and let us know what you think… It’s free!

Adventures with Snowflake MCP and Semantic Views

Posted on by
Snowflake MCP and Claude

Last month, I had an opportunity to roll up my sleeves and start building analytics with Snowflake MCP and Snowflake Semantic Views. I wanted to see how far I could push real-world analyst and quality assurance scenarios with Tableau MCP and DataTools Pro MCP integration. The results gave me a glimpse of the future of AI/BI with real, production data. My objective was to deliver a correct, viable analysis that otherwise would have been delivered via Tableau.

The time spent on modeling my data, providing crystal clear semantics, and using data with 0 ambiguity helps. My results delivered great results, but I ended the lab with serious concerns over governance, trust, and quality assurance layers. This article highlights my findings and links to step-by-step tutorials.

Snowflake MCP and Claude

Connecting Claude, Snowflake MCP, and Semantic Views

The first step to connect all of the components was building my Snowflake Semantic views. Snowflake MCP gave me the framework to orchestrate queries and interactions, and using Snowflake Semantic Views gave me the lens to apply meaning. All of my work and experimentation occurred in Claude. This gave me the AI horsepower to analyze and summarize insights. To connect Snowflake to Claude, I used the official Snowflake MCP Server, which is installed on my desktop and configured in Claude.

Together, these tools created a working environment where I could ask questions, validate results, and build confidence in the answers I got back.

Creating Snowflake Semantic Views

With my Snowflake Semantic View setup, I spent some time researching and reading other folks’ experiences on semantic views. I highly recommend having a validated and tested Semantic view before embarking on AI labs. If you don’t know what metadata to enter into your Semantic View, seek additional advice from subject matter experts. AI can fill in blanks, but it shouldn’t be trusted to invent meaning without human oversight: Why AI-Generated Meta-Data in Snowflake Semantic Views Can Be Dangerous

Bottom line… Begin with a simple and concise Snowflake semantic model. Build clearly defined dimensions and measures. Use real-world aliases and refrain from using AI to fill in the blanks, unless your objective. Layer on complexity once you’re comfortable with the results.

What Worked Well

  • Control over data access
    Thankfully, the Snowflake MCP is limited to semantic views and Cortex search. The opportunity and value of Cortex search cannot be understated. I will cover that in another post. The idea of unleashing an AI agent with elevated permissions to write SQL on your entire data warehouse is a governance nightmare. Semantic Views gave me the ability to scope exactly what Claude could see and query.
  • Accuracy of results
    The top questions I get during AI labs: “Is this information correct?” I had a validated Tableau dashboard on my other monitor to validate the correctness of every answer.
  • Simple to complex questioning
    My recommendation with any LLM-powered tool is to start with high-level aggregate questions. Use these to build a shared understanding and confidence. Then, grounded on validated facts, you can drill down into more detailed questions with confidence. This approach kept me in control when the analysis moved beyond existing knowledge and available analysis.

Where I Got Stuck

Three challenges slowed me down:

  1. Metadata gaps – When the semantic layer lacked clarity, Claude produced ambiguous answers. It isn’t garbage in, garbage out problem…. It is me having a level of subject matter expertise that was not captured in my semantic layer or in a feedback loop to make the AI system smarter. LLM analysts feel less magical when you know the answers. That is where adding Tableau MCP allowed a pseudo peer review to occur.
  2. Over-scoping – When I got greedy and exposed too many columns, ambiguity crept in. AI responses became less focused and harder to trust. Narrower scope = better accuracy.
  3. Context Limits– I had Claude do a deep analysis dive. I also had it code a custom funnel dashboard that perfectly rendered a visual funnel with correct data. At some point, Claude explained that my context limit had been reached. My analysis hit a brick wall, and I had to start over. Claude is a general-purpose AI chatbot, but it was still disappointing to hit a stride and have to stop working.

Risks You Should Know

If you’re using AI to build your semantic layer, you need to be aware of the risks:

  • AI-generated semantics can distort meaning. It’s tempting to let an LLM fill in definitions, but without context, you’re embedding bad assumptions directly into your semantic layer: Why AI-Generated Meta-Data in Snowflake Semantic Views Can Be Dangerous
  • Do not give LLMs PII or Sensitive PII. As a rule of thumb, I do not add PII or sensitive PII into semantic models. I hope that at some point we can employ Snowflake aggregation rules or masking rules.
  • Governance blind spots. Connecting the Snowflake MCP requires access from your desktop. For governance, we use a personal access token for that specific Snowflake user’s account. That ensures all requests are auditable. Beyond a single user on a desktop, it’s unclear how to safely scale the MCP.
  • False confidence. Good syntax doesn’t equal good semantics. Always validate the answers against known results before you scale usage.

Final Take

Snowflake MCP and Semantic Views are still very much experimental features. They provide a glimpse of what will be possible when the barrier and access to governed, semantically correct data are removed.

In my case, I employed DataTools Pro for deeper metric glossary semantics and a writeback step via Zapier to capture learnings, re-directions, and insights for auditing purposes. If you would like assistance setting up a lab for testing, feel free to contact us to set up a complimentary session

Streamline Team Collaboration in Salesforce with DataTools Pro

Posted on by
Streamline Salesforce Team Collaboration

Collaboration is key when multiple teams work with complex business applications like Salesforce. Seamless teamwork across technical roles ensures that everyone, from administrators to analysts, are on the same page. This leads to more efficient processes and better outcomes. Yet, achieving smooth collaboration can be challenging when different teams need access to shared data and meta data resources and clear communication channels.

DataTools Pro is designed to help cross organizational challenges head-on. By offering a range of tools tailored for Salesforce, DataTools Pro simplifies cross-team collaboration. Tools like the Metrics Glossary and Interactive ERD make it easy for teams to understand and communicate relationships business and data relationships, promoting transparency and alignment across various departments. This ensures that all team members can access up-to-date metrics and reports relevant to their roles.

The ability to streamline data management, governance, and improve communication can have a substantial impact on your business operations. With DataTools Pro, teams can work together more efficiently, reducing the time spent on data-related tasks and focusing more on strategic decision-making. In this article, we’ll explore how DataTools Pro enhances team collaboration in Salesforce, diving into its key features, best practices, and the overall benefits of its implementation.

How DataTools Pro Enhances Team Collaboration in Salesforce

DataTools Pro significantly improves team collaboration within Salesforce by offering a suite of features designed to make data more accessible and understandable for everyone. One of the main ways it does this is through its Metrics Glossary. This tool ensures that all team members, from Salesforce administrators to data analysts, have access to a shared, up-to-date glossary of metrics. By tracking and updating Salesforce metrics, the Metrics Glossary helps everyone stay aligned on key performance indicators and how they are measured across systems like Salesforce and Tableau.

Another vital feature that enhances collaboration is the Interactive Salesforce ERD (Entity Relationship Diagram). Teams often struggle to understand the both basic conceptual relationships and nuanced complexity between different Salesforce objects. The Interactive ERD visualizes these connections in an easy-to-understand, color-coded format. This makes it simpler for teams to collaborate on data-related projects, as they can easily see how different objects interact and affect one another. DataTools transforms an ERD from a technical data administration tool to a business communication tool.

Moreover, DataTools Pro includes a powerful Data Dictionary for Salesforce. This tool provides quick access to Salesforce objects and fields, aligned with business initiatives. Having a centralized, live documentation asset allows team members to easily find and use the data they need. This minimizes the time spent searching for information and maximizes the time spent on productivity.

Key Features of DataTools Pro for Streamlined Collaboration

1. Metrics Glossary for Salesforce: The Metrics Glossary is essential for keeping track of and updating Salesforce metrics. It ensures that your documentation evolves with your business processes. This tool helps everyone in your organization understand the relationships between metrics, reports, and business topics. You can also easily publish and export your metrics glossary, which aids in maintaining consistent communication across teams.

2. Interactive Salesforce ERD: This feature allows you to auto-generate and organize your Salesforce Entity Relationship Diagrams. By selecting relevant objects from your dictionary, you can create intuitive, color-coded diagrams. These visuals help teams quickly understand the connections between different Salesforce objects, making data management much more straightforward.

3. Salesforce Data Dictionary: The Data Dictionary was created for analysts, admins, and data professionals. It provides quick access to Salesforce objects and fields that align with your business initiatives. Unlike static Excel sheets or outdated published dictionaries, this live documentation asset keeps track of changes in real-time. This helps teams understand the impact of changes on reporting and analytics.

4. Salesforce Data Migration: The Data Migration mapping tool simplifies the process management of mapping Salesforce objects and fields. It replaces spreadsheets, reducing errors and making the process more efficient. By generating usable SQL code, it helps teams iterate between field mapping and ETL (Extract, Transform, Load) for data migrations, regardless of size. This ensures that data transitions smoothly and accurately.

5. Salesforce Analytics Management: This feature is designed to help manage the lifecycle of hundreds or even thousands of Salesforce dashboards and reports. Through advanced categorization and search capabilities, teams can easily find the right information and keep track of dashboard adoption. This ensures that the most relevant and useful data is always at your fingertips, boosting overall efficiency.

Best Practices for Using DataTools Pro to Improve Collaboration

To get the most out of DataTools Pro and enhance team collaboration, it’s important to follow some best practices. Here are a few tips to help you maximize the benefits of this powerful tool:

1. Regularly Update the Metrics Glossary: Keep your metrics glossary current by regularly updating it. This ensures that all team members have access to the latest data and understand the metrics relevant to their work. Regular updates help avoid confusion and maintain consistent communication.

2. Utilize the Interactive ERD: Make full use of the Interactive Salesforce ERD by organizing your entity relationships by business topic, initiative, or application. This visualization helps teams quickly understand how different Salesforce objects are connected, making it easier to collaborate on projects and align strategies.

3. Maintain the Data Dictionary: Keep your Data Dictionary up-to-date to provide quick access to Salesforce objects and fields. This live documentation helps analysts, admins, and other data professionals find the information they need without wasting time. It also ensures that everyone is working with the most current data.

4. Streamline Data Migration: When planning a Salesforce data migration, use the Data Migration mapping tool to ensure accurate mapping of objects and fields. This helps prevent errors and makes the migration process smoother and faster. Generate usable SQL code to streamline the task of mapping data points and iterating between field mapping and ETL.

5. Organize Analytical Dashboards: Use Salesforce Analytics Management to categorize and search for reports and dashboards efficiently. Organize these assets in a way that makes them easy to locate and use. This will help teams keep track of dashboard adoption and ensure that the most relevant data is always accessible.

Benefits of Implementing DataTools Pro for Team Collaboration

Implementing DataTools Pro can bring a range of benefits that enhance team collaboration and overall productivity. Here are some key advantages:

1. Improved Efficiency: By providing tools like the Metrics Glossary and Data Dictionary, DataTools Pro reduces the time team members spend searching for information. This leads to more efficient workflows and allows teams to focus on important tasks.

2. Better Data Accuracy: Tools like the Salesforce Data Migration mapping tool ensure that data is accurately transferred between systems. This reduces the risk of errors and maintains the integrity of your data, which is crucial for making informed business decisions.

3. Enhanced Communication: The Interactive Salesforce ERD and Metrics Glossary promote clear communication among team members. These tools help everyone understand data relationships and metrics, leading to better collaboration and fewer misunderstandings.

4. Effective Data Management: Salesforce Analytics Management helps teams govern the lifecycle of their dashboards and reports. Advanced categorization and search features make it easy to find and utilize the right data, ensuring that teams always have access to the most relevant information.

5. Alignment with Business Goals: DataTools Pro helps teams align their data management practices with business initiatives. This alignment ensures that data efforts support overall business goals, driving better outcomes and adding value to the organization.

Conclusion

DataTools Pro was built for cross team access and documentation of Salesforce assets. By offering a range of powerful tools, it simplifies the way teams collaborate and manage data. From the Metrics Glossary to the Interactive ERD, each feature is designed to improve efficiency, accuracy, and communication. These tools help keep everyone on the same page and ensure that data is used effectively to support business goals.

Implementing best practices when using DataTools Pro can further enhance these benefits. Regular updates to the metrics glossary, organized entity relationships, and streamlined data migrations are just a few ways to get the most out of this tool. As a result, teams can work more efficiently, make better-informed decisions, and drive their business forward.

Ready to streamline your team collaboration in Salesforce? Discover how DataTools Pro can help you achieve greater efficiency and alignment with your business goals. Visit our website today to learn more!

New DataTools Pro fights Salesforce zombie reports

Posted on by
Salesforce zombie reports

Just in time for Halloween, we have new tricks and treats for DataTools Pro. Jam packed with integrations and a brand-new Reporting and Dashboard management tool, you can take control over reports, and clean up Salesforce zombie reports that are clogging up your Salesforce org.

Salesforce zombie reports

Solving for Salesforce Report Deluge

Our latest DataTools Pro release includes a brand new Salesforce Report and Dashboard management tool. We recognize as data and analytics professionals that Salesforce has an incredible self-service reporting and dashboard function. However, managing and maintaining reports over time is a task that challenges the most experienced admins and analysts. Our team approached this problem with the goal of getting hundreds or even thousands of Salesforce reports under control.

Common Problems with Salesforce Zombie Reports

  • Aggregating data from different objects for same metric.
  • Multiple versions of truth.
  • Redundant copies of reports.
  • Outdated metric definitions.
  • Lack of tagging and business context.
  • No visibility on what reports and dashboards are utilized.
  • Over-used filters removing data from analysis.
  • Abandoned reports still accessed and used.
  • Lack of controls resulting in changes to reports used for key metrics.

Governing Salesforce Reports and Dashboards with DataTools Pro

To combat zombie reports, and make it easier to manage day to day Salesforce report and dashboard lifecycle, we have created a new tool that provides:

1. Relating reports and dashboards to business context. Enhanced tagging and search reports by line of business, topic, and status.

2. Manage Report and Dashboard lifecycle to declutter Salesforce. Bulk disposition reports with a status so you can search and filter your report repository.

3. Provide a lens for admins into Report and dashboard utilization. Search and tag reports dashboards based on last viewed – making deprecating reports easy.

4. Help focus from activities to metrics and goals. Connect relationships between reports, metrics and KPIs using DataTools Metrics Glossary.

New DataTools Pro 3rd Party Integrations

In addition to our new Report and Dashboard management, we have been beefing up our native integrations, making it easier to integrate existing metrics glossaries or push your metrics glossary where you and your colleagues already work.

Zapier

The DataTools Pro Zapier integration provides the ability to stream your metrics glossary. Zapier is the ultimate conduit to connect any cloud application containing metrics into DataTools Pro. Soon, we will offer bi-directional connectivity through Zapier so you can utilize DataTools to help centralize and manage metrics with with hundreds of potential integrations to link and distribute metrics across your enterprise. Our new Zap is currently available in beta.

Zapier DataTools Pro

Coda

The DataTools Pro Coda bundle ensures your Salesforce, data, analytics, and business teams have immediate access to your metrics glossary. Coda is the perfect knowledge and AI brain to deliver metrics and relationships.

Need Help Eliminating Salesforce Zombie Reports?

We will continue to add more DataTools Pro integrations into 2025 including other CRMs like Hubspot. We look forward to getting early feedback and hope to collaborate with you to make zombie reports obsolete! If you need help mapping out your metrics and analytics governance plan, we are always here to help! Schedule a free consultation with us anytime

Why we love automating knowledge retention with Zapier and DataTools Pro

Posted on by

At DataTools Pro, we’re always on the lookout for ways to streamline processes and retain knowledge to feed into our AI brain! We are obsessed with hacking cross team knowledge which is why we have chosen to innovate new ways to manage metrics with Zapier and DataTools Pro. Zapier has become an essential tool for automating our own internal workflows and ensuring that our team is always in sync with as little human intervention as possible.

Zapier: Automating Knowledge Flow Across Apps

Zapier is a powerful workflow automation platform that connects over 4,000 apps, allowing us to create seamless data flows without custom coding. For us, this means we can push critical metrics from various sources into DataTools Pro with just a few clicks. Whether it’s Salesforce, Google Sheets, or Tableau, Zapier helps ensure that all of our metrics definitions and changes are automatically centralized in one place: our Metrics Glossary in DataTools Pro.

This process not only saves time but also ensures that our knowledge retention efforts are smooth and consistent across all platforms.

How We Use Zapier internally at DataTools Pro

Lead Intake and Activation Funnel

Internally, we’ve integrated Zapier to manage our intake, activation and onboarding of DataTools Pro users across our website, app, and Salesforce. With Zapier we are running an ultra simple Salesforce org where our business process flow for lead intake exists in Zapier, not Salesforce.

As a result of our approach:

  1. We don’t have dupe lead problems
  2. All web forms and activities are captured and retained
  3. Our marketing automation – emails are aligned and captured
  4. Our entire end to end activation journey across 4 disparate clouds are in sync with clean data
  5. Our Salesforce management and development costs are extremely low.
  6. Returning users, customers, and prospects are routed and logged as activities

Risk we acknowledge

Zapier is a single point of failure to connect prospects and clients to activation. However, Zapier has sophisticated logging, debugging, alerting and replay capabilities, that you need to properly manage your onboarding funnel. There is no concept of “build and pray” that our critical pipelines don’t fail at DataTools Pro.

Metrics Management

We have just started scratching the surface of our brand new Zap for DataTools Pro, allowing our users to connect any app into Zapier. The first iteration of this integration allows Zapier to push metrics directly into our centralized Metrics Glossary. The flexibility of Zapier’s workflows will ultimately allow us to synchronize new metrics across knowledge management platforms. DataTools Pro will handle monitoring, change management and integration across business and analytics teams. Zapier handles distributing that knowledge to the productivity tools that you are already using!

A Simple, Powerful Approach to Knowledge Retention

By connecting our Metrics Glossary to Zapier, we’ve removed a significant pain point: the manual labor of gathering and syncing information across platforms. This automation gives us more time to focus on what matters—delivering value to our customers. With Zapier handling movement of data, our team can stay razor focused on driving education, utility and value to our DataTools Pro users. The next horizon for us is fully automating our metrics, roadmap, prioritization, and knowledge distribution as we ship DataTools Pro features!

New Salesforce ERD DataTools Released

Posted on by
Salesforce ERD

Our DataTools Pro team created a free Salesforce entity relationship diagram tool that generates clean, and clear Salesforce ERD visualizations. Our product philosophy is “release early and often” giving early adopters an opportunity to kick the tires and help shape our newest Salesforce ERD release! In this post, we are excited to share new features to that make designing and referencing ERDs significantly better.

Get Started

Decluttering your Salesforce ERD

If you have lots of objects and field relationships, it can get overwhelming to understand relationships in context of a larger ERD. Our focus mode allows you to select and focus on objects and their relationships, letting everything fade to the back.

Connection Grouping – When multiple relationships exist between 2 objects, we have enhanced our grouping mode to group and remove redundant lines in your ERD.

Salesforce ERD

Object Layout Locking

Add objects from your Salesforce org and arrange them in the ERD without leaving the page. As you drag and arrange your ERD, it now saves position and layout so you can ensure your views are locked in place.

Entity Relationship Diagram

Embedded Field Dictionary

Manage and select your Salesforce objects which can be refreshed anytime. In our latest ERD, you can add and remove objects from your dictionary without leave the page.

Create ERD Views: With a dictionary of objects from Salesforce, you can create multiple views to highlight data object relationships. This focus allows for a focused and uncluttered perspective how your data model and relationships align to your desired outcomes.

Embedded Salesforce ERD

Embedded Field Dictionary

We have merged our data dictionary into the the ERD, eliminating context switching between screens. Our dictionary allows basic access to field name and a tooltip to quickly reference other attributes that may be reference for relevance. Additionally, you can filter and export your dictionary without leaving the page.

Salesforce Data Dictionary

Your input can shape what’s next for DataTools Pro Salesforce ERD

With a solid foundation, we have a massive list of enhancements expand the utility of a connected Salesforce ERD. We are working with a wide range of experts and backgrounds from AI application developers to Salesforce admins who manage massive, multi-org enterprises.

What is Metrics Governance and why you need it

Posted on by
Metrics Governance

Ensuring accuracy, consistency, and reliability in business metrics

Metrics governance refers to the systematic approach to managing and maintaining the accuracy, consistency, and reliability of metrics used within an organization. It is crucial for achieving data-influenced decisions by ensuring that the metrics used in reports and dashboards accurately. Without metrics governance, organizations often encounter inconsistent reports, leading to confusion and mistrust in the data. This article explores how the “single source of truth” problem is best addressed by governance process.

Metrics Governance Throne

Why Metrics Governance is difficult?

Metrics governance is difficult mostly because it is a cross organizational problem relying expertise, understanding, and distribution of knowledge regularly across teams. Getting data governance right is tough enough! Modeling data and applying business rules to understand results and outcomes adds another layer of complexity. Typically this complexity is inherited by professionals responsible for creating business intelligence and operational reports. Your metrics and KPIs that drive your organization are extremely important. The reality for many growing enterprises is metrics definitions live scattered across teams, documents, and technology applications. Every business has to make the right decision where to implement a glossary of metrics but there is no shortage of great technology solutions to put those definitions into motion:

  • BI and Analytics tools like Tableau Pulse let analysts build a library of metrics
  • Data development platforms like DBT provide a semantic layer to code and manage definitions, including metrics
  • Google Analytics has built-in metrics and standardized definitions into the core application

These 3 examples are typically managed by different teams highlighting where gaps can occur thus providing the inspiration for the graphic for this post. We believe in a federated approach to analytics is effective but a centralized repository of metrics definitions is needed not only to improve analytics, but to improve employee onboarding and AI co-pilot training.

Metrics Governance vs. Data Governance

While metrics governance and data governance are closely related, they have distinct focuses:

  • Data Governance: This involves the overall management of data availability, usability, integrity, and security within an organization. It encompasses data quality, ownership, stewardship, and compliance with data privacy regulations.
  • Metrics Governance: Specifically focuses on the metrics that are definitions intended to measure business outcomes using data. It deals with the definition, standardization, monitoring, and validation of metrics to ensure they are accurate and consistent.

Metrics governance complements data governance by ensuring that the metrics used to make business decisions are based on high-quality data and are consistently applied across the organization. The key difference lies in the scope—data governance is broader, covering all aspects of data management, while metrics governance zeroes in on the metrics themselves.

Steps to Implement Effective Metrics Governance

To implement effective metrics governance, organizations you should consider these typical areas of improvement:

Metrics Governance Flow
  1. Promote a Culture of Accountability and Data-Driven Decision-Making: All metrics should have business owners. Accountability and ownership of metrics and how to use them helps every team involved. This fosters a culture of accountability and ensures that decisions are based on reliable data.
  2. Establish Clear Definitions and Standards: Define metrics clearly and ensure that these definitions are understood across the organization. This prevents confusion and ensures consistency in reporting.
  3. Create a Centralized Metrics Glossary: Maintain a centralized repository of metrics to ensure consistency and easy access. This helps in tracking and managing metrics effectively. Here is a free template on: Notion Metrics Glossary Template
  4. Implement Data Quality Management Practices to your metrics: Ensure that the data used to calculate metrics is of high quality. This includes data validation, cleansing, and regular audits.
  5. Regularly Monitor and Validate Metrics: Continuously monitor metrics to ensure they remain accurate and relevant. Regular validation helps in identifying and addressing any discrepancies.
  6. Metrics Governance management as part of your data strategy – Understand where and how metrics are managed and deployed. Learn more about analytics strategy playbook

We would love to hear how you manage and standardize your metrics and KPIs. Our team at DataTools Pro is working on solutions to help automate the traditional metrics fact gathering and metrics glossary preparation steps!