Hot answers tagged

11

I found a way to do it finally via "The Internet". Here is what worked for me. Sub ImportSharePointList() Dim objMyList As ListObject Dim objWksheet As Worksheet Dim strSPServer As String Const SERVER As String = "mysite:8003/sites/the-sharepoint-thing/" Const LISTNAME As String = "{D1F1C2ED-81BA-41CC-A698-XXXXXXXXXXXX}" Const ...


10

From my experience, this is not possible through the SharePoint Dataview Sheet View. This is a new feature in 2010 and although super delicious and powerful, it still has a lot of issues that need to be resolved before it will be as powerful as it can be - in 2013, Microsoft has made improvements as per this article from MSDN To answer your question - in ...


10

First, you should specify what's the type of risk that you expect when you try to export and import a library from one farm to another with different build number Will the cmdlet be worked and executed properly? Yes, the cmdlet will be worked and executed properly. regardless the source farm build number is identical or greater or lower than the ...


8

You can create a Site Template to create the copy. Go to the list settings of the list (ListA) Click save list template on the right list of links Save the template as something Click save list content if you want the same content in the new list Go to the All Site Content page and create a new list based on the saved template (ListB) This will create an ...


7

I stumbled across a way to fix this today. Under "Versioning Settings" there is a setting called "Require documents to be checked out before they can be edited" By default, in all my libraries, I have this set to "Yes" I discovered if I change that to "No" my datasheet views become read/write. Odd? Very. But it does seem to work. Incidentially, I ...


7

I changed the text type from 'Enhanced Rich Text' to 'Rich text' in the column setting(through List setting) from SharePoint and it worked for me.


5

After migration lookup columns lost relations because list GUIDs they are using are different. This cannot be avoided and this is main disadvantage of using export/import based migration. Here you can find known issues when using import/export: Migration Ugliness - SharePoint 2010 Content Migration Limitations


5

I had the same issue. There is another way to solve this problem with editing Multiple lines of text field in DataSheet(Access) view: Changing Versioning Settings for lists and libraries is useless. You should change field settings in SharePoint Designer. Open site- choose list, then right click on Multiple Line Field (with editing problem) and choose ...


5

Using Export and Import, you can migrate list from SP 2010 to SP 2013 but you have to make some manual changes. Export the list from SharePoint 2010 using either the Central Administration or PowerShell (Export-SPWeb). In the Central Administration, go to Backup and Restore > Export a site or list. Choose your list, and click Start Export Copy the exported ...


5

You can even increase the maximum size of list templates up to 500 MB (I don't know if it is large enough for you) either via stsadm: stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 524288000 or via PowerShell as well: $webservice = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $webservice....


5

When you export a site / web, it created one or multiple CMP files depend upon the Size of Site and value of FileMaxSize By default, the .cmp files are limited to 24 MB in size, although you can change this value using the FileMaxSize property. If set to zero, the value resets to the default. When site data exceeds the specified limit, site data is ...


4

Technically, you have foundation in both cases. Server "bolts" onto foundation. These errors are common. For the sake of stating the obvious, you need to ensure the account you are using are properly privileged. Open the site you are importing too and ensure the account you are using is a site collection administrator. Additionally ensure you are running ...


4

Since you removed DocAve already, the solutions bits were probably removed but it appears they were not un-registered with SharePoint. You need to ensure all the DocAve solution features are unregistered and removed from the farm. You can use CA, Powershell, or a tool like feature admin from codeplex to assist: http://featureadmin.codeplex.com/ Then re-...


4

SPExportObject/SPImportObject can be used to migrate the list item, but only issue that you need to take care is if you export an item from a database (e.g. a list) without exporting it's parent, then the exported item will become orphaned in the package. A package can contain multiple different orphaned objects (e.g. if you export multiple different lists ...


4

No it is still not available. You will need to create a new column as a person/group field and then in Quick Edit view, copy over the data. Then delete your single line of text column.


4

The key points are recognizing the column types and formatting the data appropriately in Excel before the attempting the import. Certain column types are not able to be imported in this way, such as the Multi-line Enhanced Text. Let me break it down for you. :) Column Types Must be formatted as follows: -COLUMN- | -FORMAT / COMMENT- Single ...


