DialogService not showing the DialogSideContent dialog

I followed the instructions carefully and added .css and Radzen.Blazor.js to the _Host.cshtml.
Also added the followings to the Shared\MainLayout.razor:



builder.Services.AddScoped() in the Program.cs

For testing purposes, I added two DialogServices. One for the OpenOrder "Open page as a dialog" and the other is the Side Dialog (OpenSideDialog) DialogService as in the example.
However, I am able to open the OpenOrder but not the Side Dialog. Please let me know what I am missing to get the OpenSideDialog to work. Thank you!

Hi @Mike1,

Make sure <RadzenDialog /> isn't nested in any other HTML element. This could prevent dialogs from working correctly.

Hi @korchev,

Thank you very much for your response. The RadzenDialog/> is declared in the Layout.razor and isn't nested in any other HTML element.

I put a break point on the OpenSideDialog() and I noticed that the OnClick event is only triggered once but it did not open the OpenSideDialog. Sub-sequence click did not hit the break point and did not trigger the the call to the OpenSideDialog(). However, Sub-sequence clicked on the OpenOrder() trigger the call and hit the break point and opened the OpenOrder dialog every time.

Thank you in advance for your help.

The side dialog probably renders but is behind something. You can check that with your browser's developer tools. Also you can compare your app with the Radzen.Blazor demo application.

Hi @korchev,

You're right, it's hidden behind the <RadzenDataGrid ...
My intention is to implement an advance search on the grid. When click on the side dialog button, the <RadzenDialog/.. is supposed to open where I can filter the grid but since it is hidden behind the grid, is there anyway we can show it on top of the grid?

Thank you!

The side dialog appears on top of the page by default. Check what CSS is interfering with it in your app (use your browser's developer tools). I am afraid we can't do that for you.

Another CSS element was blocking the side dialog. Thank you @korchev.