Enhance the way people collaborate with documents in SharePoint
Come and learn those extra settings we can turn on to enhance the way people collaborate with documents in SharePoint. There is a set of out of the box settings available in a document library that we can configure to provide a friction free experience for document authors and content consumers.
I receive a question around Administrator-approved InfoPath form templates. Here is the answer.
Q. Haaron, what really happen when we upload a new version of an InfoPath form in central admin?
A. When you upload an InfoPath form template using SharePoint Central Administration some things happen:
1. In Manage Form Template you can provision the same version of the form in more than one Site Collection, you can manage the form, activate or deactivate.
2. It creates a WSP file based on your InfoPath Form Template version and deploys as a farm solution, automatically creates a Site Collection Feature that you can Activate or Deactivate.
3. In Manage Form Templates page, when we Activate To a Site Collection basically activate a Site Collection Feature in the target Site Collection, and that provision the form in the Form Templates library.
4. Behind the scenes, when the WSP is generated SharePoint maintain a version of the form template. That make sense because forms instances can point to older version of the template
And this behavior is the same for MOSS 2007, SharePoint Server 2010 Enterprise and SharePoint Server 2013 Enterprise.
The following image shows the steps for updating a specific group policy with a setting that will describe the path of the binaries required to update Windows 8.1 software, that mean, that you need to mount your Windows 8.1 installer ISO or put your Windows 8.1 installer DVD.
Then you just add the feature .NET Framework 2.0 using the regular Programs section in control panel.
Some of the attendee are knowledgeable SharePoint experts, Speakers and MVPs:
- Gustavo Vélez
- Juan Carlos González
- Fabián Imaz
- Alberto Díaz
- David Martos
- Miguel Tabera
- Mario Cortes
- Edin Kapic
- Gerardo Reyes
- Ricardo Muñoz
- Juan Manuel Herrera
- Juan Andrés Valenzuela
- Haarón González
- Juan Pablo Pussacq
- Andrés Rojas
- Vielka Rojas
- Adrian Díaz
- David Sánchez
- Santiago Porras
- Marco Antonio Canales
This event brings together people from Spain, Costa Rica, Colombia, Mexico, Argentina, basically anywhere Hispanic. Thanks for the good vibes.
- How can I make sure that a particular SharePoint feature or set of feature represent a solution approach for a specific business challenge?
- How can I really envision the level of effort and cost of a SharePoint implementation?
- Wait, did I say business challenge? What are my business challenges?
There are always scenarios where products fit and represent a viable solution for a specific technical challenges. Today I want to talk a little bit about Layer2 Cloud Connector, this is handy tool for dealing with data synchronization between any data source and our favorite product, SharePoint. This tools allow you to define a source connection to one data source and a target connection to a second data source, then you define the mapping between those data sources and just let it run, will sync the data between data source 1 to data source 2 or you can configure bi directional sync so data will get updated in both data sources.
Maybe you have the scenario to sync on premise list to Office 365 SharePoint Online list, or maybe your are not ready for a Hybrid scenario between on premise and Office 365 and you need a solution now, or, maybe you want to sync data from an CSV or excel file in the network on daily basis, this tool can make the difference.
Some general comments:
The process of setting the source and target data connections is easy and very straight forward
Support key columns identifier in the source database
Support key column identifier in the target SharePoint list
It use .NET Data Providers including .NET OracleClient Data Provider
It use Layer 2 Data Providers to SharePoint, it’s based on CSOM so will connect to any SharePoint List
Some sync comments:
Cloud Connector reads the source data and insert in to target list
I created a mapping between database columns and SharePoint Fields using the tool
The tool automatically identify inserts, updates and deletes that need to be performed on target list
Tools has a log that will show how the sync process outcome so you can tell how many records were updated
Tool can run as service so we can do a sync schedule
The licensing model it’s based on the number of source and target connections you need to do, so be careful with that.
Her is an example of the resulting log, I was able to open a local excel file in a share drive, run a SQL query to filters the data from excel and sync the data to a SharePoint list, that was awesome, here is the result:
-> Current product edition is ‘Shareware’
-> Loading items from the data entity ‘SQL Customers’… 91 items retrieved.
-> Loading items from the data entity ‘SharePoint Customers’… 25 items retrieved.
-> Loading metabase…
-> Executing uni-directional synchronization…
-> Instructing data entity ‘SharePoint Customers’ to perform 0 inserts, 6 updates and 0 deletes…
-> Performing post synchronization tasks…
-> Synchronization of connection ‘Customers to O365′ finished:
-> 19 records were already up-to-date, 6 records have been synchronized and 0 records have been skipped. 1 warning occurred. (0.43 minutes)
Just think about it. Is your SharePoint operational state capable enough to support your business enterprise content and information? A SharePoint implementation is more than one server, yes, you can install one server just for testing purposes, not recommended for production. Any software product or solution that your business relies need to be carefully planned and implemented in away to ensure that your business will not be impacted by technical issue or problem that can arise over time specially if you own the hardware and software.
SharePoint has been architected to support high availability and scalability so the business is not impacted with potential hardware or software risks. Make sure your staff knows the implications of an specific server configuration or what we like to call "topology" for your SharePoint implementation.
Yes, it’s expensive, so with your technical staff make sure you explore the implicit costs of owning a server product like this, there are several approaches for using SharePoint this days, third party hosting or the cloud are some examples that can help us with the ROI.
Rolling up SharePoint is not a matter of installing the server infrastructure, also, plan an structure or what we like to call "taxonomy" that represent and fit your business model also is critical and important to ensure that what we present to people make perfect sense.
The following list are some artifacts and configuration settings we also need to plan for:
- Corporate Branding
- Content Types
- Site Columns
- Term Sets
- Sub Sites
- Security Groups
- Web Parts
- Site Templates
Interested on understanding more about this concepts? Just join to my session "Introduction to Intranet Planning" next April 12, 2014 during the First Online SharePoint Saturday Gulf event!
SharePoint MVP and Lead Solution Architect
You have no idea how the MVP program has motivated and influenced my career. Today I was renewed for the tenth consecutive time as a valuable professional Microsoft. Doing some history is clear that this recognition and the opportunity to learn, share and interact with a network of 4000 experts in Microsoft technologies from around the world, has been an experience in my professional and personal life. First I was recognized as valuable professional in ASP / ASP.NET category since February of 2004 and since then I received opportunities and challenges that put me in a position to challenge my paradigms and conceptual models of thought and language. Also, in April 2009 I was recognized as a valuable professional in SharePoint Server. It has been a long journey with a variety of scenarios and people that have left something significant in my life and every day, in every experience I can see and feel their influence. In this journey I have been with my wife and children whom without their support and understanding would not be possible to continue. Thanks Microsoft to renew, thanks friends and colleagues for sharing your experiences, thank to my family for understanding and be part of this effort.
In even the most creative SharePoint implementation plan, we cannot escape one reality we all face: the user. Though the most difficult part of most projects to understand, the user plays a critical part in the success of an overall deployment. In this session, we are going to look closely at new strategies which can be implemented (or improved) in 2013 around understanding our users, building solid user interfaces to support them and deploying them in a manageable way. Each step of the way, Virgil will give attendees a firm understanding of how these strategies can be accomplished in both a 2013 and current 2010 environment. Creating your own Information Architecture best practices in SP2010/SP2013 In the session, Virgil will explore how to develop a solid information architecture strategy for the different aspects of your SharePoint implementation, including collaboration sites, portals and processes. After creating firm IA objectives, the rest of the session will explore how these best practice implementations would differ from SharePoint 2010 to 2013. The session will compare/contrast the feature sets and discuss how to take advantage of both to deliver a user-centric SharePoint experience.
Bring your questions and see you there!