> For the complete documentation index, see [llms.txt](https://docs.selectstar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selectstar.com/changelog/sep-8-2024-salesforce-crm-analytics-bigquery-sync-mcp-updates-and-more.md).

# Sep 8, 2025 – Salesforce CRM Analytics, BigQuery Sync, MCP Updates, and more

August’s update is all about making your catalog smarter and more connected. We’ve added Salesforce CRM Analytics integration, launched BigQuery description sync, improved both MCP and Chrome Extension Ask AI. These updates make it easier than ever to keep your documentation fresh, discover data faster, and power smoother AI workflows.

## ✨ What's New

### 📊 **Salesforce CRM Analytics Integration**

Salesforce CRM Analytics (CRMA) is now integrated into Select Star. With this release, you can bring your CRMA dashboards and lenses directly into your catalog. This makes it easier to understand how Salesforce analytics content connects to your warehouse models, track ownership, and apply governance.

* Ingest dashboards, lenses, datasets, and recipes from your CRM Analytics environment.
* See lineage from CRM Analytics content back to Salesforce objects and downstream warehouse models.
* Assign ownership, apply governance, and discover unused or stale CRMA assets.

Learn more in our [Salesforce CRM Analytics docs](https://docs.selectstar.com/integrations/salesforce-crma).

### 📝 **BigQuery Description Sync**

You can now sync descriptions back from Select Star back to BigQuery.

* Any updates or approved propagated descriptions in Select Star can be written directly into BigQuery tables and columns.
* Keeps your data warehouse documentation in sync with the improvements your team makes in Select Star.
* Ensures BI users and analysts always see the latest context, no matter where they look.

<figure><img src="https://3470314135-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MgAiVthA_yg9UXKuhyY%2Fuploads%2Fgit-blob-8af5bfe8f925a2a3409c85b81798cf214f9f6eac%2Fimage%20(177).png?alt=media" alt=""><figcaption></figcaption></figure>

Learn more in our [BigQuery description sync docs](https://docs.selectstar.com/integrations/bigquery/bigquery-description-sync).

## **➕** Improvements

### 🛠️ **MCP Updates**

We’ve made several improvements to the MCP server:

* **Owners info**: Better visibility into who owns what.
* **UX & Docs**: Cleaner tool descriptions and updated documentation for easier onboarding.
* **Queries tool**: Enhanced functionality for smoother querying and analysis.

### 🧩 Chrome Extension Ask AI update

We’ve improved the experience when using **“Explore this table with AI”** on chrome extension pages. Now, Ask AI makes it easier to understand the asset you’re exploring, giving you clearer insights and a smoother interaction when asking questions about your data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.selectstar.com/changelog/sep-8-2024-salesforce-crm-analytics-bigquery-sync-mcp-updates-and-more.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
