Tag Info

New answers tagged

0

Once you change the rules you have to run a full crawl, back in 2007 sometimes two full crawls.


0

No, the easiest way I think would be to manually bring over the attachments, it may be possible to capture all the attachments using SharePoint Designer 2007, then importing them using SharePoint Designer 2013.


0

Are you familiar with powershell? You could do it with powershell. Otherwise, you could export the data in Excel format. Join them manually. And import the data back to SharePoint.


0

Either the user account has not been synchronized yet or You have to click on "No exact match found" in order to view more.


2

If i was to move list elements and keep their version history etc. i would take a look at the homepage of Sharegate in order to download a trial so that You can evaluate it. I have used it and i think it was very easy to use and the elements i moved/copied kept its properties. The gui looks like this:


0

You add a custom style sheet to you page using a content editor web part or customize the master page. You will find some CSS snippet on my blog post on how to turn summary link web part into an accordion. What you need to customize is basically the groupheader: .groupheader{ background-color: #0072C6; color: white; font-size: 140%; ...


0

There is a path in the "C:\ProgramData\Metalogix" in which the XML file is "EnvironmentSettings" responsible for all thresholds and overall performance. so you need to update that to make it work. Pls see the detailed note from the metalogix documentation: For large lists, we recommend starting with batch sizes of between 100 to 200 items. For smaller or ...


0

I just created a new folder for each reference, so user can upload same file but in different folders.


0

Under Navigation in site settings you should be able to add a new category and the necessary links.


3

CSOM: will work in SP online, SP 2010, 2013 and most probably 2016 REST: will work in SP online, SP 2010, 2013 and most probably 2016 OOTB Web service: will work in SP 2007, 2010, 2013 but maybe not in 2016 (and maybe not with future versions of SP online) Creating your own Web service with SOM: will work in SP 2007, 2010, 2013 and 2016


0

I think, SOM is better option for doing complex operation in SharePoint. Becuase if you use REST/ CSOM, internally it will call some service which will get some time to execute that query than SOM on the server. so better to use SOM which will directly hit the server for operation.


5

CSOM and REST was introduced in SP 2010 so you wont be able to use that with 2007. SOM is an option but requires that your code runs on the servers of each farm. SharePoint Web Services will be your best option if you need to support all three versions with the same code from client computers. Lists Web Service (/_vti_bin/Lists.asmx) for getting libraries ...


1

The client object model was created in 2010. CSOM did not exist in 2007. So I would recommend the server object model.


1

You can use any of these tools: Metalogix Avepoint Sharegate Metavis There are other tools as well. With the explorer view, you can not migrate metadata.


0

You can not add any category here by NO-Code (OOB) way. Now, if you are OK with creating farm level solution, then you have create custom application page and mimic this site content page plus add your category and replace existing site content page on run-time. Here is the reference on, how to create custom application page. Creating an Application Page ...


0

There is no "Search Tool" for SharePoint 2007, but there is a built-in Search Engine that has gotten better with each successive version of SharePoint (2010 and 2013). For example, performance and scale have improved significantly.


0

Because you lost the whole databases, so that's why you able to recover it at single point of time. You should perform the full testing on your farm. make sure everything is working. yes, their are many actions which stored in the config DB i.e creation of site collections. As user action can change the stuff in the config DB so that's not supported to ...


1

Tinkering around to fix it in the database is not recommended or supported. The old stand by is to navigate to your web part page and add ?contents=1 to the end of the URL. Here you can delete the corrupt web part. Then go back to your web part page and add it back. You can always try exporting the web part from the site it is working in and importing it ...



Top 50 recent answers are included