Martin Reid
mwp.reid at qub.ac.uk
Mon Jan 13 02:32:00 CST 2014
Shamil We found out of the box workflows limited for anything complex. For simple tasks the out of the box stuff is fine. The developers here generally build SharePoint features which give us greater control and are easier to manage. All development is done using Visual Studio and each developer has their own MSDN subscription which really cuts down on license costs. We have also began to look at Azure Virtual Machines as a development platform. My own role has changed here now and I now lead the development team for SharePoint and CRM 2013. However, I am more than happy to pass any technical questions to the team in here who I have to say are one of the best about when it comes to getting stuff done in SharePoint. We are also moving to SharePoint 2013 this year and almost all new development will involve building 2013 apps. In my own opinion there is a huge market for well designed and developed SharePoint apps using the 2013 model especially in the education market. Martin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Salakhetdinov Shamil Sent: 13 January 2014 02:21 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Sign up for an Office 365 Developer Site Hi Martin -- Thank you for your reply. Yes, I'd also prefer to use C# to develop Office 365/SharePoint data-lists manipulations. I'd use SharePoint REST API for that http://msdn.microsoft.com/en-us/library/office/jj860569.aspx Would that work? For small business Office 365/SharePoint hosting plan are also available SharePoint Designer: What's new with SharePoint 2013 site development http://msdn.microsoft.com/library/jj163942(v=office.15).aspx and workflows: What's new in workflows for SharePoint 2013 http://msdn.microsoft.com/library/office/jj163177(v=office.15).aspx Still the issue could be to develop custom workflows: How to: Build and deploy workflow custom actions http://msdn.microsoft.com/en-US/library/office/jj163911.aspx as this development would need a SharePoint server installed locally? Thank you. -- Shamil Monday, January 13, 2014 12:11 AM UTC from Martin Reid <mwp.reid at qub.ac.uk>: >Shamil > >We have lists with millions of items. However not many and for specific purposes. Out generic lists have a limit currently set at 15000 items. Re access you can use access services or hybrid, linking to data onsharepoint lists but we don't do much of access anymore. We mostly build apps in C sharp running as Sharepoint features etc in terms of users I have over 30000 we have a 16 server farm with 4 sql clustered instances running it all. > >We also,use remote blob storage to get around Sharepoint limits. > >Martin > >Sent from my iPad > >> On 13 Jan 2014, at 00:04, "Salakhetdinov Shamil" < mcp2004 at mail.ru > wrote: >> >> Thank you Darryl. >> >> So, when you have to handle (structured) data then you use SharePoint Lists? >> Do you use MS Access with SharePoint Lists? >> Have you ever met SharePoint Lists limitations - http://msdn.microsoft.com/en-us/library/ff647105.aspx - recommended max qty of items in a list to be 2000 (two thousands)? >> Or SharePoint Lists usually keep unstructured data - whole data tables stored as CSV/text delimited files, XML, JSON...? >> In this case is there a limitation on the size of the data stored in one SharePoint list item? >> >> Please feel free to reply when you'll have time. >> >> Thank you. >> >> -- Shamil >> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com