Tag Info

Hot answers tagged

3

It looks like you omitted parentColumn and childColumn. This needs to be present for the script to work, otherwise it doesn't know what fields on the form to manipulate. parentColumn The DisplayName of the parent column in the form childColumn The DisplayName of the child column in the form Correct code should be: ...


2

I don't think you use the correct columns' names. You're using the names as seen by the SharePoint search engine, not the internal names of the fields. For instance, ows_Title should be Title, etc. On the other side, I don't think the nested OR are wrong here, they're just up-side-down.


2

The whole Or section looks wrong, try using BIWUG CAML Designer to craft your query, then use that in your SPServices function. Also, you need to use the internal field names, not the web service returned fields (Description1 vs ows_Description1 etc). http://www.biwug.be/resources Typical nested Ors would look like this: <Where> <Or> ...


2

Yes you need to place following query option CAMLQueryOptions: "<QueryOptions><ViewAttributes Scope="Recursive"/></QueryOptions>"


2

You can expand the user field using following code CAMLQueryOptions: "<QueryOptions><ExpandUserField>True</ExpandUserField></QueryOptions>" Now you can extract username in success method by using string manipulation.


1

https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.expanduserfield(v=office.14).aspx Whether to use special rendering for user field values that makes them include the login name, e-mail address, Session Initiation Protocol (SIP) address, and title, when present, which causes a user field to behave as a multilookup field. You don't need ...


1

Hello World - this is the field's display name (as you noted, which is visible in the UI), which in the object model is the SPField.Title property. If you are creating the field from the UI, this is what you specify initially as the field's name. Hello_0x200_World - this is the field's internal name, which in the object model is the SPField.InternalName ...


1

What you are seeing is the internal name and the display name. These can be the same or different. When I am creating an application or anything custom where I will be using web services to fetch data, I carefully name my columns. In the UI when you create a column like "My column" it gets set as My_0x200_column internally like you see and as ...


1

I have used the following javascript to set people pickers on new/edit forms in SP2013: First you need to get the loginName for the user, you could extract the ID from the value you got and use it to get the loginName through a REST query: var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/web/getuserbyid(" + userid + ")"; $.ajax({ url : ...


1

Take a look at this link http://sympmarc.com/2012/04/22/working-with-sharepoint-people-pickers-with-jquery-a-new-function-called-findpeoplepicker/ And use following code to set picker value siteContactPeoplePicker = $().findPeoplePicker({ peoplePickerDisplayName: "Site Contact", valueToSet: $().SPServices.SPGetCurrentUser() });



Only top voted, non community-wiki answers of a minimum length are eligible