Is there a reason why deleted fields still used in element don’t result in an Issue in the editor ?
We don’t count them as issues as we don’t actually delete the data (you can restore the fields). that’s why.
1 Like
Ok.
As deleted fields don’t appear in the App Search Tool > Use field, it’s not easy to clean the app.
1 Like
@emmanuel, @nicolas_dap is right, I’m in the same situation now.
I expected to get a lot of issues while restructuring the data architecture, instead everything is fine.
This is an important problem because: there’s no way to find programmatically every single usage of the deleted field, and it can be tricky to find them by testing alone.
Before erasing a field, I place a ‘z_’ in front of the field I want to erase. Then, I make a search for that field in the App Search Tool. Identify and replace everything I need. Then I delete the field and optimize the code. Longer process, but working for now 
5 Likes
@JohnMark, I use to do exactly the same “z_”
1 Like
It would be much better if issues showed up as sometimes you don’t know.
1 Like
About this,
This time, an unfamiliar custom data type deletion occurred, which we were able to restore immediately, but we lost the trust of some customers because we didn’t realise it until too late.
Although this is a collaborative project, it is possible that someone accidentally hit the trash button. In that case, we apologise. However, no one has any idea what happened.
So I would like to say that this would be very helpful as a safety against human error at least.