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
Julie VermeirenJulie Vermeiren 

Superbadge Lightning Experience Roll-Out Specialist Challenge #10. Help.

I am going after the Lightning Experience roll-out specialist badge and I am having issues with challenge #10. Could you give me some pointers on how to finish this challenge?  

Here is my error : The Lightning component named TrailheaDX must open a link to https://developer.salesforce.com/trailheadx/, must open in a new window (using the target attribute of ui:outputurl), and must be included in the Sales app. 

I tried everything (with controller, without controller, etc.), but still no green sign! Some people are talking about a bug. Could it be?

Please help...
User-added imageUser-added imageUser-added image
NagendraNagendra (Salesforce Developers) 
Hi Julie,

Sorry for this issue you are facing.

I finally managed to solve this. No need for a controller, if you have one just remove the component from everywhere then delete it after that create a new component with no controller and use this code
<aura:component implements="flexipage:availableForAllPageTypes" access="global" >
    <ui:outputURL value="https://developer.salesforce.com/trailheadx/" label="TrailheaDX" target="_blank"/>
</aura:component>
add it to the utility bar in the Lightning Sales App with TrailheaDX as the label.

Please let us know if this helps.

Kindly mark this as solved if the reply was helpful.

Thanks,
Nagendra
Julie VermeirenJulie Vermeiren
This is still not working. I do not know what I am doing wrong...
Scott McClureScott McClure
Hi Julie.  Were you able to get this resolved?  I am running into the same issue.  I have the the component created, added to the home page and it launches in a new window perfectly.  I am not sure what I am doing wrong?
Julie VermeirenJulie Vermeiren
Dear Scott. No, I was not able to get this resolved. I think it is a bug in the system. All my colleagues faced the same problem. 
Nirmal Kumar 91Nirmal Kumar 91
This worked for me after deleting the lightning component and adding back again as suggested by @Nagendra