#Sales And Marketing22 discussing

Hi Ulas, 

Yes, you’re mostly going right. The main difference is who initiates the process.

Lead distribution starts with your internal sales/marketing team. They create or capture the lead in Salesforce and assign it to a partner. The partner then qualifies the lead and, if it meets your criteria, converts it into an account, contact, and opportunity. 

Deal registration starts with the partner. The partner submits a potential deal through the portal, and your sales team reviews and approves it before moving it into the appropriate account, contact, and opportunity records. 

The exact Salesforce objects and approval flow can vary depending on how you design the partner process. Tools such as Salesforce Flow, Experience Cloud, or LeadAngel can help automate parts of the routing and assignment when the partner network gets more complex. 

So, in simple terms: your team distributes a lead; the partner registers a deal. 

You can! All you have to do is this - 

1. Login to Dataloader.IO [ http://dataloader.io ] with your Salesforce Credentials.
2. Click New Task to select Export
3. Select the Object as: Email Template
4. Select the Fields: Id(this is required), Name, Subject and all the other fields that will help you identify the ones that needs to be deleted.
5. Click Save and Run
6. Now, you should see an CSV file that will have all the Email Templates.
7. Open it in a Spreadsheet Application of your choice.
8. Retain all those rows which has to be DELETED.
9. Now, login to the same Dataloader.IO
10. This time select New Task to opt for Delete operation.
11. Upload the CSV(the one that you formatted in step 8)
12. Click Save and Run

That should do it!

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.