#ISV Partner0 人正在讨论

Salesforce AppExchange Research Opportunity!

The Salesforce Research & Insights team is interested in learning about the future ISV experience on AppExchange.  We invite you to be considered for various paid feedback session(s) conducted remotely in 2024.  We will gather feedback on various ISV tools, goals and experiences for selling and transacting on the AppExchange.

Remote sessions and async opportunities will take place from February to December 2024. Please complete this brief questionnaire if you are interested in participating. If selected, you will receive a confirmation email with further details.

Thank you!

#CommUpdates #AppExchange #ISV Partner @Salesforce Research Program 

Hello everyone! 

Every month, our team collects different Salesforce solutions to update the info and remind people which contribution they make.  This time, we present a set of sustainable AppExchange solutions that can help you to go green.  I won't stop thanking @Amanda Matlock for her Medium article that provided a strong base for the collection :) 

 Maybe one of them will allow you to hit sustainable goals in your company. If you use another tools, let us know in comments. We will publish a 2d part. Thanks to these partners for their products! 

@All About AppExchange #AppExchange #ISV Partner #Sustainability  @Sustainability at Dreamforce

Hi, 

Any ISV partner get this error when trying to create an analytics template: 

insights.api.template.exceptions.InsightsTemplateException: Failed to create dashboard template [dashboard name] : org.json.JSONObject$Null cannot be cast to org.json.JSONArray

I have a support case opened but wanted to check here as well.

Also, anyone has jotted down potential pitfalls to avoid kind of a post while creating templates and distributing them?

Glad to join the group. Fastcall is an ISV partner with a highly-rated native phone app. We have two subscriptions plans in the same app and use capabilities to enable our "editions." We would love to control capabilities outside protected settings (so not via support.) And we would love to be able to bill for more granular features in our app.  We did not take the extension package route. 

Of course, when we enable capabilities in the subscriber org, we do not see these in our LMO. Huge bonus if we had this insight in our LMO. If we knew which features are enabled we could better support our subscribers.  

We are also very interested in offering smaller "light" versions of our app. Basic SMS, internal calling within a Salesforce org (internal dialer.) Great small apps that can upgrade to our full capabilities. 

@Antonio Grassi @Maiquel Cabrera 

I'm an ISV Partner but Dev Hub doesn't show up as an option in my business org's setup page.  I attempted to file a partner case about it but got told that it was out of scope and sent here then got a message that it was active in my org but it clearly isn't.  Please advise!

Guys, how do we create a "Partner Developer Edition" Org? I was solving a challenge in ISV partner trail. This challenge needs me to have a PDE before I start working on Environment Hub etc.,

I was not able to locate a signup for PDE/Environment hub. Can someone help me out? Thanks.

Hmmm, so am I overreacting? I don't think so. I think there is an issue with "all releases are backwards compatible" and I'm seeing and experiencing a few examples of this with Summer '15.

We are an ISV partner with an OEM application. We suddenly started getting an error in a Flow that essentially said "Field DeveloperName not found in object RecordType". What? RecordType is standard and DeveloperName is the Name field. Ran a SOQL query on this in the org and when we checked "Use Tooling API" the query errors with same error. When unchecked it runs fine. Ok...maybe?

We are talking about Flows and native queries not code. Code identifies what API version, other stuff doesn't. So this should have no effect.

group but his conclusion so far is that in his org there was an "issue" whereas in other orgs it was fine. This is same thing we are seeing.

A MAJOR issue is that this app is deployed in other orgs and we DO NOT get this error. Yes, yes same version of the app. That's not good.

After a call with Support for our issue he eventually deferred it to a Known Issue