Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at the 2025 Microsoft Fabric Community Conference. March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for $400 discount. Register now

Reply
FabricUser_5037
New Member

View name is not getting updated in CREATE/ALTER script

I have this sample View created with the name 'dbo.TempView' and I have executed the script to rename the same view. Here are the picture attached:

1.png

 

 

 

 

2.png

 

Now in the object explorer, the view name seems to be changed. However, if I want to see the CREATE script of that view, it will show me the old name of that view in the script. Pictures attached below:

3.png

 

4.png

Even when I download the files using the "Download the SQL Database Project" button, the view script file reflects the new, changed name. However, within the file itself, the old name still persists.
5.png

 

6.png

 

7.png

Is there a workaround to resolve this issue, or is it a bug in the Fabric Warehouse that needs to be addressed?

3 REPLIES 3
v-priyankata
Community Support
Community Support

Hi @FabricUser_5037,
It may issue/bug, can you please raise a Microsoft support ticket. You can create a Microsoft support ticket using the link below.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.

Hope this works for you!

Thanks.

 

suparnababu8
Super User
Super User

Hello @FabricUser_5037 

 

The similar issue faced by someone. You can please go through this accepted solution - Solved: Re: Data Warehouse: Bug in ALTER Stored Procedure - Microsoft Fabric Community

 

If you want to troubleshoot the issue use this official documentation - Troubleshoot the Warehouse - Microsoft Fabric | Microsoft Learn

 

Hope the url might helps you to solve the problem.

 

Thanks!

Thank you for the response.

The provided thread seems to have a similar issue but it seems to be resolved from Microsoft end back in 2023.

However, we are currently facing the issue highlighted.
@GeethaT-MSFT Is this a known issue/bug in Fabric Warehouse? Can you provide a workaround for this issue

Helpful resources

Announcements