Is there a way to export/Connect TFS (On-Prem) work items to SharePoint online or on-prem list? I need those work Items in SharePoint Task list. Is it possible to set the connection? or another option would be exporting TFS work items on daily basis to Excel sheet and then use that excel sheet synced with SharePoint list? In our organization TFS has been setup on separate server and SharePoint on-prem is on another server.
You can have try below options to export tfs workitems to sharePoint.
1, Connect Your TFS project to Excel first. See the document Connect Azure DevOps project to Excel for detailed information
After you have connected your TFS project to Excel, Import workitems to excel. You might need to create custom queries to query your workitems in TFS.
2, After you have imported the workitems to Excel. Go the Design tab and Click Export to export to share point list.
You can also export the TFS work items to Excel sheet and upload to sharepoint list.
1, Create queries to query the workitem in TFS and export to csv file
2, Import workitems csv file to sharepoint via Import Spreadsheet web part.
Go to sharepoint-->Click gear icon --> Add an app-->search for Import Spreadsheet
See this blog for more information.
Related
I need to GET data from SharePoint Server 2019 (On-premise) list and then I need to add that data to the SharePoint Online list using CSOM.
I have found the below link to get data from SharePoint Server (On-premise) list.
https://www.c-sharpcorner.com/article/sharepoint-client-object-modal-csom/
I have found below link to add data to SharePoint Online list.
https://www.c-sharpcorner.com/blogs/create-a-list-item-in-sharepoint-using-csomannouncement-list
Is that correct way or do I need prefer another way?
Thanks
If you just need list data without any version history or created/modified user and time stamps - you can export the SharePoint on-premise list to excel and use this excel file to create/import a new list in SharePoint Online.
Other options are to
Use Microsoft's "SharePoint Migration Tool" to migrate content - this is a free tool provided by Microsoft - https://learn.microsoft.com/en-us/sharepointmigration/introducing-the-sharepoint-migration-tool
use CSOM code in a VS application as per the links you have - note that you don't need to create 2 separate applications for it, just create one app and create separate instances of the ClientContext for SP on-prem and SP online
use PnP PowerShell to get all list items and then loop over each item and create each item in target SPO site OR use SharePoint Powershell module to do the same. Here is an example of a script that migrates documents but with some minor modification you can get it to work with list data - https://github.com/alimughalx/CopySharePointFilesWithMetaDataAndVersionHistory
I am trying to use "Publish in Access Services" with a Sharepoint 2007 server. The thing is, I have a problem where it tells me that I can't do that thanks to the "UserInfo" table that happens to be a reserved name. What can I do to correct this? Is there a way of changing the table name or is there some other way?
I was not aware that you can publish to SharePoint 2007. However the terminology somewhat changed. And there is a significant difference between SharePoint 2007 and 2010 when you use the term "publish".
However, ignoring all of the above, one thing is to simply delete the table (or make a copy). You can then publish your database. At that point you then LINK to the UserInfo table that is available for all published databases (regardless of the new publishing that Access 2010 has that allows you to create Access form that run in an web browser.
what do you think is the best way to display items from some Custom List (on sharepoint 2010) to completely different portal on SharePoint 2007 with minimum or not at all programming?
I tried with RSS and that is not what I need, so Am now stuck with IFRAME pointing some custom page on sp2010 that shows list items.
Under SharePoint 2007, you can try tu use the BDC feature (known as Business Connectivity Services(BCS) with SharePoint 2010).
It provides the ability to SharePoint 2007 to consume external datas like SAP. It is describe in msdn with complete tutorial:
Business Data Catalog
In production environment, we have a SharePoint site with some Nintex 2007 workflows. Now we need to replicate the production site for testing purposes.
The target server already had Nintex installed when I restored the SharePoint backup.
Unfortunately, it turned out Nintex license has expired on it so we're a little paralyzed.
The workflows seem to have been moved with the backup, however some workflow steps in Nintex designer show exclamation marks with this tooltip:
queryListActivity1 of type Nintex.Workflow.Activities.QueryListActivity is unrecognized by Nintex Workflow
When I activate Nintex license, how can I ensure that Nintex workflow is deployed correctly? I see the following options:
copy Nintex database to the new server and try hook it up with Nintex instance (how?);
save existing workflows on source server using Nintex Export feature and upload them on target server.
What is the best one, or are there any other options available?
The preferred method is to export your workflow from the Developer License site and then import the workflow in your newly licensed site.
Once you have imported the workflow, simply save and publish.
Be aware that copying workflows between sites doesn't always result in a working result.
For example if your workflow queries a list, the connection to the list is implicitly based on the List unique ID (GUID) on the development server. When you move the workflow to the production server the equivalent list will have a different GUID.
You will often have to open these steps in the editor and re-create the list query (pointing at the right list) to get them to run.
I would be very keen to find a tool that can migrate Nintex workflows and automatically fix up things like site URLs and list GUIDs myself.
I have a SharePoint 2010 web application with one site collection. I want to copy that site collection to a new web application on the same server.
I took a backup and restored it to a new database on the sql server. I then created a new web application with a temporary content database that I removed from the web application. I then added the restored copy of the original web app to the new web application.
The problem is the newly attached content database show 0 site collections, but there is in fact 1 single site.
I guess it has something to do with the id's? I have tried adding the content db both with and without assigning a new ID to the database.
Any idea how one can copy a site collection to a new web application on the same server?
--
Christian
Try using import/export. The main difference between import/export and backup/restore is that import/export generates new Guids.
http://technet.microsoft.com/en-us/library/ee428301.aspx
Use Windows PowerShell to export a site, list, or document library in SharePoint Server
You can use Windows PowerShell to export a site, list, or document library manually or as part of a script that can be run at scheduled intervals.
To export a site, list or document library by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt, type the following command: