Answer
This can be caused by an unrelated dictionary error blocking the whole cache refresh, not just the view named in the error message. Specifically, a customer-defined report or object whose generated database name would exceed Oracle's 30-character identifier limit throws its own DBNAME_TOO_LONG error partway through the same cache-refresh process, which can abort the refresh before it reaches the view the Conditional Field actually needs — leaving that view looking permanently missing even though the real problem is a different, oversized custom object name elsewhere. Check for any custom reports/objects with names close to or over 30 characters and rename them; that lets the Dictionary Cache refresh complete cleanly, which then resolves the original 'view not found' error too.