3

Thanks to @sfdcfox and @AndrewFawcett we were able to figure an elegant way on how to create a dynamic RemoteSiteSetting for the actual salesforce org in order to use MetadataAPI, ToolingAPI and so on: Access MetadataAPI via JavaScript

Now we did bad earlier and included a longer list of Remote Sites into the managed package... :-(

Is there any chance to get rid of RemoteSiteSetting again? The package is in the wild and in use by a lot of users. So to uninstall it everywhere and let support revert it back to beta seems not to be realistic.

Improve this question
1
  • The best thing I found so far is to deactivate the RemoteSites. So if new users install the package they get a bunch of inactive settings. Still they get warning-popup in the installer and have to confirm it (which is pretty much on the save-side for a peace of inactive configuratin)
    – Uwe Heim
    Jul 30, 2014 at 7:16

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy