I can confirm the "Reboot-Solution".
We had the same problem after adding a new field. In our development system it was visible. On the QA system, mismatch-error "No corresponding EFC-Element" and the field was not displayed.
After we restarted out QA system, the field was immediately visible, and the error had disappeared.
This discussion was the only one I found regarding the "No corresponding EFC-Element" error where it was fine on the development system, but not on the QA system. Thank you for mentioning this solution here. I can confirm that reboot really seems to be a way that can help.