What is the order of initialization of Lightning components?
I am building a Customer Community using the Napili Template. I have customized the home page by adding a few custom-built Lightning Components. I want to ensure that all the external JavaScript libraries are loaded last (lazy loading) so that the end-user does not have to stare at a blank page while all those libraries get loaded. For this I thought putting the <ltng:require> tags in my footer will work because I assumed that the components are initialized in order from top to bottom of the page and the Footer will initialize (i.e. fire the init event) all last since I had placed it at the very bottom of the page BUT in practice I am observing that many times the footer initializes before the other components do.
 

I am using my Force.com (Unlimited Edition) org as the IDP(Identity Provider) and at the same time I have created a Customer Community on that same org which I want to use as my SP (service provider). The pre-login URL to my SP has some parameters in it which must be available after login as well.
Problem is that although I am able to successfully login to my SP using my IDP, the query string parameters are no more available after login. E.g.,

I am developing a Customer Community with the Lightning "Napili" template and need to embed the Open Graph icons for Twitter, Facebook and LinkdIn in my Lightning component. Any suggestion or sample code is urgently needed as I have never worked with Open Graph before. 

Is there any way to use SOQL on the Topic standard objects to know which topic is a featured topic and which is a navigational topic?

Is there anyway to prevent URL encoding of the webservice endpoint which I want to callout to from my SFDC org? I am trying to call a webservice hosted on another non-SFDC public cloud from my SFDC org but the endpoint keeps getting URL encoded automatically by the time it reaches its destination.
To be more specific, I am trying to send across a security certificate as the request parameter and its value contans commas as a separator. But since URL encoding is proactively converting these commas to %2C the URL keeps failing at the webservice host which will not allow anything else but a literal comma. In my apex class which makes the callout I am NOT using EncodingUtil.urlEncode() to explicitly encode the endpoint but still it gets url encoded.

For example: 
http://webservice.thirdparty.com/sfdcaccept?accessMode=r&auth=CN%3D01,OU%3DMyDept,OU%3DMyCompany,O%3MyWorkplace,C%3DAP&expiration=1653514361&secKey=xxxxxxx

 is reaching the 3rd party webservice as...

http://webservice.thirdparty.com/sfdcaccept?accessMode=r&auth=CN%3D01%2COU%3DMyDept%2COU%3DMyCompany%2CO%3MyWorkplace%2CC%3DAP&expiration=1653514361&secKey=xxxxxxx
 

What is the order of initialization of Lightning components?
I am building a Customer Community using the Napili Template. I have customized the home page by adding a few custom-built Lightning Components. I want to ensure that all the external JavaScript libraries are loaded last (lazy loading) so that the end-user does not have to stare at a blank page while all those libraries get loaded. For this I thought putting the <ltng:require> tags in my footer will work because I assumed that the components are initialized in order from top to bottom of the page and the Footer will initialize (i.e. fire the init event) all last since I had placed it at the very bottom of the page BUT in practice I am observing that many times the footer initializes before the other components do.
 

Is there any way to use SOQL on the Topic standard objects to know which topic is a featured topic and which is a navigational topic?

I am using my Force.com (Unlimited Edition) org as the IDP(Identity Provider) and at the same time I have created a Customer Community on that same org which I want to use as my SP (service provider). The pre-login URL to my SP has some parameters in it which must be available after login as well.
Problem is that although I am able to successfully login to my SP using my IDP, the query string parameters are no more available after login. E.g.,

I have a batch job defined below as the scope. 

 

 

global Database.QueryLocator start(Database.BatchableContext BC){

return Database.getQueryLocator([select id, DUNS_Number__c, Parent_DUNS__c, ParentId from Account where Parent_DUNS__c != null]);
}

 

But from the debug log, I saw the scope is returned as: select id, DUNS_Number__c, Parent_DUNS__c, ParentId from Account

The where statement is ignored completely. So there are much more records returned.

I do not know what went wrong.