Asp – Problem with DataAnnotations and MVC1: Required attribute is ignoring the ErrorMessage property

asp.net-mvcdata-annotationsvalidation

I'm validating the properties of a linq to sql entity using DataAnnotations, the properties are validating fine but the Required[ErrorMessage="error message"] ErrorMessage attribute is being ignored and instead I'm getting the default error message.

Here's the code I have so far:

    [DisplayName("Nombre")]
    [Required( ErrorMessage = "Este campo es requerido" )]
    public string Name
    {
        get;
        set;
    }

    [Required( ErrorMessage = "Este campo es requerido" )]
    [Range( 0, 1000000, ErrorMessage = "Debe insertar un valor entre {1} y 1,000,000" )]
    public decimal Maximum
    {
        get;
        set;
    }

    [Required( ErrorMessage = "Este campo es requerido" )]
    [Range( 0, 100, ErrorMessage = "Debe insertar un valor entre {1} y {2}" )]
    public byte Periods
    {
        get;
        set;
    }

Best Answer

Check to see if it's a namespace issue. I just fixed my problem by putting the Metadata "buddy" class into the same namespace as the Model L2S class, even though I thought I had everything referenced properly. I wanted to put the metadata classes into their own namespace for organizational purposes but it didn't seem to like that. FWIW, I'm running on .net 3.5, VS 2008, MVC 2 RC.

Related Solutions

Asp.net-mvc – ErrorMessage is ignored in DataAnnotations DataType Attribute

In MVC1 DataType attribute does not do what you'd expect, it looks like it does not in MVC2 either. Your best call is to have a string property representing the date, check it's validity there.

Here's a small excerpt from a project (using DataAnnotations and xVal):

private List<ErrorInfo> _errors;
        private List<ErrorInfo> Errors
        {
            get
            {
                if (_errors == null)
                    _errors = new List<ErrorInfo>();
                return _errors;
            }
            //set { _errors = value; }
        }

private string _startDateTimeString;

        /// <summary>
        /// A string reprsentation of the StartDateTime, used for validation purposes in the views.
        /// </summary>
        /// <remarks>
        /// If the user passes something like 45/45/80 it would be a valid mm/dd/yy format, but an invalid date,
        /// which would cause an InvalidOperationException to be thrown by UpdateModel(). By assigning dates to string properties
        /// we can check not only the format, but the actual validity of dates.
        /// </remarks>
        public string StartDateTimeString
        {
            get
            {
                return _startDateTimeString;
            }
            set
            {
                // Check whether the start date passed from the controller is a valid date.
                DateTime startDateTime;
                bool validStartDate = DateTime.TryParse(value, out startDateTime);
                if (validStartDate)
                {
                    StartDateTime = startDateTime;
                }
                else
                {
                    Errors.Add(new ErrorInfo("StartDateTime", "Provide a valid date for the start time."));
                }

                _startDateTimeString = value;
            }
        }

        partial void OnValidate(ChangeAction action)
        {
            if (action != ChangeAction.Delete)
            {
                Errors.AddRange(DataAnnotationsValidationRunner.GetErrors(this));

                if (StartDateTimeString != null)
                {
                    DateTime startDateTime;
                    if (!DateTime.TryParse(StartDateTimeString, out startDateTime))
                    {
                        Errors.Add(new ErrorInfo("StartDateTime", "Provide a valid date for the start time."));
                    }
                }

                if (Errors.Any())
                    throw new RulesException(Errors);
            }
        }
    }

It makes sense to have the check in both places in our project, but I just want to show you a concept.

Asp – MVC2 Validation – “A value is required”

I've had this problem too, and I discovered it was actually nothing to do with the optional fields. It was because I had an auto-generating primary key column for the entity, called 'Id'. MVC2 automatically checked for a value for this, and obviously there wasn't one as it was being auto-generated.

There's an easy way to fix this is to rename the column to BarcodeId etc, rather than just Id. I gave a better explanation here: http://www.ediblecode.com/post/A-value-is-required-with-ASPNET-MVC-2.aspx

That explanation is all assuming you're using LINQ...

Best Answer

Related Solutions

Asp.net-mvc – ErrorMessage is ignored in DataAnnotations DataType Attribute

Asp – MVC2 Validation – “A value is required”

Related Topic