Hot answers tagged

11

You can use the below code, Add-PSSnapin microsoft.sharepoint.powershell $web = Get-SPWeb -Identity "<URL of Site>" $list = $web.Lists["List Name"] $AllDuplicates = $list.Items.GetDataTable() | Group-Object title | where {$_.count -gt 1} $count = 1 $max = $AllDuplicates.Count foreach($duplicate in $AllDuplicates) ...


10

Below worked for me: Steps: 1) Open Excel File. 2) Go to ribbon, select DATA and select From Other Sources, and click on From OData Data Feed. 3) In ‘Data Connection Wizard’ form, provide appropriate REST link and click on Next. REST Link format to get Sp Group users: https:// Your SP2013 Site /_api/Web/SiteGroups/GetById(9)/Users 4) In Next form, ...


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


9

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) Site Contents Add App ...


8

Exporting and importing as html will not work in SharePoint as it refers lots of controls and files internally Thee best suggested option would be to open the page in designer and copy the content to target page** but make sure all the those web parts are already in the web part gallery and fully functional. To check all webparts are in the gallery, ...


6

You can map a drive to the List: http://community.office365.com/en-us/forums/154/t/5216.aspx The attachments will be under the Attachments folder.


6

With the script below you can easy export all column in a list a comma seperates file Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue -WarningAction SilentlyContinue | Out-Null $url = "<site url>" $listName = "<list name>" $path ="c:\Columns.csv" $web = Get-SPWeb $url $list = $web.Lists.TryGetList($listName) $list....


6

Edit the page in the browser Inspect the DOM to find the div containing your web part Change the allowexport property to true <div ... webpartid="my-web-part-id" allowexport="false"> becomes <div ... webpartid="my-web-part-id" allowexport="true"> This should enable the 'Export...' option in the context menu for the web part.


5

Why don't you make another personal view with all columns?


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

There is just a subtle difference: Workflows are included when you use the Backup-SPSite cmdlet. If you backup a root web of a site collection the site collection recycle bin will obviously not be included.


5

Backup-SPSite is generally used when you want to replicate the entire site collection (including all subsites) to an existing web application. Export-SPWeb is generally used when you want to replicate just a single subsite to an existing site collection. Also below links are worth to read for other major differences: http://blogs.msdn.com/b/yvan_duhamel/...


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


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

Here is a trick I've tried in your situation: Change your view in SharePoint to only display like Maximum 1000 rows. (use the Limit in the bottom of the view definition screen) Attempt again to export to Excel - this should work without issues (if it doesn't the problem lies elsewhere in your SharePoint and then you should have a look in ULS) Change back ...


4

You mentioned, you were able to export the groups in Excel what method you use for it? Here is method I used. Navigate to the People and Groups tab under Site Settings [Site Settings > People and Groups] Copy the URL of the People and Groups page. Open up your Excel workbook, and click on the Data tab. Click "From Web" and paste the URL from the People and ...


4

You can pipe the output from your command to an .csv file: FileToExecute.ps1 | Out-File C:\output.csv Make sure you in your script file uses Write-Outputand not Write-Host when printing your output.


4

Use the following Command: $spWeb = Get-SPWeb SiteUrl $spWeb.Lists | select Title | Export-CSV c:\Lists.csv


4

If you get an error adding SharePoint DLL which states Could not load file or assembly 'microsoft.sharepoint, Version=12.0.0.0 you can try using this script instead [Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") and you can continue exporting the WSP from your 2007 environment $farm = [microsoft.sharepoint.administration....


4

I found another way to export a web part. There is a hidden page in SharePoint that takes a couple of query strings for the web part Id and the page URL and generates a file with the exported web part. You can get the web part Id from the HTML source of the page. http://yourwebsite.com/_vti_bin/exportwp.aspx?pageurl=http://yourwebsite.com/Pages/...


4

Indeed, as Sergey B. Hizof pointed out in the comment above, the Export-SPWeb and Import-SPWeb PowerShell commands work great to copy sites or lists/libraries to another location. Here's a good explanation (https://technet.microsoft.com/en-us/library/ee428301.aspx ) and here's a good video about it: https://www.youtube.com/watch?v=8WgPeYMd4Ss. There are a ...


4

Suggestion for your second question, Better to use web-hooks instead of remote event receivers. Web hooks support only asynchronous -ed events (like updated, deleted, etc). Assess the requirements in your current farm, if none of the event receivers are fired before the database transaction happens, more precisely synchronous -ing events are not required (...


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 need to define a custom permission level for employees. The easiest way is to copy from one of the default ones. Once you create your permission level uncheck the following option: [] Use Client Integration Features Create a group that has this permission level, and and your users to this group. Hope this helped :) for more information you can ...


3

Had the same problem with two user fields containing texts. Export works fine without them. And the Solution was to add additional Filter to the View! The Filter is on Date Created Field (in my case) > xx and it's set so that all the data that we were displaying before is also shown, the additional Filter does not return any less Results, so the amount of ...


3

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


3

None of the above should be necessary. The "Action" options are dependent on the view used. Open the "Overview" view, click "Actions" and the export option magically appears. There's no way anyone would know this so this is a good example of the bad design / UX that plagues Sharepoint.


3

This could work, but only for a given SPWeb: Get-SPUser -Web http://localhost | ForEach-Object { $_.Id }


3

Making a backup of the site collection is best used when you need to restore it on the same environment It's nearly like a content database backup. Exporting a site collection will allow you to import it on a different environment. It's working in a similar fashion than content deployment jobs. It will include in an environment agnostic way all the assets ...


3

As another option, you can also just put a link on a wiki page or wherever your webpart is, if you want to do it in the browser and not in code: The link would be {siteurl}/_vti_bin/owssvr.dll?CS=109&Using=_layouts/query.iqy&List={GUID of list}&View={GUID of view}&CacheControl=1 Just fill in your siteurl and the 2 GUIDs. Use the encoded ...


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