Best Practice for Reusing Functionality and DAC Fields from Another Customization

​@bihalivan15   The recommended approach would generally be to make the first customization a dependency of the second customization, rather than duplicating the DAC fields or functionality.

If the second customization needs to access DAC extensions, graph extensions, or other functionality introduced by the first project, you can reference the first customization's assembly/project and build the second customization against it. This keeps the shared functionality in one place and avoids maintaining duplicate code.

Another option, especially if the functionality is going to be reused across multiple customization projects, is to move the common DAC extensions and business logic into a shared customization library/assembly and have the individual customization projects reference that shared library.

I would avoid copying the DAC fields or implementation from one customization into another, as that can lead to duplicate definitions, upgrade issues, and maintenance problems.

The best structure depends on whether the first customization is always going to be deployed together with the second one. If they are independent/customers may deploy them separately, I'd lean toward a shared library or common customization layer. If the second customization will always depend on the first, treating the first project as a dependency is usually simpler.

Hi ​@bihalivan15 ,

Is the DAC field/functionality conceptually common to both customizations?

• Yes → Move it into a shared/common customization package and let both projects consume it.
• No, B is an extension of A → Make B dependent on A.
• Only a small amount of code is shared → Dependency on A may be simpler, but avoid copying the DAC extension.
• Large amount of common code → Consider a shared customization/library architecture.

The key principle is: don't duplicate DAC extensions or business logic merely because they are currently implemented in another customization project. Keep ownership of the shared DAC fields/functionality in one place and make the dependency explicit.

Hope above helps!!