Tuesday, November 29, 2016

Building CAML query with AND and Order by?

Building CAML query with AND and Order by?
For Example:


<OrderBy>
<FieldRef Name="ID" Ascending="TRUE"/>
</OrderBy>
<Where>
 <And>
  <Eq>
   <FieldRef Name="HomeType"/><Value Type="Choice">Condo</Value>
  </Eq>
  <Eq>
   <FieldRef Name="LastName"/><Value Type="Text">Doe</Value>
  </Eq>
 </And>
</Where>
Read more »
By at No comments:

How to download the U2U CAML query Builder for SharePoint 2013?

CAML Query ,
How to download the U2U CAML query Builder for SharePoint 2013?
CAML Designer

 The one that works is this URL: http://camldesigner.blob.core.windows.net/offlinepackage/CamlDesigner2013.zip

 The link comes from Karine Bosch's Blog. CAML Designer is the successor of CAML Builder, and from experience I can tell you this tool is much better and accurate. I've tried the both.

 Edit: Looks like the CAML Designer now is a subscription application, but it is present on GitHub. https://github.com/chrisdee/Tools/tree/master/SharePoint/CamlDesigner

 CAML Builder

 But if you want the previous tool, the page to turn to is http://www.u2u.be/Software where you have the download at http://www.u2u.be/Downloads/U2U.SharePoint.CQB2010.zip which contains the wsp.

 The CamlBuilderSetup.msi-file is located here: https://docs.google.com/file/d/0B1H-kV-5gwStUlF1OEdjWWJZNXc/edit?pli=1


U2U CAML Query Builder is now available again and updated for SharePoint 2013:

 http://www.u2u.be/Software
Read more »
By at No comments:
Labels:

Sharepoint service applications and Proxy Usage - Purpose of each component

Sharepoint service applications and Proxy Usage - Purpose of each component
  • Service
    This is the actual service, with its own engine, data storage, and infrastructure. It can be hosted on a specific server of the farm, or it can be a third-pary service. For example, this could be an external ERP, or it can be a software component that will be installed in the farm.

  • Service Instance
    Represents a single instance of the service, running on a server of the farm. There can be multiple instances of a service running on multiple application servers. The service application architecture gives you the ability to provide services in a scalable, multi-server configuration, with a load balancer to dispatch requests to the servers.
  • Service Application
    This is a logical layer that makes the back-end infrastructure available to the farm. Whenever you use a service application, you do not care about where and how it is exposed. You do not care about the number and location of the physical service instances. You simply access the service application as a logical service.
  • Service Application Proxy
    This is the proxy that virtualizes the access to the service application. In general, it is used on front-end servers of the farm and allows accessing the service application transparently and independently from its actual location.
  • Service Consumer
    This is a page, a Web Part, or whatever else that runs on a server of the farm, consuming a service application through its service application proxy.
Read more »
By at No comments:

Tuesday, November 22, 2016

SharePoint Interview Question & answers Q3

SharePoint Interview Question & answers Q3
What are the different types of elements used in CAML?

  • CAML allows the developers to construct and display the data using the rendering process and other processes. CAML consists of different types of elements to represent the lists and the sites by using some predefined style.

1. Data definition elements : It is used to define the lists and the sites by using the XML tags with the same style. The code will look like this:<Fields><Field Type="Counter" Name="ID"/>// insert other statements here</Fields>
2. Data rendering elements : CAML also allows the generation of HTML based sets that use the tags like the loops that are used to loop around a given condition. The example is given below that shows the drop down menu with choices:<ForEach Select="CHOICES/CHOICE"><HTML>fld.AddChoice(</HTML><ScriptQuote><Property Select="."/></ScriptQuote><HTML>, </HTML><HTML>);</HTML></ForEach>
Why are event receivers used in Sharepoint?
Event receivers are the classes that inherit the properties of the SpItemEventReciever and SPListEventReciever base class.

Both of these classes use the abstract base class that is SPEventRecieverBase.

This base class provide the option to respond to the event of the occurring of the sharepoint. It keeps the function of adding and deleting of an item. The event receivers respond to the requests that come when an event is performed by the user. For example, if there a cancel of an action is performed then the request is received by the event receiver and the actions will be taken according the request received. The event receivers are used to store the input of the action that is been taken by the user by performing an action on the button or any other action on the site.
What is the function of a content type in sharepoint?
Content type consists of the information or act as a blueprint that has the reusability properties. This feature is included in the sharepoint to define the Meta information like metadata and its associated information and properties. It acts like an extension to the sharepoint program and consists of the list of the types that are present. It is also used to make the list portable for use throughout the instance of the type by using the instantiation process. It is used to set the content type as location independent. Multiple content types can exist together in one document library and the setting of the document library becomes enabled. It will have access to the listform pages, workflows, templates and custom written functionality. Content type is important to all the deciding of the diffirent types of contents that are used in sharepoint.
What are the different components that are used for single as well as multiple servers?
Sharepoint consists of many different components of the server that can perform many tasks at a time. The list that is given below consists of the components that are used by the sharepoint and it is as follow:


  •  Sharepoint foundation : This is the program that provides the communication, collaboration and management of the content between the server systems.
  • Sharepoint server : This consists of the software that provides the material for both the internet as well as local sites.
  • SQL Server Reporting Services (SSRS) Integration : It is a feature that allows the installation and the containment of the reports to be managed in the sharepoint itself.
  • Business Connectivity Services (BCS) : It is a feature that allows the system to display the data that is contained inside the sharepoint server. The data can be directly manipulated and wroked upon from the sharepoint.
  • Sites : It is a SharePoint site that is managed by checking the compatiblity with the content-management features.
  • The single server consists of the database servers and the servers that consist of all the data related information. The single server environment is not scalable and there are many applications that can't be installed because of the reduced size. Multiple servers are used to keep user Profile Synchronization in a single server with all the built-in functionalities like database. Other server will consist of the services that are distributed to many layers and provide easy scaling up of the architecture.
What is the difference between WSS and MOSS?
WSS is known as Windows Sharepoint service and it is the core technology used in sharepoint and it is the heart engine of the sharepoint program. It provides management techniques and reporting services to be used with some tools that can be used for communication. It is a free to use service that is implemented on the windows server and used by the sharepoint. Whereas, MOSS (Microsoft office Sharepoint server) just extends the capability of WSS and provides features like audio and video. It includes search engines and enterprise facilities that are used to personalize like management of content and search, etc. It is not free software and can't be used directly.
What are the steps required for the sharepoint to act like an Organizational Platform?
The steps that are required to make the sharepoint act like an organizational platform is as follows:
1. The individual groups that are already present in the sharepoint consist of the collaborative web site that can contain of the data and the communication tools to communicate between different objects of the sharepoint.2. The access to the team and the appropriate group of members will be restricted or limited due to the automative tools that are present.3. The storing of the relevant information can be centralized and maintained according to the organization.4. The communication can be maintained and streamlined so that it will be easier to use and communicate with the parties.5. The involvement of the IT is minimum and familiar tools and technologies are used like web, and windows operating systems.What is the function of delegate control?Delegate control in sharepoint allows the object oriented features to be controlled and replaced by the custom control without doing any modification to the rest of the page. It provides an easy way to access and override the existing functions. It provides certain controls that like add or remove by using the control. The delegate control is very important feature that is included in WSS and MOSS. The delegate control is instantiated by the use of the following lines:<SharePoint:DelegateControl runat="server" ControlId="InputBox" />
The delegate control object uses the features to locate the control that is specified in the ControlID. There are features that are used to create and deploy the InputBox control on the server using the web services.Why is it required to use sandbox solution in sharepoint?The sandbox solution allows easy deployable and reusable packages to be used that consist of features, site definitions and many more functionalities. The sandbox solution can be enabled and disabled manually by going and changing from the settings. The solution can be deployed on the server. The sandbox allows the restriction to be put where the execution of the environment allows certain resources to be enabled and kept into the sandbox without affecting the rest of the server. Sandbox solutions can't affect the whole server as they are not used to deploy at the administrative level. It can be deployed on a site with the administrator permissions using the site collection. Only the administrator is allowed to configure the sandboxed solutions that are related to settings like load balancing, tiers, quotas and resource points, etc.

