Showing posts with the label 2010

Error when activating feature of list instance


Always we separate our project in features :
feature for the list instance.
feature for the list definition.
that's will help us to keep data of our list when we disable and we enable features.

so we should activate first of all the list definition then the list instance:
when activating the list instance we get this error:

to fix this issue we should add the feature ID in the listInstance elements.xml:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="">
  <ListInstance Title="TicketLD" OnQuickLaunch="TRUE" TemplateType="100" Url="Lists/Ticket" Description="Ticket List instance" FeatureId="2a3ef305-e7f8-4582-ad89-89612ff82d8b"></ListInstance>

Thanks for sharing.

Deploy Info path using PowerShell, SharePoint 2013

INTRODUCTION This post aims to describe how to deploy infopath forms as form templates in a sharepoint site using Powershell.
SCOPE This post will not detail out how to create a custom infopath form. It will assume that there is already an existing Infopath source files that are for deployment. REQUIREMENTS Sharepoint 2010 Microsoft Infopath Designer 2010
1.Locate the manifest.xml, right-click and click on Design. The Infopath Designer should load.

2.Whenever modifications have been made to the form, it is a good practice to change the version of the infopath form. This is because when you create a version 1.0 and so on for a form, all of the previous versions will be saved in Sharepoint. To do this, Click on File on the Infopath Form Designer. On the Info Ribbon tab, Click on Advanced Form Options. The Form Option dialog box should appear.

3.Change the version on the Version field. 4.[Not Required] If you would like to create another set of source files for the modified I…

SharePoint 2013 Autocomplete textbox using the term store and CSOM

Hello Everyone,

you don't have sometimes the idea to customise the textbox by getting the terms from the termstore ?
if yes, continue reading this post,
ok it's very easy let's start:
you need  jQuery UI Autocomplete.  
The code loads the terms from the term store and then sets the source.
  This implementation is really only ideal for a small amount of terms, but it’s enough to get you started.
For this example, I am going to use a simple set of terms using state names in the United States.  My terms are included in a group named Jobs and a Term Set named Persons.  Here is what my term store looks like.

In this example, we’re going to build our code inside a Client Web Part.  Take a look at that post if you are not familiar with the process yet.  We then need to add a heap of JavaScript references.  Some of these are included already, but specifically we need to load SP.Taxonomy.js.  We also need to include init.js as I mentioned in an earlier blog post. <scripttype="…