#Collaboration12 discussing

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.

In the Winter '27 release, this new feature can solve what you're looking for: 

Process Multiple Records with Screen Flows from List Views and Related Lists -

https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_screen_mass_quick_action_264.htm&release=264&type=5

I just completed a new screen flow for one of our long-term requests here and it came out beautiful!

pdf-lib is what most people use for this. Upload it as a static resource, load it in an LWC with loadScript, pull the files' base64 VersionData from Apex, merge in the browser, then save the result back as a new ContentVersion.

Main reason to do it client-side rather than Apex: you skip the 6MB/12MB heap limit, so large files still work.

const merged = await PDFLib.PDFDocument.create();for (const b64 of base64Files) {  const doc = await PDFLib.PDFDocument.load(b64);  const pages = await merged.copyPages(doc, doc.getPageIndices());  pages.forEach(p => merged.addPage(p));}const out = await merged.saveAsBase64();

If the library misbehaves under Lightning Web Security, the usual workaround is running pdf-lib in a Visualforce page inside an iframe and passing data with postMessage.

If you'd rather not host the library, Api2Pdf and Adobe PDF Services both do merge via callout — but the files leave your org, which rules them out for most healthcare/finance work.