Skip to main content

FatalError: Value cannot be null. Parameter name: g


The problem is that it is not sufficient to specify Type="User" for these fields (the UI equivalent field type is "Person or Group"). You also need to add an attribute List="UserInfo" to get it to work properly. If you miss this out it will fail at the import step if the field has been populated. If the field is left blank the import will work, which can give rise to confusing behaviour when you are trying to diagnose the problem.


Change Manifest.xml file

So your field definition should look something like this:



Now your import will work

Comments

Popular posts from this blog

Ghosting and Unghosting

Ghosting means process of requesting an uncustomized page instance by using a page template loaded into memory from the file system of the front-end Web server. These Ghosted pages are pulled from the cache at runtime and therefore it will increase the scalability from the system. All uncustomized pages are reused across all the sites and there is no unnecessary data storage or retrieval. Ghosting eliminates the need to transfer the contents of a page definition file from the SQL Server computer with the content database to the front-end Web server computer For example, the default home page is a ghosted page. Any web part pages created via New Web Part Page user interface also ghosted. Unghosting means that the site has been customized. When you customize a site in SharePoint Designer, or you add custom fields to a Document Library, or create sites using that template; then the changes that you made are stored in the database as a difference and that is referred to as Unghost...