Custom Datatype Content Fragment with new Editor & Universal Editor

[CarlosNu]

Hello,

We have created a new datatype for the content fragment, as we need to overwrite certain fields in the universal Editor.

We have generated a custom data type, and in AEM with the old editor, it works correctly, we have tested with a colorPicker and with a normal text field.

(this example is a texfield to contribute a hexadecimal code color, not exactly a color picker) 

The problem comes when we try to visualize those fields with the custom datatype in the new editor and with universal editor:

1. new editor : It does not recognize the field and shows the following message. Field/type colorPicker/text-color is not implemented yet.

2. Universal editor. The custom datatype field does not appear.

Is it possible that custom datatypes cannot be generated for use with this? Is it necessary to have any extra configuration?

Translated with DeepL.com (free version)

[AmitVishwakarma]

To resolve the issue with custom datatypes not appearing or being recognized in the new and Universal editors in AEM:

1. Ensure Custom Datatype is Registered:

   • For the new editor or Universal Editor, ensure the custom datatype is properly registered in the relevant Content Fragment Model or Editor configuration.
   • You may need to update the model’s Editor Settings to include your custom field.

2. Check Compatibility with New Editor:

   • The new editor might not support all custom field types by default. If you're using a color picker or custom text field, make sure they are explicitly defined in the model and that the editor supports these types.
   • You may need to define a custom editor component for your field type.

3. Universal Editor Configuration:

   • In the Universal Editor, ensure your custom datatype field is included in the model's schema and that it's configured in the dialog.
   • If the field is missing, verify your field’s settings in the content fragment model editor.

4. Custom Datatype Configuration:

   • Make sure that your custom datatype is properly implemented in AEM. You may need to update the Editor Configuration to reference your custom component.

Actions to Try:

• Update Content Fragment Model: Add the custom field in the model for the new and Universal editors.
• Create Custom Editor Components: If required, create editor components to handle custom fields.
• Check AEM Version: Ensure you are using a version of AEM that supports these changes for the new and Universal editors.

By ensuring correct configuration and compatibility between your custom datatype and AEM editors, your fields should appear and work as expected.

[Julio_CesarAs1]

can you provide more info on how to proceed with the different steps ?
for example : 
point 1 and 4 how you extend and how can you check that is corrently implemented . 
point 2 and 3 how can you create a custom  editor component for out field and ue
thanks

[kautuk_sahni]

@CarlosNu Did you find the suggestion helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!