Explore apps for invoice automationIntegrate CRM with CLM solutions
Help & Support
Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More
Have Questions?
Data Fetcher
Return records on screen flows based off user interaction
- Business Need
- ProductivityAdmin & Developer Tools
- Requires
- Sales Cloud
- Compatible With
- Sales CloudService CloudExperience Cloud
Dynamically query Salesforce records using SOQL, SOSL or use a List View to return records in a collection variable based on user interaction on a screen flow.
Rating
Reputation
MVP
Recognized by Salesforce for their leadership, expertise, and generosity
Top Reviewer
Contribute reviews that encourage conversation and help others make informed decisions
Ranger
Lifelong learners who have earned the Ranger rank or higher on Trailhead
Showing 10 of 27 Reviews
Less Clicks - More Fun!
Love this tool! It saves so many clicks inside a flow - truly what we’re all here for. Thanks for putting it out into the community!
Excellent Component!
Easy to use and makes such a difference to my users!
This Component should be included Natively within Salesforce. So much Power to make Screen Flows Bet
Using this app has been such a pleasant experience. Great set-up documentation and an excellent support community. Would love to see this someday included within Salesforce as a native component.
Simple and amazing feature.
It's so simple to use and yet so powerful. Thank you for this!
I Have a problem with permission
In the screen component the users see this error message: The Data Fetcher screen component on this screen is reporting the following Error: You do not have access to the Apex class named 'DataFetcherController'. At first I installed the plugin only for the administrator, then when I saw the error I installed it for all users, but it didn't help and the error didn't go away. In my view, as an administrator, the data is displayed without error.
I the user guide it is mentioned that you will need to grant the apex class access to the users via permission set or profile. If you run into problems you should have received an email from me at the time of install with a link to my calendar if you are running into issues or you can reply directly to that email or the email linked in the posting above.
Beyond Impressed
I am so glad I came across this app. Josh, through his creation of Data Fetcher, shows truly how innovative and supportive the Salesforce Community is. The only feedback I would give is some more examples in the training documentation of how to write/modify the SOQL and SOSL queries. As a non-developer it was a little tricky for me to understand using the " + " syntax. Again, thank you Josh for an amazing app, screenflows are 10x more powerful, agile, and impressive.
Awesome! Thanks Josh!
Component works awesome for my use case and Josh quickly helped with a question I had to get it up and running! Thanks so much!
Endless Possibilities!
This looks like a very useful tool! I've played with it a bit and I can see so many possibilities. I have a quick question though... does the user who is running the flow need access to SOQL? Or just the objects/fields being accessed in the query?
Hi Steve the running use will need access to the controller Apex class that comes in the package along with appropriate object/field and record access Data Fetcher always runs in user mode regardless of the flow context full details on the class access are in the setup and user guide.
Makes a beautiful flow
being able to use data fetcher to get/display my records allowed me to move away from multiple flow screens but it also looks and works great.
Amazing Component - Update Fails If Used In Flows
First of all: This is one of the most important components and I use it in almost all of my screenflows. Unfortunately, it is currently not possible to update the version without removing the component from all screenflows. This is unthinkable and not possible in terms of workload. The error that is displayed when updating from version 1.4 to 2.2 is: LightningComponentBundle(dataFetcher) lwc/dataFetcher/dataFetcher.js-meta.xml: Property types can't be changed: 's'. Make sure the component is not referenced by these flow versions:.......... The component gets 5 stars as soon as the update problem is solved without removing data fetcher from all existing flows! ___ Update: I discovered josh's answer on unofficial myself and it's down to salesforce. Unfortunately there's nothing he can do about it. Quote: ".....in order to move forward to add additional functionality I had to make the decision to add a new propertytype to the xml in the LWC. Unfortunately Salesforce packaging doesn't allow for an upsert of new propertytypes when there is an update. So for ver 2.0 you would need to remove the Data Fetcher reference in existing flows update and then add it back to your flows....."
Thanks Karri!