Simplex Explanation: “Praedae pretium non est in parte.”

UPDATE: An anonymous poster left a great comment about internal names. Be sure to read it.

Cum operantes cum eventus receptatores et Codicis references SharePoint album items per obiectum exemplar, Saepe erroribus quod generare hoc error ad runtime:

Error oneratisque et currit eventus susceptor Conchango.xyzzyEventReceiver in xyzzy, Version = 1.0.0.0, Culturae = neutra, PublicKeyToken = 0dc50a750396c3ac. Additional information is below. : Value does not fall within the expected range.

I think this is a fairly generic error that is potentially caused many different ways. Autem, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", Ego oportet respicere quasi hoc in eventus accipientis:

properties.ListItem["Due Date"]

Cum misspell vel uti iniuriam causa cum indiciunt agro, SharePoint generates the above mentioned runtime error. Verbigratia, hoc est iniuriam:

properties.ListItem["Debitum Date"]

</finem>

Scribet ad mea blog.

Technorati Tags:

Cogitavi in ​​unum "Simplex Explanation: “Praedae pretium non est in parte.”

  1. Sanjaykuma​r Patel

    I agree with paul but i also want to add something for this exception.
    Sometime the Field Name is different than the Field Internal Name in the list so trying to access the field using Field Name in the object model gives us the above exception. To resolve this problem always try to access the fields using their Internal Names.
    How can you find the internal Names of the Fields?
    1) Go To Sharepoint List. Go to New | New Item.
    2) New Item form will be displayed. Right click on the form and click on View Source. Search for the Field Internal Name in the opened HTML code. You will find the Field Internal Name along with Field Name.

Aliquam

Tua inscriptio electronica non editis. Velit sunt insignis *