Feed

Hi @Kalyan Ranjan

It is normal for Launch to open either the Playground Starter landing page or the Setup page. Identify the Playground where you completed the challenge. Go to the relevant module/unit, and in the Challenge section(bottom), choose the right hands-on org and clicking Launch.

If the Playground is not already connected, click Connect Org to link it to the module.

Once the correct Playground is connected, click Check Challenge to earn points to validate your work and complete the challenge.

Hi @jill dixson

Please check the solution provided in this thread -

Hope it helps!

Hi, @Blake Swan

I may still not fully understand what you’re trying to achieve, but is this the kind of calculation you had in mind, as shown in the attachment? Please take a look. 

<sample>

@Himanshu Shekhar

I put:  

Content Document ID= File Upload > Related Record ID but it's not working and I can't find Title like you mentioned.  

Also, if I don't do the loop and if the partner submits 2 more more attachments, will it just capture one documents' name?  If so, that's still perfect.  This File Name field will populate into another related object's text field.  

For Local Pack visibility, I’d look at the factors together rather than relying on one tactic. Google says local rankings are primarily influenced by relevance, distance and prominence.

For an HVAC business, I’d make sure the Google Business Profile is complete and accurately categorized build genuine customer reviews keep business information consistent across important local sources and strengthen the website’s local relevance with useful service area content.

Local backlinks can help with prominence but I’d focus on relevant, legitimate local or industry sources rather than simply building a large number of links. The quality and relevance of the local signals matter more than just the quantity.

Hi @Pranjal Budhlakoti, 

When one sObject variable is assigned to another, both variables refer to the 

same sObject instance

 in memory. 

For example:

Account acc1 = new Account(Name = 'Original');Account acc2 = acc1;acc2.Name = 'Updated';System.debug(acc1.Name); // Updated

Here, changing acc2.Name also changes acc1.Name because both variables reference the same Account object.

So, assigning an sObject variable does not create a new copy

 of the record; it creates another reference to the same object.  

Hope This Helps!!