How to split a bundle field configuration?

by ssibal   Last Updated January 08, 2018 10:07 AM

Currently, we are using Configuration Split for providing components for different customers. Right now there is a component, which adds a field for an existing default content type: "A".

The problem is: the field cannot be separated because once the component is enabled (and the field configuration is active) the config export will move all the related configurations to the component's sync directory, which has a dependency on the field: form views of 'A' and also displays.

Do you have anything in your mind how to separate a bundle field completely from the default sync directory?

Related Questions

How to load field configurations in code

Updated January 26, 2017 14:03 PM

Change existing field definition

Updated January 27, 2017 14:03 PM

Add new existing field for existing content type

Updated June 12, 2017 13:07 PM

Add default image to image file programmatically

Updated August 11, 2017 10:07 AM