I have 2 questions about sharepoint 2010.
When will Sharepoint Server 2010 released ?
Is Sharepoint Server 2010 easy customized in terms of layout aspect ?
Description:We have a government client. They care UI more than other aspects such as functionality. So this B/S project will have a very customizable UI, and the client is highly likely to modify the UI at any time. I have reviewed Sharepoint Server 2010 that it is easy to make different themes, but I am wondering if it is still easy to modify website's layout.
SharePoint 2010 has already been released to RTM and is available through an MSDN subscription.
As for customization... It's as customizable as you want it to be, and even more so than 2007.
If they are going to modify the UI at any time, what elements are you talking about? The masterpage? layout pages, or just content withing the sites?
Themes are simple css files that don't do much more than change styles,fonts, colors etc. Masterpages give you all the muscle of ASP.NET so you can pretty much go to town on them. You do need to be careful of the new Ribbon UI though.
Related
I'm starting a new project where we are expecting to migrate desktop based Access 2016 applications (with a lot of backend VBA and relationships between the tables) into SharePoint 2016 on-premise and very soon, SharePoint Online. From what I've been told, we'll be given site permission to a SharePoint site that we can do whatever we want with. I am hoping that with SharePoint 2016 on-premise and eventually SharePoint online means that there is a SQL Server and eventually Azure SQL Database that I can migrate the Access backend tables and queries, as I know SharePoint lists will be inadequate for this, despite the false notion that SharePoint lists are an equivalent substitute for database tables.
My concern is how to build the custom forms, perform the needed business logic, perform CRUD operations, and upload data in the form of Excel files from the SharePoint site to the backend.
I'm new to SharePoint and given that it does not support VBA, that Microsoft cut out Access Web Apps earlier this year, and they are phasing out SharePoint Designer 2013 and InfoPath, some research over the past week indicates my best options are building custom web application using ASP.NET Core and somehow deploying that to the SharePoint site and subsites that we have control over, or developing a lot of HTML, CSS, and JS to create the front-end interface. I had read about the Business Connectivity Service to get and post data to / from the SharePoint site front end and the DB backend, as well as using Javascript and AJAX calls to do CRUD operations between the database and the frontend. I looked into PowerApps and those seem insufficient, and I'm still trying to distinguish between SharePoint web parts and SharePoint add-ins.
Is any of the above even a feasible option? Could someone chime in on a better path to go about this? What technologies would I need to best go about this?
Support for moving tables from Access to SharePoint remains a choice and option.
So all of your VBA code etc. will work as before. The only real question is if you want to move your data to SharePoint tables in place of using SQL server.
SQL server tables are far faster than SharePoint tables.
However, you can certainly consider moving your tables to SharePoint. When you move your tables to SharePoint (or SQL server), then Access code, forms, reports etc. and EVEN your VBA code will work as before. What this means is that you continue to deploy the Access application to each desktop. The only difference is now your tables are on SharePoint, or SQL server.
The above choice does not result in a web based application.
So you can move the data, but your application will remain a desktop application.
If you looking to build a web based application, then Access is the wrong tool – you need to adopt something like Visual Studio.
So you can continue to use Access, and put the data tables into the cloud, or on-site SharePoint - but the application will be still desktop based.
I have used the following extensively over the last couple of years and I am happy with the experience:
Azure SQL Database as a back-end
Flow for automation and as an interface to the DB
PowerApps for forms, desktop apps and mobile apps
Excel for reporting (Get & Transform aka PowerQuery and DAX), especially for printing reports
Power BI for dashboards (limited use)
Yes, PowerApps has drawbacks, but there are a lot of realistic workarounds out there and new features/improvements are being added regularly.
I have also used SharePoint lists as data sources, but almost always then migrated to Azure SQL Database.
Is it possible to use use SharePoint to custom develop a GUI for an SQL Server backend for updating the data? Thanks.
If you are using SharePoint 2007 you might want to take a look at the Business Data Catalogue - http://msdn.microsoft.com/en-us/library/ms563661(v=office.12).aspx
Not sure what the comparable feature (if any) in 2010/2013 is...
EDIT:
In 2013 it is called Business Connectivity Services - http://msdn.microsoft.com/en-us/library/jj163782.aspx#BCSoverview_Whatcanbcsdo
Look at "Business Connectivity Services" and "External List".
SharePoint Designer can make the process pretty simple or you can develop a Visual Studio project:
http://msdn.microsoft.com/en-us/library/ee558778(v=office.14).aspx
If you want to do the legwork try building an Access Application in SharePoint 2013.
It is much better than 2010 but requires more setup. This will encapsulate a database within a SQL database, very versatile super quick and you can do all your SQL fun stuff from there.
This is a low or no code solution.
SharePoint 2010 Access apps use lists as back-end repositories, you can interact with the data in the SharePoint WSS_Content database, but it is not supported and no advisable.
I am looking for a migration tool. We want to upgrade from SharePoint Server 2007 to SharePoint 2010 in a new environment. We need to have functionality to granulary select which content to migrate and eaven select to map to new structure in the new solution.
We want to tag the content migrated.
The migration tools we are considering are AvePoint, Axceler Davinci, Metalogix.
I'm doing migration scenarios for a consultant firm based in Montreal. First of all, I think you have the correct thinking about how you want to get this done. Doing a SharePoint upgrade (database upgrade) usually bring your SharePoint 2007 problems over to SharePoint 2010.
Here's what we usually do :
Define governance for the new SharePoint platform
Define the new Information Architecture
Implement the new Information Architecture (build sites, lists, libraries, etc.)
Migrate the content over
Tools such as Sharegate (www.share-gate.com) can allow you to do some mapping from your old content source over to the new one.
Hopefully, this will help you!
All my googling returned only information related to how to add additional right click features.
I swear somewhere I saw screenshots of MSS2010 being used where right clicking provided the menu to do various operations, versus having to use the ribbon, or worse that awful menu pictured here.
I was expecting this to all be drag drop... :(
I'm really disappointed with the lack of ajaxy-ness built into mss2010. I can't believe every save/apply reloads the whole page.
SharePoint is a massive product. Microsoft appears to be adding and improving as much functionality as it can in each release.
A high priority of Microsoft for SharePoint 2010 was to redo the HTML for the end user pages. And it is much improved. The poorly formed, table heavy HTML of SharePoint 2007 now has more divs and unordered lists. However, you have stated that you do not like their design choices of the ribbon and full page refreshes. And you also do not like that UI improvements did not extend to system pages in the layouts directory.
SharePoint 2010 was released almost a year ago. Functionality changed during the beta, but it is unlikely that big changes will be introduced at this point. Your two best bets for getting your desired functionality are:
Create a CodePlex project that provides the functionality you want. If the project becomes popular, Microsoft might include it in the next release.
Based on Sharepoint Feature Request, post your request to the SharePoint forums with a subject of "FEATURE REQUEST". If Microsoft agrees to your request, it could be included in the next release.
MacroView specializes in document management, email management and knowledge management solutions based on Microsoft Office and Microsoft SharePoint.
MacroView DMF and MacroView Message add a new pane to Outlook which displays all the areas of the SharePoint environment for which you have access permission. The new pane in Outlook provides:
Searching across the SharePoint DM store with results displayed in Outlook
Formatted previews of files in SharePoint, without the need to download and open
Extensive right-click menu for files and areas
Right-click to create new Libraries and Folders
One-click access to your Favorite document libraries and folders in SharePoint
Automatic creation of Favorites – e.g. for Projects for which you are a timekeeper
Drag & Drop from everywhere to anywhere to save emails or attachments to ANY area where you have permission
Go here for more information
I'm working with Visual Studio 2010 and Sharepoint 2010. I would like to know if there's a way to have a web part that crawls all the data within a SharePoint site so I can save it into a custom db.
You can certainly create a custom web part that will do this. I do not know of an out of the box web part that will work. I began writing something like this when I found SharePoint List Source and Destination. It's a CodePlex project for an SSIS SharePoint adapter. We did not need a user interface for the extract, so we used it successfully last year for transferring data between SQL Server and SharePoint.
Sounds like all you need to do is use the API, OOB web services, or the Client OM to write some code and access the lists directly. Which approach you take depends mostly on where the code will run.
Well I found this article - Document Library Tree View Web Part for SharePoint - it is a Web Part that shows all the info of any of the document libraries within a site. At least I know how to crawl that kind of library.