nikhilj0421
Databricks Employee
Databricks Employee

Hi @Einsatz, this is expected in DBR version 14.3 and above since we don't have a Spark context. This is happening due to the cache invalidation. 

To resolve the issue, please go with the dynamic name for the view every time.