cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Varasset
Regular Visitor

Solution layering with base product and addons

Hi,

 

I have two solutions I'm developing in an environment, both currently unmanaged.

 

Solution A: Base product, which every customer will receive.

Solution B: Addon product to Solution A, which will be optional and incur additional charges.

 

Solution B in many cases will need to extend tables with additional columns, and add these to views and forms, that I don't want in Solution A. Does the best practice in this scenario involve development of these in separate environments, with changes to Solution B being made in an environment that has Solution A imported as managed? If the answer is yes, am I able to share a publisher across these environments for these solutions? 

 

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
cchannon
Solution Supplier
Solution Supplier

Yes, your best practice is to manage these in separate environments, although it is not strictly necessary, it is just a much safer way of doing things.

 

This is because it can be surprisingly easy to accidentally drop unintended dependencies into your managed solution A if it is unmanaged in the same place as B. By having one environment where the only unmanaged content is A and a totally separate environment where the only unmanaged content is B, it is much easier for you to guarantee you don't accidentally cross your dependencies and break your solution.

 

WRT publisher, that's your business. The publisher will move with Solution A so it is available to you in environment B. Use the same publisher or use different publishers for the two solutions: there is no constraint to force you one way or the other.

View solution in original post

1 REPLY 1
cchannon
Solution Supplier
Solution Supplier

Yes, your best practice is to manage these in separate environments, although it is not strictly necessary, it is just a much safer way of doing things.

 

This is because it can be surprisingly easy to accidentally drop unintended dependencies into your managed solution A if it is unmanaged in the same place as B. By having one environment where the only unmanaged content is A and a totally separate environment where the only unmanaged content is B, it is much easier for you to guarantee you don't accidentally cross your dependencies and break your solution.

 

WRT publisher, that's your business. The publisher will move with Solution A so it is available to you in environment B. Use the same publisher or use different publishers for the two solutions: there is no constraint to force you one way or the other.

View solution in original post

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Power Apps June 2021

June Power Apps Community Call

Did you miss the call? Check out the recording here!

Users online (78,471)