#Sales Cloud187 人がディスカッション中

Hi Angela,

Reporting on Salesforce Surveys can definitely be a bit confusing because the survey data is spread across multiple objects (such as Survey Invitations, Survey Responses, Survey Question Responses, and Survey Question Scores).

If you're using a custom report type with Survey Question Scores as the primary object, try adding fields like Survey Name, Question, Response, Score, Respondent, and Submission Date, then group by Survey and Question to make the report more meaningful.

These resources are a good starting point:

• Salesforce Help: Reports for Salesforce Surveys
• Salesforce Help: Survey Data Model
• Salesforce Trailhead module: Get Started with Salesforce Surveys
• YouTube search: "Salesforce Survey Reporting" or "Salesforce Surveys Reports and Dashboards" (there are several walkthroughs that explain how to build useful reports).

If you can share what you're trying to measure (e.g., CSAT, NPS, average score by question, response rate, etc.), the community can suggest the most appropriate report type or dashboard approach.

Great question, the proposal send/edit/sign loop is one of the more frustrating gaps in native Salesforce.

On Sdocs specifically: it's solid for generating documents from templates, but collaborative editing back-and-forth with clients tends to require workarounds (shared links, exporting to Word, etc.).

For a more end-to-end flow, a few teams I've worked with use 360 Smart Docs,

 it generates proposals directly from Salesforce data (quotes, opportunities, custom objects) as Word or PDF, has built-in eSign so clients can sign without any external tool, and docs auto-attach back to the record. The Word template builder also means your team can update proposal templates without developer help. 

AppExchange listing: https://appexchange.salesforce.com/appxListingDetail?listingId=994f0c85-2adb-4c30-9e67-40f391c1fc2a

That said, if your proposal workflow is fairly simple, Sdocs + DocuSign is a reliable combo too really depends on how much you want to keep inside Salesforce vs. stitching tools together.

Hi @Philippe Jublot

CPI - Consumer Pricing Index is by default available only in revenue cloud where price will automatically modify after a specific time. You need to build a custom feature for this. 

Something like - 

1. You will have a field which stores the value of number of days 

2. A field to store multiplier (If its specific to product, you can have it in product level or some metadata) 

3. A scheduled flow which runs daily which checks whether the purchased date+60 = TODAY or not 

4. If yes apply the logic

Hi @Thanikonda Koushik

- Check below steps 

• DKIM Key Activation: Sandbox refreshes copy production DKIM keys in an Inactive state. Go to Setup > DKIM Keys and activate or recreate them for this sandbox.
• Domain Verification: Go to Setup > Authorized Email Domains and ensure your sending domain is verified via TXT record.
• Fallback Bypass: Go to Setup > Deliverability and check "Use a substitute email address for unverified domains" for an immediate workaround.
• Email Relay TLS: Your logs show Sent via TLS: False. Go to Setup > Email Relays and change the TLS setting to Required, matching your Office 365 Exchange connector rules.

Hi @Anik Mallick, A good approach is to investigate the user from multiple angles before deactivating it. Below are some places to check, 

1. Login History
   • Check Setup → Login History to see if the user is actively logging in and from where.
2. Last Modified By / Created By
   • Run reports or SOQL queries to see if records are being created or updated by that user.
3. Scheduled Jobs
   • Review Scheduled Apex, Batch Jobs, and Scheduled Flows to see if they run under that user's context.
4. Workflow Email Alerts / Flow Notifications
   • Check whether the user is configured as the sender, default workflow user, or email recipient in automations.
5. Connected Apps & Integrations
   • Review Connected Apps, Integration Users, Named Credentials, and API usage to determine whether external systems authenticate using that account.
6. API Usage
   • Check Event Monitoring (if available) or Login History for API logins. Frequent API access is often a sign of an integration account.
7. Dashboards and Reports
   • Verify whether the user is the running user for dashboards or scheduled report subscriptions.
8. Default Workflow User
   • In Process Automation Settings, check whether the user is configured as the Default Workflow User.
9. Email Services & Automated Processes
   • Review Email Services, integrations, and custom Apex that may reference the user explicitly.

Before deactivating, I usually freeze the user first and monitor for failures or stakeholder complaints. This provides a safer way to confirm whether the account is still being used without immediately breaking automations or integrations. 

Hope it heps you!