Showing posts with label JS. Show all posts
Showing posts with label JS. Show all posts
Friday, March 15, 2019
Wednesday, February 18, 2015
SharePoint Tools: A new CAML Query Designer
Praveen Battula has released a new tool on his blog to work with CAML Queries. Not only you can export the plain CAML Query it self, the tool lets you generate code for C#, JavaScript, WebServices and PowerShell as well.
Have a look at his blog:
http://praveenbattula.blogspot.de/2015/02/download-caml-query-designer.html
Have a look at his blog:
http://praveenbattula.blogspot.de/2015/02/download-caml-query-designer.html
Labels:
Administration,
CAML,
Code Snippet,
Development,
English,
Entwicklung,
JavaScript,
JS,
Powershell,
Sharepoint,
Tool
Thursday, July 31, 2014
Creating a bookshelf with the Content Query Webpart in SharePoint
A lot of information these days comes in form of an eBook or similar format like a simple PDF. In SharePoint the easiest way to present this information to the user is as a list. For the more ambitious there is the metadata navigation, which brings a lot of beauty for handling list content. I will use a more sophisticated approach via the Content Query Webpart (CQWP) to present the information like books on the bookshelf.
Before we can start, we’ll need to step back for a moment and think about the data structure we’ll need in order to support the view we are creating here. There are a few questions you must ask yourself:
In my case, I have more documents other than just eBooks. I’ve decided to keep all documents in a single document library and to identify the documents by their content type. Therefore, one of the first steps will be to create the library, the columns and the content type.
Preparation
Before we can start, we’ll need to step back for a moment and think about the data structure we’ll need in order to support the view we are creating here. There are a few questions you must ask yourself:
- Where and in which document library will you store you eBooks?
- Will you mix different content types in that document library or will you create a new library for every document type?
In my case, I have more documents other than just eBooks. I’ve decided to keep all documents in a single document library and to identify the documents by their content type. Therefore, one of the first steps will be to create the library, the columns and the content type.
This post is
Labels:
CCS,
CQWP,
Development,
E-book. ebook,
ebooks,
English,
Entwicklung,
HTML,
Hypertext,
JavaScript,
JS,
No Code,
NoCode,
Office365,
Sharepoint,
Sharepoint 2007,
Sharepoint 2010,
Sharepoint 2013,
Stylesheet,
Webdesign
Subscribe to:
Posts (Atom)
Featured Post
How are Microsoft Search quota consumed?
With Office 365 Search, Microsoft has created a central entry point for the modern workplace. In one convenient spot, users can access all ...
