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

Hi Gagan,

For bulk Content management, there are two separate pieces here.

1. Publishing to specific libraries: Content records have library/membership relationships, so this can be automated rather than manually moving each file. Depending on the Salesforce release, you may need Apex or the appropriate Content API/tooling to create the library memberships in bulk.
2. Linking Content to Products: If you need each Content item related to a Product, you can maintain a mapping such as Content ID → Product ID and use Apex/API automation to create the required relationships. This is generally more reliable than trying to do it manually through the UI.

If you have a large number of files, I'd recommend testing the process with a small batch first, especially if the same Content item needs to belong to multiple libraries or Products. 

Hi Stacy,

Yes, this is possible. You can have the WordPress form handle the registration/access to the protected content and then send the submitted form data to Salesforce. 

The integration could create or update a Lead or Contact in Salesforce after the form is submitted. Depending on your WordPress setup, this can be done through a Salesforce integration/plugin or by using the Salesforce API from the form submission. 

For the protected documents, I would keep the access-control logic on the WordPress side and use Salesforce primarily for storing the submitted lead/contact information.

If you can share which Gravity Forms version and Salesforce edition you're using, I can suggest the specific integration approach. 

Hi Paul,

Because you need to make those files searchable via SOSL, leveraging Salesforce Files (ContentDocument and ContentVersion) is definitely the right approach compared to legacy attachments. However, bulk-loading files directly into the ContactFeed (or via FeedItem / FeedAttachment) through a standard batch process requires linking the Content Document to the record feed correctly. 

Here is how you can set up a bulk upload and feed attachment process:

1.Bulk Load Files via ContentVersion:Content Version Upload. 

Use Data Loader or the Bulk API to insert your documents into the ContentVersion object. This creates the underlying file records in Salesforce and makes their searchable text bodies fully indexable for SOSL queries. 

Querying ContentVersion via SOQL confirms your files have successfully uploaded with valid Title and VersionData fields. 

2.Create FeedItem and ContentDocumentLink Records:Feed Attachment Linking. 

To attach those files to the specific Contact's Chatter feed, you need to create a ContentDocumentLink record mapping the ContentDocumentId to the ContactId with ShareType = 'V' (Viewer) and Visibility = 'AllUsers'. Then, insert a corresponding FeedItem record with Type = 'ContentPost' referencing the file to display it directly in the contact's feed. 

Hey Melinda!

Yes, this is a common issue with large email threads or meetings involving multiple people. When you forward a thread with many recipients in the CC field, Email-to-Salesforce can create multiple tasks or add activities to unrelated records.

By design, Email-to-Salesforce checks the To, CC, and BCC fields to identify matching Salesforce records. Unfortunately, there isn’t a native setting to disable recipient matching while still keeping Email-to-Salesforce enabled. 

Here are a couple of ways you can work around it:

1. Clean up the email recipients before forwarding 

Before forwarding the email to your Email-to-Salesforce address, remove the unnecessary addresses from the To, CC, and BCC fields. Keep only the primary contact or record you want associated with the activity. This helps prevent unnecessary tasks or unresolved items from being created. 

2. Use Salesforce's native email integration 

For meeting recaps or large email threads, you can use the Gmail or Outlook integration to log the email directly to the specific Account, Contact, or Opportunity. This gives you more control over where the activity is recorded instead of relying on automatic recipient matching. 

If the issue continues, sharing the exact Email-to-Salesforce setup and an example of the unwanted tasks would help narrow down the best approach.

Hey Orian!

You hit the nail on the head regarding keeping your sales reps inside Salesforce—forcing them into the DocuSign Console just to tag an envelope is a huge adoption killer.

Even though DocuSign’s native component doesn't automatically surface custom envelope fields onto standard Salesforce page layouts out of the box, you can bridge this gap by passing your Salesforce picklist values directly into DocuSign using Custom Button URL parameters. 

Here is how you can set that up so your reps never have to leave Salesforce:

1.Create a Document Type Field:Salesforce Field Setup. 

Create a custom picklist field (e.g., Document_Type__c) on your parent object (like Opportunity, Contract, or Agreement) with values like "Insertion Order (I/O)", "NDA", and "T&Cs". You can verify success when reps can select the document type right from the Salesforce page layout before clicking send. 

2.Map Salesforce Fields to DocuSign Custom Fields:Custom Button URL Parameters. 

Customize your DocuSign Send button URL to dynamically pass the selected picklist value into DocuSign’s custom envelope field (such as your "IO Test Field" shown in the screenshot). By appending custom field parameters (like &CF1Name=IO%20Test%20Field&CF1Value={!Opportunity.Document_Type__c}) to your button's JavaScript or URL syntax, DocuSign will capture the selection automatically. You can verify success when sending an envelope populates the custom field in DocuSign without manual entry.

Hi Kathrin,

You're definitely not the first person to want this for a paperless setup! Standard Salesforce validation rules can't check whether an attachment is present before saving a record, but here are the three best ways to achieve this:

1. Use a Visualforce Page or Flow (No-Code/Low-Code) Replace the standard record edit page with a Visualforce page or a screen Flow. When the user populates the "Invoice Received Date", you can dynamically render a file upload input on the next screen and make it a required field before allowing the final submit/save.

2. Apex Trigger (For Strict Validation) If you want to enforce this at the database level regardless of where the record is edited:

• Write a before update trigger on the object that checks if Invoice_Received_Date__c is changed or populated.
• Query the Attachment (or ContentDocumentLink) child records for that object.
• If no attachment matches your required naming criteria, use addError() to prevent the save and display your custom error message (e.g., "You must attach the invoice document before saving this date.").

3. AppExchange Route Search the AppExchange for "Required Attachments" or "File Upload Validation" apps. There are several pre-built managed packages designed specifically to enforce mandatory file attachments based on field criteria or stage gates.

Hope this gives you a good direction for your paperless office initiative!

Hi Amy,

If you’re referring to the standard Ideas

functionality, the comments are displayed in chronological order, with the newest comments appearing at the bottom. There isn’t a standard setting to reverse the order so the most recent comment appears first. 

If having the newest comment at the top is important, it would require a custom solution, such as a custom Visualforce page/component that queries and displays the Idea comments in descending date order.

Hi Gia,

The difference is likely related to the Email Template Builder features available in your Salesforce edition/org configuration, rather than the template itself. 

The Editing Modes, including Block Edit and Live Edit, are part of the enhanced template editing experience and may not be available in every Salesforce version or configuration. The tutorial may also have been recorded in a different Salesforce release. 

I’d first check which Salesforce release/edition you’re using and whether the Email Template Builder features are enabled for your org and user profile. 

If you can share a screenshot of your template editor and the Salesforce edition/release, it would be easier to identify what’s missing.

That being said, there are other alternatives that you could use to accomplish your goal (which I'm not 100% sure I understand, but feel free to clarify).

• In App Guidance: All those pop ups that happen when you log into Salesforce that you see FROM Salesforce, could just as easily be Your Help Video to your Users
• Start here in the documentation: https://help.salesforce.com/articleView?id=sf.customhelp_lex.htm&type=5
  • There are lots of other documents that will guide you through the "technical stuff"
  • Read them through, so you apply the tool correctly.
• Take this trail for a quick overview of the tool and how it works:  https://trailhead.salesforce.com/en/content/learn/modules/user-engagement

If all you want is a video, you could use the Rich Text Component to simply put up a link to the videos.