#Sales Cloud162 personnes en discutent

Maiko様 

商談（Opportunity）に紐づく活動（Task/Event）の件数をレポートで抽出する方法は以下の通りです。 

1. レポート作成画面で「新規レポート」をクリックし、レポートタイプの検索窓に「活動」と入力します。 

   標準レポートタイプの中に「商談との活動（Activities with Opportunities）」というタイプがあるので、それを選択します。 

   公式リファレンス:

2. レポート形式は「サマリー」を選択します。 

3. グループ化の設定で「商談名」を選択し、商談ごとに活動をグループ化します。 

4. レコード数（件数）を表示するには、レポートビルダーの列一覧から任意の項目（例：件名）を選び、集計欄で「レコード数」にチェックを入れます。 

   これにより商談ごとの活動件数がサマリー行に自動集計されます。 

5. 件数が多すぎてエラーになる場合、Salesforceの公式サイトでも案内がある通り、日付やステータスなどのフィルタを追加するか、レポートタイプを「商談との活動」に絞ることで解決できます。 

   公式リファレンス:

補足: 

- 「共有活動（Shared Activities）」が有効な組織では、複数のコンタクトに紐づく活動の集計結果が管理者権限の有無によって異なる場合があります（管理者は主要連絡先分＋招待者ごとに別カウント、非管理者は主要連絡先分のみ1件としてカウント）。件数の見え方に差異がある場合はこの仕様が原因の可能性があります。 

- アーカイブ済みの活動（Activity History）はレポートに含まれない点にもご注意ください。 

これで商談ごとの活動件数が一覧化できるはずです。

Hi @Rohit .

I would use a Record-Triggered Flow with a Scheduled Path on the Contract.

•  Set the Time Source = Contract End Date and Offset = 30 Days Before. 
•  At the scheduled time, check whether a Renewal Opportunity already exists. 
•  If not, use Create Records to create the Renewal Opportunity and notify the Account Owner. 
•  To prevent duplicates, use a Renewal Opportunity lookup or Renewal Created checkbox on the Contract. 

Flow: 

 Contract → Scheduled Path (30 Days Before End Date) → Duplicate Check → Create Renewal Opportunity → Notify Owner 

This is cleaner than calculating the 30-day window manually. Salesforce supports Scheduled Paths based on a date field with a positive or negative offset. 

Hope This Helps!!

Hi @Rohit .

Since the App Launcher is working but Sales/Service apps are not appearing, I would check the app assignment and visibility settings rather than cloning the profile again. 

1. Check the Profile's Assigned Apps

Go to: 

 Setup → Profiles → [User's Profile] → Assigned Apps

Make sure Sales and Service are assigned/visible for that profile. Salesforce users only see apps they're authorized to access through their profile or permission sets.  

2. Check App Manager

Go to: 

 Setup → App Manager

Find the Sales and Service Lightning Apps and verify that they are enabled/visible and that the required profile is included in the app's user-profile assignment.  

3. Check App Menu

Go to: 

 Setup → App Menu

Find the Sales and Service apps and make sure they say:

Visible in App Launcher

and not:

Hidden in App Launcher.  

4. Check the cloned profile

Since you mentioned that you cloned the profile, compare the cloned profile with the original profile and verify its Assigned Apps and relevant object/tab permissions.

Also remember that app visibility and object/tab access are two different things. A user may be able to see an app but still not see particular tabs such as Accounts, Contacts, Opportunities, or Cases if their object or tab permissions don't allow access. 

So troubleshoot in this order:

Profile/Permission Set → Assigned Apps → App Manager → App Menu → Object & Tab Permissions 

Hope This Helps!!

Yes, It is possible to update the Campaign Members Status of a specific Campaign and Contact in SFDC from the Outreach Sequence.

You can use the Salesforce Update Object step to update a Campaign Member's status to whatever you want. To do this,

•  you will need to first create a Salesforce connection in Outreach,
•  then create a Salesforce Update Object step in your Sequence.
•  Select Campaign Member from the Object dropdown.
•  then set the appropriate filter conditions to identify the Campaign Member you want to update.

 Finally, select the Status field and set the value to the status you want to update. 

Hi @Swati Malkar

This is a known pain point in Spiff/ICM the tool is calculating off a live field (

Root cause: Spiff's plan logic is likely referencing Opportunity.CloseDate (or a similarly live-synced field) to bucket the deal into a payout period. When that field changes after calculation/payout, any report or re-run that re-evaluates the deal picks up the new value, creating a mismatch between "period paid" and "period the deal now says it belongs to." 

How to actually fix it a few layered options, roughly in order of how I'd sequence them: 

1. Snapshot the period at calculation time, don't derive it live. Add a dedicated field something like Commission_Period__c on the commission/statement record (or in Spiff's own statement object) that's set once when the statement runs and never recalculated from CloseDate again. Spiff does support adding effective dates on plans/logic and locking historical statements, so this should be a config change in Spiff's plan design rather than custom Apex — check that "lock historical statements" setting is actually turned on for closed periods.
2. Separate "Close Date" (sales-facing, editable) from "Commission Effective Date" (finance-facing, locked once a statement is generated). Reps and deal desk need to edit Close Date for pipeline/forecast reasons that's normal. The commission engine should never read that same field for historical periods once paid.
3. Treat post-payout edits as a reconciliation event, not a silent recalculation. If a close date changes after a statement already paid against it, that should trigger a clawback/adjustment workflow (a new adjustment line in the next period), not a retroactive rewrite of March's numbers. This is standard ASC 606-adjacent practice Spiff's audit-ready expense reporting is built around exactly this kind of compliant, locked-period model.
4. On the Salesforce side, if Opportunity edits are what's causing this, consider a validation rule or Flow that blocks/flags Close Date changes on Opportunities that already have a Commission_Statement__c (or equivalent) linked and Closed/Locked at minimum, notify Finance/RevOps rather than letting it happen silently.

I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.