When an Application Configuration Package (ACP) export ends up containing custom fields belonging to two or more different components/modules (e.g. one field in Enterprise/enterp and another in Accrual/accrul), how should that be organized in the customer-solution git repository — does it need to be split into separate ACP files per component?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

There's no technical requirement forcing a split, but it's best practice to keep configuration organized by component/module — export and store separate ACP files per component even when nothing technically prevents combining them into one. Keeping the ACPs component-scoped makes them easier to manage, review, and place correctly in the repository structure documented for configuration management, rather than ending up with a single ACP that mixes changes across unrelated modules.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions