Is there a way to set up a column that would allow SharePoint to use Lync location. Such as if Lync shows you at 1400 building, SharePoint can show you at that same location. Then if you move, that location would be updated as necessary.
The Location property is available only on Lync. I'm not aware of any possibility of mapping with Active Directory fields and, consequently, syncing in SharePoint.
Further, as you can imagine this property value can change frequently. In case you'd be able to it map with SharePoint User Profiles, you'd be always subject to user profile synchronization schedule to have this property updated.
A possibility would be to create a visual component in SharePoint that, communicating directly with Lync via REST APIs (UCWA), retrieves this information directly from Lync, and displays this in your SharePoint pages.
The best starting point for information about Lync 2013 UCWA is: http://ucwa.lync.com
Related
We've set up the Sharepoint integration for our Dynamics 365 online instance. It works fine.
On the document management tab I've chosen 16 entities to have sharepoint integration. The wizard does it's work and it claims that 16 folders have been created. In truth, only 15 have been created.
When I re-run the wizard, it claims that all 16 folders are existent. It also lists the URLs. 15 work, the 16th shows a 404 HTTP error.
No idea, why the wizard is acting up.
Any idea what I would need to do to manually setup the 16th folder? How's Dynamics linked to Sharepoint? Would it be good enough to create a document collection manually in Sharepoint?
Not sure why it didn't do that automatically for you.
When you run the wizard it creates locations in SharePoint, and in CRM; document location records that point to those locations in SharePoint. The link at a folder level is based simply on URL stored as text in CRM document location records.
You should be fine to create the location manually in SharePoint. You could also try deleting the document location records from CRM and running the wizard again. You could also check the document location records have the correct URL configured.
Related reading: Integrate Microsoft Dynamics 365 with SharePoint.
I solved the issue by access Sharepoint with the Sharepoint Designer.
I saw that the 16th element was already present but not as a list but as some other type (folder?).
Apparently, the wizard just checks whether an element with that name already exists but it doesn't check the type of the element.
Solution: I deleted the element with that name and ran the wizard again and now it's fine.
I have a web application. When the user clicks on a button in my web application, I'd like to retrieve data from SharePoint on behalf of the user. I have read quite a few articles on SharePoint but I'm still not sure how to proceed. Should I create a provider hosted SharePoint App and use the SharePointREST API? Thank you in advance for your help.
You don't need to create a Provider to use the SharePoint Rest Services.
Quoting http://msdn.microsoft.com/en-us/library/office/jj164022(v=office.15).aspx :
One advantage of using REST is that you don’t have to add references to any SharePoint 2013 libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. See Get started with the SharePoint 2013 REST service for a thorough introduction to the SharePoint 2013 REST interface and its architecture.
Inside the page you will find videos and code examples that will help you to connect and execute operations.
It's Correct. Data in SharePoint is Stored in Lists or Libraries (to files).
You can use the Client Object Model, to get data remotely from a SharePoint Server (on-premise or Online). The Client Object Model can be used through Assemblies (DLL files) or REST services provided by SharePoint. Generally you should know the location of the data you are going to get, that is, as I initially mentioned, the data in SharePoint are stored in Lists or Libraries, therefore you must know the name of the List or Library Additional Site or Sub-site of the List or Library is.
If the name of the list where the information is stored is "employees" and the HR website, the URL could be formed as follows:
http://spserver.company.com/HR/Employees
For REST services, simply complete URL of the list you want to see, so that you retrieve the information from the list. If you want to apply filters, sorting, to retrieve specific columns, you must do it through CAML queries which the add on REST service call.
I was wondering if is it possible to retrieve Office 365 directory information (i.e. security group membership) from SharePoint online programmatically (for example through a workflow custom action)?
By the way, I am not looking for retrieving Sharepoint group membership information.
I know the custom development is pretty limited with SharePoint online since the code has to run as a sandbox solution. Is there any web service or any another solution available?
I have been looking for information about this matter but I could not find anything so I guess there is no way to do this.
In our case there is an active directory synchronized with office 365. So we will use a powershell script to read data from AD and update a sharepoint list every day.
Then we will be able to use this data from custom code (like a workflow custom action).
Is it possible to create an activity explorer in Sharepoint 2010?
By activity explorer I refer to the functionality of logging emails, phone calls, documents accessed (and time and who accessed/edited them) to specific entries in a database.
For example, I intend to export my current Access Claims Management database top a Sharepoint sever.
With each claim entered into the database:
I wish to log all relevant emails sent, and the user logs all relevant calls. This would require sending emails through the sharepoint front end I pressume?
For each claim a directory is created, where the user can store relevant documents to each claim. Is it possible to log / version control these documents?
Thanks in advance for any assistance or advice.
Noel
Quick answers:
-I wish to log all relevant emails sent, and the user logs all relevant calls. This would require sending emails through the sharepoint front end I pressume?
Yes, otherwise you would not be able to track them.
-For each claim a directory is created, where the user can store relevant documents to each claim. Is it possible to log / version control these documents?
Yes, you could employ a document library that creates folders automatically when an email arrives. Or you can pre-create and then any email sent to the document library will be displayed as a SharePoint item. You can enable versioning on any SharePoint list/document library.
You could then build an custom activity explorer that will display all these actions.
I'm curious about the best/most efficient way to do this.
I've already set up my sharepoint 2010 site, and it is configured to use FBA. What i'd like to do is allow users to create their own accounts by filling out a form (the form will sit on a public sharepoint site, and filling it out creates a user in the membership database which is used for validation to enter the FBA sharepoint site).
I'm familiar with using the asp CreateWizard tool to build user accounts as part of a .Net web application, but I'm not sure on how to develop this as a webpart for use in a sharepoint site, as a webpart doesn't have the config file to store connection string and membership/role provider info.
Can this user creation form be put in a webpart and deployed to other sites, or is there another/better way to add this functionality to sharepoint (allowing users to register/create their own FBA accounts for access)?
There's nothing not much difference between SharePoint and regular ASP.Net for this.
The membership provider will need to be configured in the SharePoint web.config, including connection strings. However, it does not actually need to be used for login, so you can still create users in that membership provide from a different site.
I use a slightly different approach though - set up an anonymously accessible page in your site (in layouts is probably easiest, though a page within a site may be better for branding) and put controls on that page to create (and log in) a new user. You will need to call EnsureUser and possibly CreateUserProfile to give the new user access to anything, but aside from that it's all standard .net.