3

This is a response I posted elsewhere (the links below contain code segments. Export/Import SPWeb works with site, list, or document libraries) - The quickest way would be to export the site/list/document library using the Export-SPWeb PowerShell command. Use Import-SPWeb for importing the file package (it can also use optional compression. See the -Path ...


3

Here is the quick summary of upgrade: Verify the hardware requirements first. Try to back up the database from SharePoint 2007 using the SQL Server Management studio. Move the backup file to SharePoint 2010 environment and restore the backup file in SQL Server in a New Database (say DB1_2010) Before you attach the DB to web app, run the following powershell:...


3

Backup-SPSite will move all your data and rights and create corresponding records in the content DB. Import-Export is not so good way for you, you can use it only for web, not for site collection, but it also will move all your data and security, if you will set corresponding flags, it has a lot of options. Previous approach is also possible, you can attach ...


3

The way I would do this is to move the site collection into its own content database. Then copy that database and attach it to the new farm. In Central Admin add a new content database to the web application Use the Move-SPSite CMDLET in PowerShell to move the site collection to the new content database Make a SQL backup of the content database Restore the ...


3

I think that using the BCS to connect to your database table would be the most effective way. Where that table lives is up to you. You could move it to the SharePoint server or another SQL server in order to remove the old sql server from the network. If the BCS is not an option, then you will either need to import the data into a SharePoint list or ...


3

I have tested your code and found the problem was with the files being created during exported were not cleaned up properly on the local disk. I implemented the files deletion logic to ensure Export and Import works fine. Note, I ran the Export and Import with and without FileCompression and both are working fine. I ran my test on two Picture libraries. ...


3

You can't foced special data types when importing or change type of existing columns. Your best option is probably to: Create a new column for the name with the right type Create a Datasheet View for the list Select all the values in the old name column Copy Click the new name column in the first item Paste This requires that all the names are in the ...


3

Not much info to go buy, but if you imported a custom web part to another SharePoint site, it will not work! The reason is that the assembly behind the web part is not allowed to run on that site by the safe mode parser (SafeControls in web.config). Try and install the web part solution in the new SharePoint solution and see if this solves the problem!


3

I'd recommend using SharePoint Manager to check everything's where it should be.


3

You can open the list in datasheet view (or create a datasheet view) and just copy & paste your excel sheet rows into the list. Just be careful that the columns are in the same order as in your sheet. If this is not possible, you need to use script or code. The problem here is to use the right format for your fields. Example: (src: http://social.technet....


3

SharePoint won't be able to create a list from a spreadsheet in that format. Nor will you be able to copy and paste it into quick edit mode. (Theoretically you would be able to copy and paste it, but it would not work as intended.) Luckily there is an option to rotate data in Excel so you should be able to correct the format and then import it into ...


3

looks like you have 29 documents that are checked out. Make sure that all documents are checked in first. when performing a export-spweb it does it on the checked in version. if it doesn't have one then its ignored.


3

This issue occurs in case you are using -NoFileCompression parameter in the Export-SPWeb cmdlet. In this case, the cmdlet will export the files with no compression in a Folder instead of one file filename.cmp as shown below And if you tried to import it, you will get The file c:\16.cmp does not exist because it's not file, it's a folder called 16.cmp So ...


2

Following on James Love's answer: For Sharepoint 2003, you can copy/paste, but you must be careful about how you do it. (not sure how this may apply to more current versions) After copying the data in your excel spreadsheet, go to your Sharepoint list and single-click on your left-most editable cell in the 'new row' at the bottom (so that you're selecting ...


Only top voted, non community-wiki answers of a minimum length are eligible