Hot answers tagged

3

You can get everything of a user from it's id. Like following function getEmail(userId) { var context = new SP.ClientContext("https://xxx.sharepoint.com"); var web = context.get_web(); var user = web.get_siteUsers().getById(userId); context.load(user); context.executeQueryAsync(function() { console.log(user.get_email()); }, ...


2

You have to login on the admin center with admin accounts. Sign in to Office 365 with your SharePoint Online admin account. Go to the SharePoint admin center. Click User Profiles. Under People, choose Manage User Properties. On the Manage Properties page, select New Property. On the Add Profile Property page, in the Property Settings section, in the Name ...


2

You can achieve this functionality using Alert Me. following are the steps. 1: Go To your Calendar 2: Go To "Alert Me"(on Ribbon) --> Set alert on this list 3: Configure your alert. 4: Done


2

This might not answer your question. Search is not real time. In your case it's a single list and you can query the list using CAML. To optimise performance you can index the fields you are querying.


1

For get files from folders you should need to load collection by passing folderPath through CamlQuery. Please refer below code: var query = new SP.CamlQuery(); query.set_folderServerRelativeUrl(folderPath); var Folderitems = list.getItems(query); context.load(Folderitems, 'Include(Title, ContentType, File , Folder)');


1

Still this no API for retrieving all user profiles from SharePoint Online You can get current user's profile _api/SP.UserProfiles.PeopleManager/GetMyProperties Or a particular user's profile by login name /_api/SP.UserProfiles.PeopleManager/GetPropertiesFor(accountName=@v)?@v='i:0%23.f|membership|xx@siteurl.onmicrosoft.com' BUT You can get available ...


1

Try this link Hope this link will help. Also you can find various tutorial on google.


1

If you write: using (SPSite siteCollectionParent = new SPSite(strUrl)) you don't need to dispose because the using-Method will do this for you as you guessed. But this has no impact on your child-Instances! So for disposing your siteCollectionChild you can write foreach(SPSite siteCollectionChild in childCollections) { try { ...


1

It is clearly mentioned in your given link at the end in Beware of host headers section that If you are using a host header for your web application apps won’t just work for that web application. Because of how the redirect for the app domain works IIS will try to resolve the app url by using the default IIS web site, which of course doesn’t work. ...


1

The best one I found is the solution provided by Share-gate here http://en.share-gate.com/blog/image-slider-with-sharepoint-2013-search-results Basically it is based on using search results web part and custom display template. I have followed the same example on an intranet site I have built, but I was able to change from SlideJS to jssor sliders here ...


1

Try writing this $.getScript(hostweburl + "/_layouts/15/SP.RequestExecutor.js", getSubSite("/Test 2")); like this instead $.getScript(hostweburl + "/_layouts/15/SP.RequestExecutor.js", function(){ getSubSite("/Test 2"); }); to avoid immediate execution of the getSubSite method ( = to wait until SP.RequestExecutor.js is actually loaded)


1

The cause of your issue should be the ownership was not released by the InfoPath. You may need to add the Fault Handling activity in your workflow to deal with the exception. Please find the solution in answers within below mentioned link's discussion. User is shown message "is checked out for editing by" their domain\username - how to ...


1

The reason why SalarioOWS is not showing because it is probably not refinable and that why You have to map SalarioOWS to one of the refinable properties like RefinableStringxx or RefinableIntxx (depends on the data type of Salario) you can follow this guide to map it a refinable property: ...


1

As your restHelper.peopleSearchQuery(options);is a promise, you can call that function and add a then() which in turn calls drawUserData restHelper.peopleSearchQuery(options).then(drawUserData);


1

If you want to use the SharePoint app model then yes, you must allow posts. SharePoint sends authorization & authentication data to your app via post. Your app needs that data to generate a client context. Take a look at the tokenhelper.cs file and/or the landing page code behind & you should see the post data processing



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