How to work around customization limitiations of Form Models when CDMs are present?

Based on Limitations to Form Engine when CDMs are present would it be possible to workaround the customization limitation

Customizing of Form Model elements (by way of the FormModelMap) does not work in combination with CDM. Trying to do so might result in errors.

of Form Models backed by CDMs using the following:

A Document Model is modeled the same way as the CDM but without any CDM features so that basically the json representing a CDM document can also be interpreted as the document for the newly created Form Model?

Are there any caveats to such an approach?

Hey @andreas-fresh-mesa,

yes, you could build a CDM and transform it into a regular DM by removing the CDM-annotations. Client/FormEngine would then treat the connected Form Model as a regular form and use the regular datahandling. But if you present it with the respective data via Custom Code (eg from a tweaked LIST_CDD operation to dataservices) you could show this CDD data in the regular form.
Validations and Computations should work as in the CDM.

But you loose all the CDM data handling features. Especially the saving and link changing. So if the user shall be able to change the data, you would have to write Custom Code to split the CDD back into the original documents.

Hi @andreas-fresh-mesa,
did the reply from @felix-blazing-river answer your question or do you need further support? If it is solved, please, use the checkbox to mark the solution to your problem so that other users also know what helped in your case.
Thanks in advance!
Denise from the Discourse team