#Sales And Marketing20 debatiendo

Hello @Marion Timmermans

go to setup > Object Manager > Account > Fields & Relationships, and then create the needed custom field, if there is no standard equivalent. 

Think of leveraging a recordtype (available in the same object manager menu in the left pane) if you have some different assignments / layout or display / sales process / set of values for your fields, or so. Otherwise it would just be an attribute on the same object. 

Eric

Hi,

If you're referring to the standard Salesforce Mail Merge option “Log an Activity,” that checkbox is part of the standard Mail Merge functionality and isn't normally configurable through the page layout or user settings.

If you need the activity logging to be optional or disabled by default, you'd generally need to use a different mail-merge process/custom solution rather than changing the standard checkbox behavior.

If you can share which Salesforce Mail Merge screen/version you're using, someone may be able to confirm whether that release provides any configuration for it. 

Hi Geoff,

Removing/deactivating a user's SaaSPoint TimeTrack license should not by itself delete the historical records that user created. The timesheet entries are Salesforce records and normally remain in the org. 

The main thing to check is whether the TimeTrack package has any specific behavior tied to an active license or user status. Before removing the license, I'd recommend confirming with the package documentation/vendor and, if possible, testing it in a sandbox. 

If you share the exact TimeTrack package/version, someone may be able to confirm the behavior more precisely. 

Hi Ker Vin,

You can transfer the activity history, but you generally shouldn't update the existing Task records by simply replacing the Lead ID with the Opportunity ID. 

For a one-time cleanup, you can export the Lead's Tasks, identify the corresponding Opportunity ID, and then create new Task records related to the Opportunity. Keep the original Lead activities intact if you still need the historical record. 

For an ongoing process, Apex/automation can copy the Lead's relevant activities to the Opportunity when the Opportunity is created. 

If you're doing this through Data Loader, the Opportunity ID can be obtained by exporting the Opportunities first (including Id and any field you can use to match the Lead), then using that mapping when creating the Tasks. 

Hi Charu,

The important distinction here is that Record Types do not control record visibility. Assigning a Record Type to only certain profiles determines which record types those users can create/use, but it does not prevent other users from viewing existing Account records of that Record Type.

To restrict visibility, check the Account sharing model:

• Set the Account OWD to Private if appropriate.
• Review the Role Hierarchy, since users higher in the hierarchy may inherit access to records.
• Check all Account Sharing Rules, including the rule you created.
• Also check manual sharing, Account Teams, and any other mechanisms that may be granting access.

Your sharing rule is explicitly granting access to members of the BMG Product Management group, but the other users may be getting access through another sharing mechanism.

If the requirement is specifically "users outside these groups must never see Accounts with this Record Type", you'll need to design the Account sharing model around ownership/sharing rather than relying on the Record Type. 

Hi Marcia,

This may be related to how Salesforce's Mail Merge process generates the Word document. The protection settings in the original Word template are not necessarily preserved when Salesforce creates the merged document. 

Could you provide the Salesforce edition/version and the type of Word form fields/protection you're using (for example, legacy form fields vs. content controls)? That would help determine whether there is a supported configuration to preserve the protection. 

If the protection is consistently being removed by the Mail Merge process despite the template being configured correctly, it may be worth opening a Salesforce Support case to confirm whether this is a known limitation of the Mail Merge functionality. 

 Hi Rakesh,

Product Quantity Scheduling is useful when a product's total quantity needs to be delivered or sold over multiple dates instead of all at once.

For example, suppose an Opportunity includes 1,200 units of a product, but the customer wants delivery in monthly batches:

• January: 100 units
• February: 200 units
• March: 300 units
• April: 300 units
• May: 300 units

Instead of creating separate Opportunity Products for every delivery, you can use quantity scheduling to split the total quantity across different dates.

This can be useful for:

• Recurring or scheduled deliveries
• Long-term contracts
• Customers with phased requirements
• Forecasting expected quantities by date

The main benefit is better visibility into when the product quantity is expected, rather than showing the entire quantity against a single date. 

Hi Rakesh,

Revenue Scheduling is useful when the revenue from a product should be recognized over a period of time rather than all at once when the opportunity is closed.

For example, suppose a customer purchases a 12-month service for $12,000. Instead of recognizing the entire $12,000 in the month the deal closes, you could schedule $1,000 of revenue per month for the 12-month period.

This can be useful for:

• Subscriptions or recurring services
• Maintenance/support contracts
• Long-term service agreements
• Products where revenue needs to be recognized over multiple periods

The main benefit is that Salesforce can provide a time-based view of expected revenue rather than treating the entire product amount as revenue in a single period.

The exact accounting treatment should still follow your organization's accounting rules and processes. 

Hi Nathan,

The issue is that the Campaign Member is a junction record between the Campaign and the Lead/Contact, so a workflow on the Campaign Member doesn't provide the same direct activity relationship to the Contact. 

If you need an activity created whenever the Campaign Member status changes to Responded, you can handle this with Apex/trigger logic. When the Campaign Member is updated, check for the status change and create a Task with the appropriate WhoId set to the related Contact (or Lead).

For example:

Campaign Member status → Responded 

→ Create Task 

→ Subject: Client responded to campaign 

→ WhoId: related Contact/Lead

If you have a large number of Campaign Members, make sure the solution is bulkified. 

 Hi Rakesh,

You can handle this by making the Quote approval status the condition for allowing the PDF to be emailed.

One approach is:

1. Create an Approval Process for the Quote.
2. Keep the Quote in a status such as Pending Approval until it is approved.
3. Provide the email/PDF action only when the Quote status is Approved.
4. If you need to enforce this regardless of how the email is initiated, add server-side validation/Apex so an unapproved Quote cannot be sent.

A custom button or Visualforce page can also check the Quote's approval status before allowing the user to generate and email the PDF.

If you're using the standard Quote PDF/email functionality, let us know your Salesforce edition and whether you're using standard or custom Quotes, and we can suggest the specific implementation.