• ecmsdb
  • NEWBIE
  • 0 Points
  • Member since 2013

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 1
    Replies

As a way to better learn about and understand managed packages, I'd like to have a way to create, deploy to app exchange, install, test and then ultimately delete managed package apps from app exhange. Basically I guess what I want is a play version of AppExhange. Is this possible?

  • November 11, 2013
  • Like
  • 0

Is there any way to use the same namespace when creating multiple managed packages?

 

For example, assume XYZ Accounting Software Co has two applications that they want to sell, one for accounts payable and one for accounts receivable. These two applications share the same data model, which includes some custom objects that XYZ has developed.

 

If the XYZ_AR and XYZ_AP managed packages are uploaded from two different DE orgs with two different namespaces, the shared datamodel will no longer be shared, because the custom objects will have different namespace prefixes.

 

How do companies who want to sell more than one application using the same shared data model handle this?

 

Only option I can think of is to develop and deploy the shared data model as yet another managed package with it's own namespace, and then install the shared data model as an app in the XYZ_AR and XYZ_AP DE orgs.

 

Is there another way to handle this that I'm missing? Thanks!

  • November 04, 2013
  • Like
  • 0

Is there any way to use the same namespace when creating multiple managed packages?

 

For example, assume XYZ Accounting Software Co has two applications that they want to sell, one for accounts payable and one for accounts receivable. These two applications share the same data model, which includes some custom objects that XYZ has developed.

 

If the XYZ_AR and XYZ_AP managed packages are uploaded from two different DE orgs with two different namespaces, the shared datamodel will no longer be shared, because the custom objects will have different namespace prefixes.

 

How do companies who want to sell more than one application using the same shared data model handle this?

 

Only option I can think of is to develop and deploy the shared data model as yet another managed package with it's own namespace, and then install the shared data model as an app in the XYZ_AR and XYZ_AP DE orgs.

 

Is there another way to handle this that I'm missing? Thanks!

  • November 04, 2013
  • Like
  • 0