Add Support for Professional / Group Edition about sfdc-related-files-lightning HOT 4 OPEN

Thank you so much for these detailed instructions! I actually completely missed the managed package installation URLs in the release notes.

Unfortunately, managed package installation fails with the following error:

1. Apex Classes(classes/CF_ChildFilesControllerTest.cls) Missing feature
Installing this package requires the following feature and its associated permissions: Apex Classes

After hunting around online, my best guess is that we're failing one of these requirements. Perhaps this app needs a security review?

from sfdc-related-files-lightning.

Hi @josh-padnick, thanks for your interest in my app and welcome to the Salesforce community =)

Sorry about the Deploy from GitHub link, seems that app (which I don't administer) needs attention. I'll update the install instructions on the readme, but for now you'll need to either install the provided package or manually deploy the source code with a tool like the Salesforce CLI (see instructions below).

Regarding the Professional Edition vs. Enterprise Edition, you may be out of luck since this app uses Apex code which often is restricted to Enterprise Edition. You can certainly try though, but if you get an error about missing required feature Apex then you know it's probably the org edition.

To use custom Lightning Components in your org, you'll need to deploy My Domain.

Manual Install Instructions

1. Install the Salesforce CLI.

2. Clone this repository.

git clone https://github.com/douglascayers/sfdc-related-files-lightning.git
cd sfdc-related-files-lightning

3. Authorize your org with Salesforce CLI using the following command, replacing YourOrgAlias with an alias of your choice.

sfdx force:auth:web:login --setalias YourOrgAlias --setdefaultusername

If connecting to a sandbox, add the --instanceurl https://test.salesforce.com argument to the above command.

4. Deploy metadata to your org with Salesforce CLI using the following command, replacing YourOrgAlias with the alias you provided in step 3 above. When deploying to production, you may need to either (a) update the code or (b) relax validation rules if any of the apex tests in this package fail during installation. If you install the managed package, you skip this headache.

sfdx force:mdapi:deploy --deploydir src --targetusername YourOrgAlias --wait 10

Resources

• 📺 Lightning Platform Orientation
• 📺 Visual Studio Code for Salesforce Developers
• 📘Quick Start: Visual Studio Code for Salesforce Development
• 📘Develop an App with Salesforce CLI and Source Control
• https://developer.salesforce.com

from sfdc-related-files-lightning.

Hi @josh-padnick,

You're correct, for Group and Professional Edition orgs the feature Apex is not supported so the code for this app can't be created/deployed to the org.

I'm not registered as an ISV and there are hoops to jump through to get an app through the Security Review process and on to the AppExchange -- unfortunately too many hoops for me to jump through currently for a part-time open source project. Sorry :(

from sfdc-related-files-lightning.

Completely understood. Thanks for your efforts, anyway!

from sfdc-related-files-lightning.