#salesforce-admins — Public Fediverse posts

The Ultimate Guide to the Salesforce Screen Flow File Preview Component

The Spring ’24 Release introduced the File Preview Screen Flow Component. This native tool allows Admins to embed document viewing directly into the flow of work. In this post, we’ll explore the technical requirements, real-world observations, and the strategic implications of this functionality.

Beyond the “Files” Tab: Why This Matters

Historically, viewing a file in Salesforce required navigating to the “Files” related list, clicking the file, and waiting for the standard previewer to launch in a separate overlay. If you were in the middle of a Screen Flow, perhaps a guided survey or a lead conversion process, leaving that flow to check a document meant breaking your concentration.

Salesforce introduced a file thumbnail preview that shows visually what is in the file without having to click into it. Please note that the thumbnails show beautifully in the Single Related List component for lightning record pages. In the multiple related list view, I did not see the thumbnails.

In addition to the lightning record page and related list functionality, Salesforce introduced a file preview component that allows the user to see the preview of the file they have just uploaded, or they find attached to an object record in Salesforce.

Technical Blueprint: Configuring the Component

Setting up this component requires a shift in how Admins think about file data. Files data model is unique. To make the component work, you need to navigate the relationship between ContentDocumentLink, ContentDocument, and ContentVersion.

Core Attribute Requirements

 When you drag the File Preview component onto a screen in Flow Builder, you must configure the following:

• Content Document ID (Required): This is the most critical field. The component needs the unique 18-character ID of the ContentDocument record. It will not accept the ContentVersion ID (which represents a specific iteration) or the Attachment ID (the legacy file format). Please note: the preview component always shows the latest version of the file.

• Label: This attribute allows you to provide instructions above the preview window. This is highly effective for compliance-heavy roles, where the label can say: “Verify that the signature on this ID matches the physical application.”

• API Name: The unique identifier for the element within your flow logic, following standard alphanumeric naming conventions.

Using Conditional Visibility

Because the preview window takes up significant screen real estate, it should not be set to “Always Display”, if it will be driven by a data table reactively. Salesforce allows you to specify logic that determines when the component appears. You can set it to display only if a specific file type is selected in the collection and hide the component if the ContentDocumentID variable is null to avoid showing an empty box.

Lessons from the Field: Our “Around the Block” Test

In our recent hands-on testing, we put the component through its paces to see where it shines and where its boundaries lie.

