Skip to main content
Featured group

Salesforce ISV Community Group

The Salesforce Salesforce ISV Community Group is a virtual resource to learn about Salesforce features and partners and network with fellow Salesforce Administrators, Developers, Users, Partners, and Employees. Community Group Leader: Steven Fouracre Community Group Leader Contact: isvcommunity-vt@trailblazercgl.com Register for Meetings/Events here: https://trailblazercommunitygroups.com/salesforce-isv-community-group

Hi All,

We are facing an issue with a managed package related to custom permissions assignment.

We have included a custom permission in our managed package. When the package is installed using the “Install for All Users” option, we observe that the custom permission becomes available across all profiles/users in the org.

However, our requirement is that this custom permission should not be assigned to all profiles by default.

We would like to understand:

  •  Can managed packages update profiles to include custom permissions during installation? 
  •  Could this behavior be caused by profile metadata being included in the package? 
  •  What is the recommended approach to ensure custom permissions are not automatically assigned to all users

Any guidance or best practices would be really helpful.

Thanks in advance!

1 answer
  1. Divya Chauhan (Kcloud Technologies) Forum Ambassador
    Apr 16, 9:55 AM

    Yes, this can happen because managed package profile settings are applied during install, and custom permissions can be included in those profile settings. Salesforce also recommends using permission sets instead of profiles for access control.

0/9000

Hi All,  

 

I am working on an App which I am planning to list in AppExchange. The app uses AWS as a backend and connects to multiple orgs that customer may have(sandbox and production). I have apps running on EC2 instance that will connect to multiple salesforce orgs via APIs.  

 

I am planning to have an LWC component in my app to capture the client credentials of all the orgs and in the background, I will create an AWS Secrets Manager record to store the client id and client secret. There is nothing stored in AWS. The other services running on the EC2 instance will use the credentials stored in AWS Secrets manager to connect to the orgs.  

 

I wanted to understand if there would be any challenges during the security review due to this approach. Any help on this would be greatly appreciated. Thanks

0/9000

I previously submitted a 2GP managed package for Security Review, but the submission failed

due to several issues reported in the findings. 

After addressing all the required fixes, I created and uploaded a

new 2GP package version.

When I attempt to resubmit the package for Security Review, the system indicates that a new submission requires a new payment.

Since this is a resubmission of the same product, only with fixes applied, I would like to clarify the following:

  1. How can I resubmit a corrected 2GP package version under the same Security Review case without being charged again?
  2. Is there a specific step to link my new package version to the previously failed review?
  3. Or should I contact the Security Review team directly to reopen the previous case?

Any guidance or official instructions would be greatly appreciated. 

 Thank you!

1 answer
  1. Dec 4, 2025, 8:35 AM

    you don't need to pay again if it's still tied to the same review case. You’ll want to reply to the original security review email (or open the case in the Partner Community) and give them the new package version number so they can attach it to the existing submission. If the case is closed, log a Partner Support case asking them to reopen it for resubmission.

0/9000

I'm running into an issue upgrading an Apex class from version 23 to 45. The class is defined with the `global` modifier and utilizes `@httpGet` and `@httpPost` annotations.  The problem appears to be a mismatch between the existing method signatures and what the annotations are expecting in the target version (45). 

 

Unfortunately, the class is no longer used and is really just a placeholder anymore, but since it's defined as a global class, we can't remove it. 

 

Here's a list of some of the solutions I've tried: 

- creating new methods that properly implement the httpGet and httpPost method signatures, leaving the existing methods in place 

- removing the annotations 

- bumping the version in our packaging org 

- just fixing the method signatures 

 

I'd love some guidance on what my options are for upgrading the API Version on this class. 

 

Here are the contents of the class if it helps. 

 

@RestResource(urlMapping='/POProcessor/*')

global with sharing class POProcessorRest {

@HttpGet

global static myobject__c doGet(RestRequest req, RestResponse res) {

return [select id, name from myobject__c limit 1];

}

@HttpPost

global static myobject__c doPost(RestRequest req) {

return [select id, name from myobject__c limit 1];

}

}

2 answers
  1. May 29, 2025, 4:23 PM

    I tried making these changes, but when I try to deploy the changes to our packaging org, it fails.  I can't change the method signature because it's global, and I can't remove the annotations from the methods with the bad signature. :( 

     

    === Deploy Errors

    PROJECT PATH ERRORS

    ────────────────────────────────────────────────── ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

    force-app/main/default/classes/POProcessorRest.cls Global/WebService identifiers cannot be removed from managed application: Method myobject__c doGet(System.RestRequest, System.RestResponse)

    force-app/main/default/classes/POProcessorRest.cls Global/WebService identifiers cannot be removed from managed application: Method myobject__c doPost(System.RestRequest)

    09:17:42.251 ended SFDX: Deploy This Source to Org

    09:19:49.772 Starting SFDX: Deploy This Source to Org

    === Deploy Errors

    PROJECT PATH ERRORS

    ────────────────────────────────────────────────── ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

    force-app/main/default/classes/POProcessorRest.cls Previously annotated identifier with @HttpGet must still be annotated: Method myobject__c doGet(System.RestRequest, System.RestResponse) (8:25)

    force-app/main/default/classes/POProcessorRest.cls Previously annotated identifier with @HttpPost must still be annotated: Method myobject__c doPost(System.RestRequest) (18:25)

    09:19:53.989 ended SFDX: Deploy This Source to Org

0/9000
1 answer
0/9000

Hello Steve, 

In March, the Trier, Germany Admin Group started a virtual Salesforce ISV Landscape Series, with four English episodes published so far, others upcoming and planned. 

 

We are featuring individual ISVs and their solutions, both well-established and budding, in a webinar format. Is that something that could interest you here?

  • So far we've featured Qkom, TITAN, Sitetracker and GoElephant. Cf. our playlist Salesforce ISV Landscape – English
  • Upcoming are Document Studio (Viewer), Permissions Assistant, Campaign Audience Builder, PDF Butler, FormulaShare and Mirage

Thanks, 

René

0/9000

Hello, 

Does anyone have the list of the typical Salesforce Personas and roles they use within SF Demos: 

Lauren Bailey 

Rob Abilin

1 answer
  1. Mar 6, 2025, 6:57 AM

    @Heather Olsen The personas differs based on the Salesforce products used. For Sales, it could be BDE, Sales Manager, Sales Director etc, for Service, it could be Support Reps, Support Manager and so on!!! Which SF product personas you are looking for?

0/9000

Hi 

 

Im busy building some content to deliver a series of events to help everyone in the group, regardless of your background and level. 

 

The first event could be either: 

 

  1. 2nd Generation Packaging
  2. Agile processes and how this can super charge your projects. - This won't be a boring lecture of have some daily stand ups etc that we all know but will include some surprising things that you wont expect

Please let me which you'd like by replying with a comment, simply replying 1 or 2 

 

Steve 

Your Host

0/9000

Hi All 

 

Our group has teamed up with Salesforce Hulk, a formidable Salesforce community and supporter of ISVs.  

Have a read of the attached which will give you knowledge of how Salesforce Hulk can help you organisation. 

 

Steve  

Your Host

0/9000

Hi All

 

Thank you all for joining. Our group is only 2 days old but we are already 26 members which is a great start.

If everyone invites 10 members we will grow extremely rapidly and importantly require that critical mass to ensure enough attendees per event.

 

Please invite at least 10 people you know to join our group

 

Regards

Steve

0/9000