MaxLength field annotation

Hi there.
I've noticed the following behavior that I think is not by design, so I am mentioning it.
When in SQL Server table the field data type is nvarchar(MAX), the annotation in the exported poco class for that field is  [MaxLength] 
Putting a field like that bound to a textbox in a column of a sfGrid (at least there), sets the maxlength of the validation rules to -1, so you cannot edit anything in it.
If there is a field of nvarchar(10) then 
[MaxLength(10)] is annotated and everything works ok.



3 Replies

RS Renjith Singh Rajendran Syncfusion Team May 2, 2022 01:22 PM UTC

Hi Rigakis,


Greetings from Syncfusion support.


We are checking this reported scenario from our side. We will update you further details within two business days on or before May 5, 2022.


Until then we appreciate your patience.


Regards,

Renjith R



RS Renjith Singh Rajendran Syncfusion Team May 5, 2022 04:01 PM UTC

Hi Rigakis,


We are facing difficulties in further validating this scenario from our side. We will update you further details within two business days.


Until then we appreciate your patience.


Regards,

Renjith R



RS Renjith Singh Rajendran Syncfusion Team May 10, 2022 11:55 AM UTC

Hi Rigakis,


We have confirmed this as an issue and logged the defect report “MaxLength validation attribute sets validation rules Length to -1”  for the same. Thank you for taking time to report this issue and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle) and including the fix in our upcoming weekly patch release which is expected to be rolled out on May 31, 2022.


You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.        

https://www.syncfusion.com/feedback/34782/maxlength-validation-attribute-sets-validation-rules-length-to-1


Regards,

Renjith R


Loader.
Up arrow icon