Hi @Vidula Khanna​ - The response was not a solution for my issue, it was more an acknowledgement that there is/was a GAP in documentation as the error was not pointing customers to the correct path to solve this issue. Hopefully this has been take care of by Databricks.

I had to refactor some SQL code to find a workaround.

Thanks for the follow-up.