[youtube https://www.youtube.com/watch?v=_k3F2eX4rdM?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent&w=1220&h=687]

The File Extension

The previewer is highly dependent on the browser’s ability to interpret file headers and extensions. During our test, we uploaded a standard log file. While the content was technically plain text, the file had a .log extension. The component struggled to render this because it didn’t recognize it as a standard format. However, once we switched to a .txt extension, the preview was crisp and readable. The admin takeaway here is that if your business process involves non-standard file types, you may need to implement a naming convention to ensure files are saved in formats the previewer can handle: primarily .pdf, .jpg, .png, and .txt.

Real-World Use Case

How can you use this component in a live production environment? Here is a scenario where the File Preview component adds immediate value:

Imagine a customer service representative handling a shipping insurance claim. The customer has uploaded a photo of a broken item. Instead of the agent navigating to the “Files” tab, the Screen Flow surfaces the photo on the “Review Claim” screen. The agent sees the damage, verifies the details, and clicks “Approve” all on one page.

Conclusion: A New Era of Flow

The File Preview component represents Salesforce being a holistic workspace. By integrating document viewing into the automation engine of Flow, Salesforce has empowered Admins to build tools that feel like custom-coded applications without writing a single line of Apex. As we saw in our testing, the component is robust and user-friendly. Most importantly, it keeps users focused. Whether you are streamlining an approval process or simplifying a complex data entry task, the ability to see what you are working on without leaving the screen is *chef’s kiss.*

Explore related content:

What’s New With Salesforce’s Agentblazer Status in 2026

Add Salesforce Files and Attachments to Multiple Related Lists On Content Document Trigger

Profiles and Permissions in Salesforce: The Simple Guide for Admins

Add Salesforce Files and Attachments to Multiple Related Lists On Content Document Trigger

Flow builders, rejoice! Now with the Spring 26 Release you can trigger your flow automations on ContentDocument and ContentVersion Flow objects for Files and Attachments. Salesforce had delivered a new event type in the previous release that supported flow triggers for standard object files and attachments. The functionality was limited. In this release, Salesforce gave us the ability to trigger on all new files/attachments and their updates for all objects.

You could easily expand this use case to add additional sharing to the uploaded file, which is also a common pain point in many organizations. I will leave out this use case for now which you can easily explore by expanding the functionality of this flow.

Objects that are involved when you upload a file

In Salesforce, three objects work together to manage files: ContentDocument, ContentVersion and ContentDocumentLink.

Think of them as a hierarchy that separates the file record, the actual data, and the location where it is shared. The definition for these three core objects are:

ContentDocument: Represents the “shell” or the permanent ID of a file. It doesn’t store the data itself but acts as a parent container that remains constant even if you upload new versions.
ContentVersion: This is where the actual file data (the “meat”) lives. Every time you upload a new version of a file, a new ContentVersion record is created. It tracks the size, extension, and the binary data.
lass=”yoast-text-mark” />>ContentDocumentLink: This is a junction object that links a file to other records (like an Account, Opportunity, or Case) or users. It defines who can see the file and what their permissions are.

Object Relationships:

The relationship is structured to allow for version control and many-to-many sharing:
ContentDocument > ContentVersion: One-to-Many. One document can have many versions, but only one is the “Latest Published Version.
ContentDocument > ContentDocumentLink: One-to-Many. One document can be linked to many different records or users simultaneously.

ContentDocumentLink is a junction object that does not allow duplicates. If you attempt to create the relationship between a linked entity and the content document when it already exists, your attempt will fail.

What happens when a file is uploaded to the files related list under an object?

Salesforce creates the ContentDocument and ContentVersion records. Salesforce will also create the necessary ContentDocumentLink records; often one for the object record relationship, one for the user who uploaded the file.

For each new file (not a new version of the same file) a new ContentDocument record will be created. You can trigger your automation based on this record being created, and then create additional ContentDocumentLink records to expand relationships and sharing.

Building Blocks of the Content Document Triggered Automation

For this use case I used a custom object named Staging Record which has dedicated fields for Contact and Account (both lookups). This method of uploading new documents and updating new field values to a custom record is often used when dealing with integrations and digital experience users. You can easily build a similar automation if a ContentDocumentLink for the Account needs to be created when the file is uploaded to a standard object like Contact.

Follow these steps to build your flow:

1. Trigger your record-triggered flow when a ContentDocument record is created (no criteria)
2. Add a scheduled path to your flow and set it up to execute with 0 min delay. Under advanced settings, set up the batch size as 1. Async seems to work, as well. I will explain the reason for this at the end of the post.
3. Get all ContentDocumentLink records for the ContentDocument
4. Check null for the get in the previous step (may not be necessary, but for good measure)
5. <span style=”font-weight: 400;”>If not null, use a collection filter to filter for all records where the LinkedEntity Id starts with the prefix of your custom object record (I pasted the 3 character prefix into a constant and referenced it). Here is the formula I used: LEFT({!currentItem_Filter_Staging.LinkedEntityId},3)= {!ObjectPrefixConstant}
6. Loop through the filtered records. There should be only one max. You have to loop, because the collection filter element creates a collection as an output even for one record.
7. Inside the loop, get the staging record. I know, it is a get inside the loop, but this will execute once. You can add a counter and a decision to execute it only in the first iteration if you want.
8. Build two ContentDocumentLink records using an assignment. One between the ContentDocument and the Contact on the staging record, the other one between the ContentDocument and the Account. You could add additional records here for sharing.
9. Add your ContentDocumentLink records to a collection.
10. Exit the loop and create the ContentDocumentLink records using the collection you built in one shot.

Here is a screenshot of the resulting flow.

Here is what happens when you create a staging record and upload a file to Salesforce using the related list under this record.

Here is the resulting view on the Contact and Account records.

Why is the Scheduled Path or Async Path Necessary?

When you build the automation on the immediate path, the ContentDocumentLink records are not created. You don’t receive a fault email, either, although the automation runs well in debug mode. I wondered about why that is and set up a user trace to see what is happening. This is the message I have found that is stopping the flow from executing:
(248995872)|FLOW_BULK_ELEMENT_NOT_SUPPORTED|FlowRecordLookup|Get_Contact_Document_Links|ContentDocumentLink
According to this the get step for ContentDocumentLink records cannot be bulkified, and therefore the flow cannot execute. Flow engine attempts to always bulkify gets. There is nothing fancy about the get criteria here. What must give us trouble is the unique nature of the ContentDocumentLink object.

The async path seems to bypass this issue. However, if you want to ensure this element is never executed in bulk, the better approach is to use a scheduled path with zero delay and set the batch size to one record in advanced settings.

Please note that the scheduled path takes a minute to execute in my preview org. Be patient and check back if you don’t initially see the new ContentDocumentLink records.

Conclusion

In the past, handling file uploads gave flow builders a lot of trouble, because the related objects did not support flow triggers.

Now that we have this functionality rolling out in the latest release, the opportunities are pretty much limitless. The functionality still has its quirks as you can see above.

I would recommend that you set up a custom metadata kill switch for this automation so that it can easily be turned off for bulk upload scenarios.

Explore related content:

Top Spring 26 Salesforce Flow Features

Should You Use Fault Paths in Salesforce Flows?

How to Use Custom Metadata Types in Flow

See the Spring 26 Release Notes HERE.

Why Traditional Support Models Fail Salesforce Managers – and How Flow Canvas Support Changes the Game

If you’re the Salesforce platform owner at a business or nonprofit, Salesforce is the backbone of your revenue or donation engine. It routes leads, guides proposals, launches projects, and keeps every stage of the client life cycle humming. When it works, no one notices; when it doesn’t, all eyes turn to you.

Yet most vendor-support offerings were never designed for the blend of urgency, nuance, and budget constraints that mid-sized firms face. A 2023 Intelligent CIO survey found 72 percent of CIOs call the standard vendor-support model “inadequate.” Top complaints? Lack of accountability and lack of expertise—often when third-party packages enter the picture.*

This post unpacks why that gap exists, what it costs in real dollars (and reputation), and how a new model, Flow Canvas Support, gives operations leaders the breathing room they’ve been looking for.

Why Mid-Sized Firms Need a Different Approach

Large enterprises paper over support gaps with headcount: release managers, on-call admins, vendor-management teams. Mid-size firms run lean by design; your Salesforce admin often doubles as analyst, release gatekeeper, and part-time data steward.

That’s precisely where traditional support collapses. You don’t need generic “how-to” articles. You need a specialist who understands why your project-intake-form Flow triggers the Apex code—and what happens downstream if that code errors out. And you need that person fast, not in two-three business days.

With personalized support plans and coaching that fits real schedules, Flow Canvas is ready to step in when things break. We help admins go from barely keeping up to confidently moving forward. It’s all about helping your admins fix automation errors fast, and build the kind of team that makes Salesforce shine.

Flow Canvas Support is your go-to resource for expert help, offering managers and teams dependable, on-demand assistance for flow errors, trigger issues, and configuration questions.

Enter Flow Canvas Support

Flow Canvas Support was built by architects who spent years inside professional-services orgs facing exactly those pain points. Rather than sell another rigid managed-services block, we flipped the model:

• Fast human response – You get human response to your cases. You decide when you need real-time live support of a Salesforce support engineer.
• Flow-and-Apex first – Deep specialization in automation, both for flow and Apex code.
• Coaching baked in – Every incident doubles as a mini-workshop, so your admin leaves smarter than they arrived.
• Month-to-month flexibility – Pick one of the affordable monthly plans and cancel anytime.

Make Salesforce Work Smarter for Your Team​

Our support plans are built to stabilize your CRM operations, enhance business processes, and achieve the performance levels you targeted. Enjoy increased ROI with affordable, personal, and straightforward support from real people—not chatbots. Elevate your CRM from a source of frustration to a powerhouse of productivity, with solutions that fit perfectly with your business goals and growth trajectory.

Your On-Demand Safety Net

Flow Canvas Support is designed to extend the capabilities of your Salesforce team without the need for additional full-time hires. Whether you’re a business owner, manager, a developer managing multiple orgs, or a consultant needing an extra hand, Flow Canvas Support provides responsive, knowledgeable assistance precisely when it’s needed.​

Flexible Support Plans

Flow Canvas offers three tiered support plans to accommodate varying needs and budgets:​

• Silver Plan: At $95/month, this plan includes up to 2 tickets per month. Live support is available at $115 per hour for low-code issues and $155 per hour for code-related challenges.​
• Gold Plan: Priced at $195/month, it covers up to 5 tickets monthly. Live support rates are $105 per hour for low-code and $145 per hour for code issues.​
• Platinum Plan: For $295/month, this plan offers up to 8 tickets per month, with live support at $95 per hour for low-code and $135 per hour for code-related assistance.​

Learn more here 👉🏼 https://flow-canvas.com/flow-canvas-support/

These plans are designed with flexibility in mind, allowing you to scale support based on your team’s capacity and workload. With no annual contracts, you maintain control over your budget and roadmap.​

As a manager or business owner, you’re responsible for keeping operations smooth, supporting your team, and protecting your Salesforce investment. But when your admin stretches thin—firefighting bugs, chasing automation errors, and scrambling to keep up with platform changes—they miss important things. Whether your admins need backup during a big project, or you want ongoing support without the cost of another full-time hire, Flow Canvas fills the gap so your team can stay focused, confident, and capable. Supporting your admin is supporting your business.

Why is Flow Canvas Support a Better Option?

Expert Support Without the Overhead

Flow Canvas Support provides the expertise of a seasoned Salesforce team without the costs associated with hiring additional full-time staff. This approach allows businesses to access high-quality support while maintaining financial flexibility.

​Commitment to Client Success

Flow Canvas delivers value and ensures every client’s satisfaction. It meticulously designs each service to tackle common challenges, boost Salesforce ROI, and keep systems performing at their best.

Boost Your ROI Today

Embarking on your journey with Flow Canvas is straightforward. Visit the website at https://flow-canvas.com/ to explore support plans, register for courses, and learn more about how Flow Canvas experts can enhance your Salesforce experience.​

Whether you’re seeking to alleviate the burden on your admin team, enhance your Salesforce ROI, or ensure your CRM system operates at peak efficiency, Flow Canvas offers the tools and support necessary to achieve your goals.​

Conclusion

Operations managers are the unsung heroes of growth. Your ability to keep Salesforce agile dictates how quickly the business can pivot, upsell, and deliver client value. Traditional support models were built to deflect tickets, not to empower you.

Flow Canvas Support flips that script. With rapid human response, deep automation expertise, and a built-in coaching mindset, we free you from firefighting and hand you the levers of strategic impact.

Ready to see the difference? Visit flow-canvas.com and fill out the contact form to take advantage of our complimentary assessment.

Flow Canvas Support: Where every Flow has a fix—and every fix makes your team stronger. 

Frequently Asked Questions

Who is Flow Canvas Support best suited for? 

The service is ideal for Salesforce Platform Managers and Administrators who are looking for tailored support in managing their Salesforce environments. This includes troubleshooting, customization, and optimization of Salesforce systems.

How does ticket support work? 

This process involves submitting specific issues or queries through a formalized system where each submission is tracked as a case. Users receive personalized solutions for their problems, and the support team manages and resolves these tickets asynchronously.

How does live support work? 

This stage includes scheduled real-time assistance, typically provided via Zoom. Users interact directly with support professionals to troubleshoot problems, receive immediate guidance, and solve issues on the spot without the wait associated with ticket resolution.

How does the support for triggers and flows differentiate from Salesforce support?

Unlike Salesforce’s broader support, Flow Canvas focuses specifically on automation and code-related issues that often require more specialized, hands-on assistance. This approach provides a more personalized and cost-effective support option for admins dealing with specific performance issues. When your issue involves AppExchange solutions, we will work with you without unnecessary handoffs often experienced with Salesforce Support plans.

What If You Want To Stop The Service

Support plans offer a flexible cancellation policy, allowing clients to stop service anytime without long-term commitments, making it a low-risk choice for your Salesforce support needs.

Contact Flow Canvas Support today for a complimentary assessment!
https://flow-canvas.com

*Source

Note: The information provided in this blog post is based on publicly available data from Flow Canvas’s website as of April 2025. For the most current details on services, pricing, and offerings, please refer directly to https://flow-canvas.com/.

Explore related content:

How To Build Custom Flow Actions For Agentforce – Planning Phase

Stop Agentforce Dev Orgs From Expiring

How To Build Flex and Field Generation Prompt Templates in the Prompt Builder

#Apex #Automation #Flow #LowCode #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceSupport