What are the limitations and the best practices in using an object common for multiple...

Hi All,

Is there any limitation in using an object common for many applications? In a case I tried, I couldn't generate the application xml due to some dependencies.

ie: I have an employee object for App-A and App-B in common. The employee object have relationships with the objects from both applications. When I tried to generate the application XML for App-A, In the tree view it shows error under 'view employee' page due to the related record view components of the objects that are not included in App-A.

As I am trying to build these applications in a way that any customer could be able to install one of the apps or both together in the same tenant without any issue, What are the best practices I should follow in this case?


Thanks and Regards,
Ithrees

Continue reading...