We are using the Canvas framework to build our integrated application, a part of which involves modifying the Opportunity detail page to include a new section where our application runs.  We currently have this working so that Canvas connects securely to our application, and displays our UI within the designated window correctly.  We also receive most of the data we need to initialize our application during the Canvas OAuth linkup process, with one exception: we need to know the ID of the Opportunity the user was viewing when our application was launched, but this piece of data is not supplied in the Canvas context object.

Can anybody tell us how we might be able to retrieve the Opportunity Id (or Account Id) for the detail screen the user is currently viewing when our application is launched?

It seems like a simple task, but we can't find any documentation on how to go about it.

We have a managed Canvas app where we integrate our cloud collaboration service with Salesforce in a couple of different places.  One is a dedicated tab, the other is a modified layout of the Opportunity page where we create a viewport through which our application can be accessed as part of the Opportunity detail area.

The problem we are having is that when we package the app and install it into another org, everything installs correctly except for the modified layout Opportunity page.  We can't seem to find any way to get that new layout to transfer as part of the install.  It's vital that we solve this problem.  Can anyone help?

We are using the Canvas framework to build our integrated application, a part of which involves modifying the Opportunity detail page to include a new section where our application runs.  We currently have this working so that Canvas connects securely to our application, and displays our UI within the designated window correctly.  We also receive most of the data we need to initialize our application during the Canvas OAuth linkup process, with one exception: we need to know the ID of the Opportunity the user was viewing when our application was launched, but this piece of data is not supplied in the Canvas context object.

Can anybody tell us how we might be able to retrieve the Opportunity Id (or Account Id) for the detail screen the user is currently viewing when our application is launched?

It seems like a simple task, but we can't find any documentation on how to go about it.

I'm trying to understand how the financial aspect of the ISV embedded license progam works. Various sources indicate the ISV pays 25$ / user / month. The force.com page about ISV says you pay 25% of your net revenue as royalties to force.com.

So if have a sfdc-independent app, I sell it to 2 customers, with each 20 users and charge 50$ / user / month = 2000$ / month, how much do I have to pay in total in royalties?

Thanks a lot for your answers!

Hi All,

I have following 3 questions.

1. Is there a way to communicate between two packages which were installed from app exchange as manage packages.

2. What is the way of comminicating between two salesforce orgs.

3. Can we add chatter feeds for a user using apex codes from two different installed manage packages

Thanks in advance

Hi 

I am creating an application, where I need to use Metadata API from APEX code running in an org. to fetch and update objects within the same org (kind of loopback). Through my investigations, I came to know that it is possible to achieve this by using APEX SOAP Stubs generated from MetadataAPI WSDL. This WSDL is generated with instance URL specific to my organization.  e.g <soap:address location="https://na15-api.salesforce.com/services/Soap/m/27.0"/>

In order to use APEX SOAP stubs on my org, my application need to create Remote Site Setting for above *na15* url instance in WSDL. Correct ?. Next lets say I publish this app, then:

1. How will my application behave on a different organization which is running on a differnt instance url(e.g *na1*) than *na15*. It will receive unauthorized end point exception. So definitely hardcoding *na15* was never a right choice. 

2. Is there any generic instance URL for the Metadata API I can specify and bundle Remote Site Setting for that URL in my application, which can work seamlessly in any organization to connect to itself or some other org. 

One thing I am sure, using URL.getSalesforceBaseUrl would not do much help, since it would return Organization specific URLs.