Tag Info

Hot answers tagged

5

Instead of exporting as a template, rather use the Sharepoint Backup Tools. Browse to http://YOURCENTRALADMINURL:portnr/backups.aspx Click "Export a site or list" Select the List you want to backup. Import into correct location using : Import-SPWeb http://site -Path export.cmp


5

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 ...


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 ...


4

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 ...


3

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


3

You're almost there, the next step is to create a new list choose the template you saved after list created delete the template from the library. Full tutorial (this is talking about between SharePoint servers, but its the same process between siets) Other ways include If it a simple list you can perhaps use the DataSheet view to copy and paste the ...


3

Please check these technet documents Export list: http://technet.microsoft.com/en-us/library/ee428301.aspx Import list: http://technet.microsoft.com/en-us/library/ee428322.aspx Sample Export: Export-SPWeb -Identity http://site -Path c:\export.cmp -IncludeUserSecurity -IncludeVersions All -ItemUrl /lists/mylistname Sample Import (path to subsite, list ...


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

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 ...


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

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 ...


3

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 ...


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

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


2

Uploading 500GB of data into a 250GB database is going to be problematic for obvious reasons. There are a number of third party utilities available to do this, but the most affordable way is to go to a Document Library and choose to open it in Windows Explorer. I would then recommend to move (not copy) files in batches to SharePoint for the following ...


2

Farm Solutions can only be added via the command line or object model, only sandboxed solutions can be uploaded and deployed through the GUI. Why this is, is anyone's guess, really - unless someone has a good answer. (ref: http://msdn.microsoft.com/en-us/library/aa544500.aspx and http://technet.microsoft.com/en-us/library/cc262995.aspx)


2

Associate your workflow with a content type. Extend Mike's suggestion by creating a new list instance which will already have the content type associated with it. As your workflow is associated to the content type you will have the workflow available in the list.


2

I'm assuming you're looking for a reusable method that's got some automation. I'd imagine you could use an Excel macro to call the lists web service, prompt the user to select a template, create that list, then push the data into the list. You may need to store the list structure CAML in the macro vs. in a template file, as I'm not positive if lists ...


2

You could write a simple console application that would do it for you through the SharePoint Object Model. You could also do it with PowerShell.


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 ...


2

Did you use Get-SPFeature to verify that the feature was successfully deactivated before re-exporting? Maybe you need to use the -force parameter on Disable-SPFeature. Also, make sure the -url parameter is for the site and not the site collection, since this feature is web scoped.


2

Solution SharePoint People Picker works directly environments like above. To be more specific if forests/domains are 2-Way trusted. So if you have One-way:outgoing trusts like my case you have to configure People Picker separately. This command on EVERY WFE server! stsadm –o setapppassword –password <password> Value of password could be any ...


2

I would either backup the whole site collection (backup/restore) and use the overwrite switch, or if you must you export/import, delete the test site and then create a new blank site. Then you can import your data into the blank site and there shouldn't be any problems.


2

Luke, First of all never change anything inside a SharePoint Content Database. Concerning the "0" number of site collections it may happen due to permissions and conflict of internal SID for the dbo user for a restored content database. Here is what can you do and it should work just fine provided that your content database is not exceeding 15GB. Take ...


2

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 ...


2

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. ...


2

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 ...


2

I do not know how to define non-excel datatypes in Excel. And it is not possible to change a datatype in SharePoint after column is created, but this workaround may help you: Create a new column with the desired data type in the SharePoint list. Position it next to your wrongly typed data column. Open the list with the Edit in DataSheet option (located in ...


2

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 ...



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