function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
eric talleyeric talley 

Can't find the forceContent:fileUpload Lightning component in the 'New Lead' flow

feels like a bug since my flow seems to be setup correctly
User-added image
<?xml version="1.0" encoding="UTF-8"?>
<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
    <interviewLabel>New Lead {!$Flow.CurrentDateTime}</interviewLabel>
    <label>New Lead</label>
    <processType>Flow</processType>
    <recordCreates>
        <name>Create_lead</name>
        <label>Create lead</label>
        <locationX>50</locationX>
        <locationY>200</locationY>
        <assignRecordIdToReference>LeadId</assignRecordIdToReference>
        <connector>
            <targetReference>File_Upload</targetReference>
        </connector>
        <inputAssignments>
            <field>Company</field>
            <value>
                <elementReference>Company_Name</elementReference>
            </value>
        </inputAssignments>
        <inputAssignments>
            <field>LastName</field>
            <value>
                <elementReference>Last_Name</elementReference>
            </value>
        </inputAssignments>
        <object>Lead</object>
    </recordCreates>
    <screens>
        <name>File_Upload</name>
        <label>File_Upload</label>
        <locationX>54</locationX>
        <locationY>297</locationY>
        <allowBack>true</allowBack>
        <allowFinish>true</allowFinish>
        <allowPause>true</allowPause>
        <fields>
            <name>Upload_File</name>
            <extensionName>forceContent:fileUpload</extensionName>
            <fieldType>ComponentInstance</fieldType>
            <inputParameters>
                <name>label</name>
                <value>
                    <stringValue>Upload_File</stringValue>
                </value>
            </inputParameters>
            <inputParameters>
                <name>recordId</name>
                <value>
                    <elementReference>LeadId</elementReference>
                </value>
            </inputParameters>
            <isRequired>true</isRequired>
        </fields>
    </screens>
    <screens>
        <name>X1st_page</name>
        <label>1st page</label>
        <locationX>55</locationX>
        <locationY>84</locationY>
        <allowBack>false</allowBack>
        <allowFinish>true</allowFinish>
        <allowPause>true</allowPause>
        <connector>
            <targetReference>Create_lead</targetReference>
        </connector>
        <fields>
            <name>Last_Name</name>
            <dataType>String</dataType>
            <fieldText>Last Name</fieldText>
            <fieldType>InputField</fieldType>
            <isRequired>true</isRequired>
        </fields>
        <fields>
            <name>Company_Name</name>
            <dataType>String</dataType>
            <fieldText>Company Name</fieldText>
            <fieldType>InputField</fieldType>
            <isRequired>true</isRequired>
        </fields>
    </screens>
    <startElementReference>X1st_page</startElementReference>
    <variables>
        <name>LeadId</name>
        <dataType>String</dataType>
        <isCollection>false</isCollection>
        <isInput>false</isInput>
        <isOutput>false</isOutput>
    </variables>
</Flow>

 
Paul LambertPaul Lambert
I'm having the exact same problem today!
Erik MolstadErik Molstad
I'm also seeing this.  I created the flow in my devloper environment and a separate trailhead playground.
Edoardo GaldiEdoardo Galdi
Me too
Jerome Daniel 3Jerome Daniel 3
It is the same for me
Erin Jenkins 3Erin Jenkins 3
I have the same error.
Nir SagiNir Sagi
The same error for me
Rhys CuffRhys Cuff
Same problem here too
Anderson da Silva 9Anderson da Silva 9
Same for me :(
Chris DuarteChris Duarte
I am sorry about this. We discovered that the challenge checker is looking for the second screen name to be Upload_Files (with an s on the end) rather than the lightning component being called Upload_File. We're getting it fixed. In the meantime, if you change the second screen name unique name to Upload_Files, you should be able to get through it.

We made a knowledge article on this (see below). My apologies again. 

https://force.desk.com/customer/portal/articles/2932027-lightning-flow-workaround-for-challenge-guide-users-through-your-business-processes-with-cloud-flow-designer?b_id=13478
Erik MolstadErik Molstad
Thank you, this worked.
Merlyn Manuel (Gomez)Merlyn Manuel (Gomez)
Thank you, Chris.. I finally completed it. 
 
Chris DuarteChris Duarte
Issue now resolved in production. We are now checking for what is documented in the challenge. You can disregard the workaround.

My apologies again for the trouble.