Unanswered

Use a Solution to add a custom page to a Model Driven App

(0) Share

Report

Posted on by davidyc

I'm working on a Model Driven App (MDA) which has a set of core functionality and also has optional extra 'modules' as we are calling them internally. Each module has a custom page which uses a series of additional tables and also integrates with the existing tables used by the core MDA.

We would like to keep the core MDA in one solution and have the add-on modules in separate solutions, however as soon as you add one of the add-on custom pages to the core MDA, you cannot export the core solution since it requires all of the tables used by the add-on custom page.

I hope this makes sense and I would appreciate anyone's help on how to organise our solutions so that we can implement a modularised approach.

Categories:

Application Lifecycle Management (ALM)

Power Platform Build Tools

All responses (2)

Answers (0)

davidyc 99 on at

Like (0)

Report

Re: Use a Solution to add a custom page to a Model Driven App

Thanks @FPelliccia, I realised that there isn't really a practical way to do this in the way that I wanted, however I will instead store a permission/role definition in a solution and deploy this to the customer environment to manage their access.

I'm still open to other suggestions. Ultimately I'm trying to control the availability of Model Driven App features (mainly different custom pages) based on a customer's level of subscription/service.
Federico Pelliccia 142 on at

Like (0)

Report

Re: Use a Solution to add a custom page to a Model Driven App

I don't know if this kind of approach is possible. If a component is required from another, you must implement that component in your solution. If not, the solution potentially could be broken, because you'll miss required component.