Good morning,
I’ve attached an image showing what happens when we add the custom field to a resource:
As you can see in the image, the bin button doesn’t appear when you hover over it, so it can’t be deleted; we have to create a new resource and transfer the information without that field.
I think this is because the text in our language is very long and the icon ends up at the bottom, rather than the text being shortened so that the icon appears in the last possible position or is placed above the text.
Best regards
Hi @mlourido
I see it’s a valid concern, but unfortunately I’m not on the team responsible for fixing it. However, I’m pretty sure you can leave this section empty when creating a resource - it won’t appear in the details for it.
If you like, you can propose a shorter alternative (if one exists and fits) for that particular resource element. Those fields are named “custom” not because they are rare or exotic - they are simple key-value elements, so you can name them “Campos de usuario” and it would still be fully correct but slightly shorter (it won’t resolve the issue, but make it less visible). We use Crowdin for translations, and you can propose the change there. I’m going to do the same for Polish 
Hi @grzegorz
Thanks for your reply. I’ll try to suggest renaming that field and making it shorter.
It would also be good to program it properly, in case something similar happens with another field in the future.
I assume this falls under the frontend team’s responsibility.
Thank you very much,
Best regards
