A conformance unit could be added to the CM stating like, "The CM/engineering tool pair shall be able to create connections to partners that have either preconfigured datasets or dynamically created datasets".
We need to review requirements and conformance units to ensure that we are not introducing something that was not intended to be required.

Add text indicating that engineering tools should be aware that some devices only support preconfigured datasets. They need to know this before delivering CCSs to the CM.
PublisherCapabilities and SubscriberCapabilities will indicate whether preconfigured datasets will be used.

Engineering tool vendors should be aware that some devices or controllers might only support pre-configured datasets, but other controller/devices might come with no pre-configured datasets. An engineering tool should be able to handle both type of configurations.

Part 83 describes that engineering tools should be able to import or export descriptors. The information model of the descriptor contains the information whether a device or a controller supports preconfigured dataset only or not. So an engineering tool has the right information available to configure a CM.
We don't think that something needs to be added in part 83.

To the previous note, this was logged against Part 81, not Part 83. The issue is what if the device or controller AC only supports dynamic datasets, but the controller/CM decided to only support preconfigured datasets? The CM profile doesn't say whether preconfigured, dynamic, or both shall be supported. So there is a potential interop problem depending on choices that the vendor makes

(this could also be considered a Part 84 issue)