Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It only takes a minute to sign up.
Sign up to join this community
In my dev org, I could do if('{!$Permission.Manage_Advanced_Org_Settings}'){}, however, I tried to package and install in another org and got 'Manage_Advanced_Org_Setting does not exist. Check Spelling' error. I tried adding the namespace to it as well, but got the same error.
I am accessing it through JavaScript, not in an VF apex components, which may be the issue. Is there a way to do this in JavaScript and not VF?
It turns out that adding the namespace did indeed fix the issue. so $Permission.ns__MySetting (or whatever ones namespace and custom setting name is) is correct, while $Permission.MySetting caused the error when installed into other orgs that use a namespace.
My issue was, that a commented out $Permission.MySetting was still trying to be interpreted by SalesForce despite being commented out. And, since it didn't have a namespace, it caused the error.
I had this issue with remote method calls from my javascript to my apex controller as well. It seems any accessor of apex/salesforce that starts with '{!$' will be counted even if commented out and throw errors if any exist, which seems like a potential bug on their part that SalesForce doesn't seem to interpret comments correctly when those are in there and apparently doesn't count them as being commented out.
$Permission.Manage_Advanced_Org_Settings__c? – battery.cord Jul 12 '17 at 20:41$Permission.ns__MySetting. – Adrian Larson♦ Jul 12 '17 at 20:57