The given key was not present in the dictionary - issue when opening a SharePoint List

Whenever you encounter this error "The given key was not present in the dictionary" when opening a SharePoint List or when creating a new item on a list, am sure you are led to search your own code to see if you have wrongly referenced any non present field...

But, that is not the case unfortunately!

This mostly comes in lists where you have Custom Fields (inherited from SPField) created.

You will have to check if you have the corresponding fldtypes xml created and placed in the template/xml folder apart from placing the .ascx file in the ControlTemplates folder.

So in your case, you will mostly not have placed the xml file and that is what will be causing this issue!

Comments

  1. Steven SummoneJuly 12, 2011 at 3:35 PM

    That worked. Your check point me in the right place we were referencing the wrong custom field type! Thats what happen when you follow tutorials with typo's!!!

    ReplyDelete
  2. Karthick SSeptember 26, 2011 at 9:25 PM

    (a little late) Glad to know! :)

    ReplyDelete
  3. GiovaniFebruary 27, 2013 at 10:13 AM

    Hi Karthick, I've encountered this kind of problem, but only for a few users. Is it possible that this happens only to some users? Any hints to troubleshoot this condition?

    Thank you so much in advance...

    ReplyDelete
  4. sHaDOwJune 13, 2013 at 12:34 PM

    Hi Karthick, I've encountered same problem like Giovani, which only few users get the error. Appreciate if you would provide us solution.

    Thanks!

    ReplyDelete

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp
Read more

NAV 2009 Issues in Role Tailored Client

Image
Role tailored client issue Changing stored procedure to 64 bit in NAV 2009 Did install Dynamics NAV 2009 on windows 2008 64 bit / Windows 7 65 bit. When trying to connect to the database in classic client I got this error. The following SQL server error or errors occurred: 17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database\xp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100). SQL: INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)} The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version. 1. Stop SQL server 2. Copy \\vedfssrv01\DynamicsNAV2009\W1\DVD\Sql_esp\x64\ xp_ndo_x64.dll to C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database 3. Rename existing xp_ndo.dll to xp_ndo_x32.dll 4. Rename xp
Read more