function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Yves Asselin 3Yves Asselin 3 

Challenge Not yet complete... Could not find a method named 'getIsClassic' in 'GetPropertiesApexController'.

========SECTION==========================================
TRAILHEAD: Develop for Lightning Experience  =>
Build Flexible Apps with Visualforce Pages and Lightning Components =>
Use a Visualforce Page as a Component in a Lightning Page 

https://trailhead.salesforce.com/trails/lex_dev/projects/workshop-lightning-programmatic/steps/programmatic-step-3
=========================================================
CHALLENGE ERROR: 
Challenge Not yet complete... here's what's wrong: 
Could not find a method named 'getIsClassic' in 'GetPropertiesApexController'. Check your code and try again.

The Lesson directives are clear, and everything works but the error persists on the challenge… I continued onto the next unit andeverything works… Except I get this error in the challenge… Note that this exercise was done on a brand new org.

It looks like a bug but hard to tell… Any work arounds?
Best Answer chosen by Yves Asselin 3
Squire TH KershnerSquire TH Kershner
UPDATE:  If you simply add the same method you added to DreamhouseProspects to the GetPropertiesApexController class, the module will pass.  It's not a fix, but let's you move forward.

All Answers

Alain CabonAlain Cabon
It is just perhaps a wrong selected org (you have modified the org1 and the org2 is selected, the names of the playground orgs are very similar)
Sometimes we have to disconnect/recornnect (+clear of the cache because a wrong org is still used).

Lightning has a very strong cache system and we start by deactivate it for the superbadges with Lex components for instance.

Lightning Component Framework Specialist
In the Setup > Security Controls > Session Settings section of Salesforce Classic, disable the component cache by deactivating the setting for Enable secure and persistent browser caching to improve performance.
https://trailhead.salesforce.com/fr/super_badges/superbadge_lcf

Here that should be not necessary for a simple VFP included in Lex.
Yves Asselin 3Yves Asselin 3
I have recreated a 3rd blank playground and redid all the steps... I successfully added the new SimilarProperties to my page, renamed it to Other Properties and still get this error...
User-added imageUser-added image

User-added image



 



As per suggested by Alain, I also swiched to Classic to disable caching .. could'nt find that feature in lightning...

User-added image

any ideas anyone???
Zach HenezZach Henez
I am receiving the same challenge not complete message. I think this may be a bug.
Squire TH KershnerSquire TH Kershner
Agreed.  Nothing in the current or prior challenges appear to be connected to the GetPropertiesApexController, so if it's not loaded by the Dreamforce app, I'm not seeing why/how that method would have been added?
Squire TH KershnerSquire TH Kershner
UPDATE:  If you simply add the same method you added to DreamhouseProspects to the GetPropertiesApexController class, the module will pass.  It's not a fix, but let's you move forward.
This was selected as the best answer
Yves Asselin 3Yves Asselin 3
Thanks Squire TH Kerhner... it worked!!!

And for those of you who are a little code challenged like me, what he meant was copy this line:

    public Boolean getIsClassic() {
    return (UserInfo.getUiThemeDisplayed() == 'Theme3');
    }

 which was from the DreamhouseProspects.apxc
and paste it into the GetPropertiesApexController.apxc
...right after  – private final Property__c prop;
TexasRobTexasRob
Looks like they missed a process in Step 3. The "fix" is to add the following code to the DreamhouseProspects Apex Class.

    public Boolean getIsClassic() {
        return (UserInfo.getUiThemeDisplayed() == 'Theme3');
    }
Chris DuarteChris Duarte
Thank you all. Trailhead team is aware of this issue and we are resolving in our next content release. Our apologies for the trouble.