We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

File Upload in March 23/2023 version the ValueChange event no longer fires at all.

After updating today and reading about the breaking changes in the File Uploader it seems that the ValueChange event isn't invoked at all anymore. I had to rollback to the previous version for now.


6 Replies

BS Buvana Sathasivam Syncfusion Team March 25, 2023 11:22 AM UTC

Hi Sheldon,

We want to assure you that we have made significant improvements to the performance of the FileUpload component in our Volume 1, 2023 release. You can find more information about this in our release notes at the following link: https://blazor.syncfusion.com/documentation/release-notes/21.1.35?type=all#file-upload


Regarding the ValueChange event, we have thoroughly reviewed the reported query and found that the event is properly triggered from our end. However, we would like to investigate further to help resolve the issue. To assist us in identifying the problem, we kindly request that you share your code or a runnable sample, as well as the replication procedure. This will help us replicate the issue at our end and work towards a solution.


If possible, please also provide a video that demonstrates the problem you are encountering. We will do our best to resolve the issue promptly and ensure that the FileUpload component meets your expectations.


Regards,

Buvana S



SH Sheldon March 26, 2023 03:58 PM UTC

You are right - in the simple case it does work. I thought maybe it was because the fileupload was in a modal dialog but I can't replicate that either. In my app the Browse button simply does nothing when it should open a file list. There are no console errors - do you have any suggestions on how to debug why the Browse button is opening windows explorer?


Thanks

Sheldon



SH Sheldon March 26, 2023 05:09 PM UTC

Interestingly the default Blazor InputFile works perfectly fine when I substitute if for SfFileUpload.



DW Dan Wood replied to Sheldon March 27, 2023 08:59 PM UTC

I had the same issue. I had forgotten to update script reference. This allowed the browse button to work. I am still working through other issues with the upload component.


<link rel='nofollow' href="https://cdn.syncfusion.com/blazor/21.1.35/styles/bootstrap5.css" rel="stylesheet"/>
<script src="https://cdn.syncfusion.com/blazor/21.1.35/syncfusion-blazor.min.js" type="text/javascript"></script>


SH Sheldon March 28, 2023 06:05 AM UTC

I caught that too eventually but the Browse button still does nothing. I just put in the default <Input File instead and it works fine. Not quite as pretty but I can probably figure out how to style it at some point.



UD UdhayaKumar Duraisamy Syncfusion Team March 28, 2023 05:47 PM UTC

Based on the information, we suspect that you are experiencing the reported issue due to a mismatch of script and stylesheet.


If you are using the individual NuGet package of Syncfusion.Blazor.Inputs, then you need to install Syncfusion.Blazor.Themes and also use the following script and stylesheet link to get the functionality and style for the component.

 

<link rel='nofollow' href="_content/Syncfusion.Blazor.Themes/bootstrap5.css" rel="stylesheet" /> <script src="_content/Syncfusion.Blazor.Core/scripts/syncfusion-blazor.min.js" type="text/javascript"></script>


If you are using Syncfusion.Blazor Single NuGet, then you need to use the below following script and stylesheet link to get the functionality and style for the component.

 

<link rel='nofollow' href="_content/Syncfusion.Blazor/styles/bootstrap5.css" rel="stylesheet" />

<script  src="_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js"  type="text/javascript"></script>


If you are still experiencing the same issue after trying the above solutions, we kindly request that you provide us with additional details about the issue, as outlined below:


  1. Are you experiencing the issue in a specific scenario?
  2. Could you please share a runnable issue reproducing sample that we can use to reproduce the issue on our end and investigate the problem further?
  3. Please provide step-by-step replication instructions for the issue you are experiencing.
  4. If possible, please provide a video illustration of the issue to help us better understand the problem.


By providing us with this additional information, we can validate the issue further and provide you with a more accurate solution.



Loader.
Up arrow icon