Snippet to render Attachments Row in SharePoint 2010 Custom Edit Form
Snippet to render Attachments Row in SharePoint 2010 Custom Edit Form
Here is the snippet of how to Create Folder in Document Library programmatically using the Object Model. It can be used in console applications for loading documents or timer-jobs.
I have copied exported site to another farm and tried to restore. After executing of cmd-let for restoring spweb (Import-SPWeb -Identity http://spdev/forums/ -Path D:\Backups\forums.bak) I've got an error:
Import-SPWeb : Could not find file 'C:\Users\spadmin\AppData\
SPWeb object has 2 different properties for work with groups. There are Grops and SiteGroups. Inspite of the fact that they look very similar, they are different.
Information about files in document libraries is strored in the table "AllDocs" of Site's content database. Of course, Microsoft doesn't allow to make queries to SharePoint databases directly. But I can't but agree with inserts and updates are not allowed, but select query in the worst case will make just some locks in database. So I guess that in some cases it's much better to execute select query than powershell script.
Once I had to add about 3 thousand users to SharePoint group. Usually when I have to add about 100 users, I use Excel function 'CONCATENATE' to add user login and ";" separator to generate a list of users. And then I manually enter them. But 3 thousand users – it's too much for manual.
The red star in SharePoint form for required fields can be written as <span> control with class "ms-formvalidation":
<span class="ms-formvalidation"> *</span>
I'm preparing to install Microsoft SharePoint Server 2016 to machines in the VLAN without access to Internet. All the distibutives of SharePoint ask for prerequisites which must be downloaded and installed. Unfortunately, you should get them by yourself. If you have internet access, than it's not a problem. But if you don't have it?
While removing Site Content Type you got the error that "The content type "My Content Type" is part of an application feature". The fix is rather easy and simple.
Managed metadata is very good and powerful tool in SharePoint. But it has some not very comfortable specialties during migration data from one farm to another, for example, from test environment to productive. You can export your managed metadata from one site and import it into another one. But here's the problem that each termset and term has its own GUID. After you import managed data into the new farm, new GUID’s will be assigned to managed data items.