It looks to me like you're trying to "copy and paste" the core components which is not a best practice. You see, when working with core-components we're expected to follow "proxy pattern" which essentially means we need to extend (sling:resourceSuperType) the core component.
If for some reason you still need to "copy and paste" a core component then make sure you provide your own properties for the component such as: component group, inherit from proper components (sling:resourceSupertType).
Ok, so it loooks like you're doing it the right way....
I see you are following "Sling Merger" for providing your custom "field label" to your "page component"; by looking at the image it seems like you created the right structure for the field but maybe we need to double check. Here's what I would:
1) copy paste the whole dialog from core component into custom component. This is to make sure we do not have structure issues
2) Make sure you select proper component when creating the "editable template" (maybe you are still selecting a previous version of the component for which you have not updated dialog)