RadzenDatePicker dont close after I have selected a date

RadzenDatePicker dont close after I have selected a date. Here is the code block.

    <RadzenRow style="margin-bottom: 1rem">
        <RadzenColumn SizeSM="12" SizeMD="12">
            <RadzenLabel Text="Datum" Component="DueDate" style="width: 100%" />
            <RadzenDatePicker DateFormat="dd.MM.yyyy" style="display: block; width: 100%" @bind-Value="@main.DueDate" Name="DueDate"  />
        </RadzenColumn>

    </RadzenRow>

On your website, the calendar only closes after I have selected the current date when I click in the dialog. I open the form in a Radzen dialog.
What am I doing wrong?

Best regards
Thorsten

Here is what I see in our demos:
dp-close

Great answer for a support request. Really very qualified, top performance. I had already written that it works on your website. But not in my Blazor Server app, as you can see. I can click on a date as often as I want, but your calendar doesn't close.

Animation

Best regards
Thorsten

Didn’t understood that from your first post. Can point me where you stated that it works on our demos? I only see this which I tough the picker is closed only if you click current date:

There is nothing also for Blazor server in your post.

I've scaffolded new .NET 8 Blazor Server app using latest version of Radzen Blazor Studio:

and here is how editing a date using RadzenDatePicker looks in our default template with dialog:

So I have a Blazor Server application in which we test your components. We use your dialog services. In this dialog we have several RadzenDatePickers. This is what the source looks like:

<RadzenDatePicker DateFormat="dd.MM.yyyy" style="display: block; width: 100%" @bind-Value="@main.DueDate" Name="DueDate" />

On your demo website the calendar closes when you click on a date. It doesn't do that on ours, as you saw in my last post. The short gif animation I showed how the control reacts for us. Why could it be that you always have to click next to the calendar for it to close? That's the question here?

Unfortunately this declaration is not enough to replicate the problem. Here is the app I've tested, try to replicate the problem and let me know how:

PS: The app is using our Sample database.

In Blazor Studio there is an error 2 when starting.

I try it in Visual Studio

What’s the error? Can you provide details?

warn: Microsoft.EntityFrameworkCore.Model.Validation[30000]
No store type was specified for the decimal property 'ProductPrice' on entity type 'Product'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values in 'OnModelCreating' using 'HasColumnType', specify precision and scale using 'HasPrecision', or configure a value converter using 'HasConversion'.
fail: Microsoft.EntityFrameworkCore.Database.Connection[20004]
An error occurred using the connection to database 'Sample' on server '.'.
fail: Microsoft.EntityFrameworkCore.Query[10100]
An exception occurred while iterating over the results of a query for context type 'SampleServerNET8.Data.SampleContext'.
Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is config

Error from Blazor Studio

The first one is warning and the second one says that you don’t have SQL server at the specified connection string in appsettings.json. You can modify the connection to your SQL server and add our Sample database from the following SQL script:

The example runs perfectly in Blazor Studio and Visual Studio. I then compared everything again. Everything looked the same except for the version of the components. I was on 5.0.9. Now I have version 5.1.11 and the datepicker works as it should....

To anyone who comes looking for answers to an issue like this as I did, where updating did not solve the issue. You may need to check the id isn't already being used by another datepicker, making them unique solved the issue for me.
In my case I was using a datepicker in a dialog with the same id as something outside of the dialog but still on that page. Software never fails to humble