What are the uses that are taken by using the sandboxed solutions?
There are many uses and benefits by using the sandboxed solutions:1. When there is a need to run the code that are in the production and on the server site then to review and test the code at a particular times becomes difficult as it requires lot of setups of the server and other facilities so to get over this in there are the organization that create the sandboxed solution and uses it to provide different files on which the review and the testing can be performed.2. This can be added to any production environment without the risk of affecting the processes that are outside the sandbox.3. Site collection administrators allow deploying the sandboxed solutions using the administrative tasks. The sandbox solutions also provide scalability and flexibility as it can be run in the separate process and it is not restricted by the quotas.4. The sandbox solution can be modified and recompiled directly on the web server.
What are the different kinds of solutions present in deploying the web servers?
Solutions are contained in the files with the extension of .wsp that contains the features, site definitions, webparts and assemblies that are used to define the whole architecture to provide the solution for deployment of the web servers.

There are two solutions that can be deployed for this purpose:
1. Farm : It is deployed on front end web servers using the user interface libraries by the farm administrators. The administrator in this case will have the full control over the server object model and it won't be having any limitation for the modification done in the files that consists the solutions configurations.2. Sandbox :It is deployed using the collective response format the site administrator that is having the full control with the full permission and the configuration file resides at the root of the site collection. It has the limited access to the resources provided by the server object model and provides isolation and monitoring techniques to the limited users.What are the requests that can't be fulfilled by the sandboxed solutions?Sharepoint server solution consists of a configuration file of the name manifest.xml and other configuration files to run the binaries and assemblies for proper functioning of the program. If the solution is running in the sandbox then the configuration files permissions are limited for the users. The following things that can't be performed by the sandbox are:
1. The solution can't connect to the resources that have to be provided to the users and are not located in the local farm.2. It can't access the database and the data elements inside it.3. It can't change the threading model and allows the new model to be implemented. No modification can be performed in this area.4. It can't call unmanaged code that is just being written by the developer and implemented.5. It doesn't have the permission to write in the disk as well. It will save a local copy but only the administrator can write the files to the disk.What is the difference between the farm and sandbox?There are lots of differences that occur on the basis of the process that has to be performed so the process on which the differences given are:
Deployment process:
1. In the farm the deployment can be done and the simple step is to add the solution and deploy it. Whereas, sandbox requires the uploading of the solution that goes to the site collection and from there it then be activated.Permissions:2. In the farm the deployment can be done only by the farm administrator. Whereas, sandbox has different levels in which if the solution consists of assembly files then only the site administrator can deploy it and if this is not the case then the user with full control permission that is on the root level can deploy it.
Data access:
1. In the farm the data access is restricted to all the users. Whereas, sandbox allow the data accessing to be done by the user through which the data is deployed.
Monitoring:

1. In the farm the processes are not monitored. Whereas, sandbox monitor the processes and are limited by the quotas that is being set by the farm administrator.
Read more »
By at No comments:

Thursday, November 3, 2016

SharePoint App giving credentials popup

APP in SharePoint ,
SharePoint App giving credentials popup



up vote4down vote
  1. Click on Start -> Run and type regedit.
  2. Locate the key 3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right click on this key and choose New > DWord Value
  4. Name this one "DisableLoopbackCheck"
  5. Double-click then on it and type the value “1”
  6. Reboot your server. (Mostly not required)

This helped me in resolving the issue. I am using windows server 2012 and on creating new dword it prompts 32 or 64 bit. I created 64 bit but it does not resolve the issue. I deleted that and created 32 bit dword DisableLoopbackCheck and setting its value 1 resolved my problem.
Read more »
By at No comments:
Labels: