Below are my raw notes from attending the “Update on InfoPath and SharePoint Forms” session at the Microsoft SharePoint Conference 2014. Most of these are from my Twitter account, as I live-tweeted the session:
Most important first: They don’t have a full replacement for InfoPath that they are announcing today. “It is a journey”, and they are looking for community / client feedback on http://officeforms.uservoice.com . They are planning on multiple technologies – primarily investments in Access and related services – to be the eventual replacements for InfoPath
Next most important: InfoPath 2013 will be supported in the standard lifecycle for the next 10 years. There will just be no new innovation in the software/services.:
Q: Should we expect contextual experience in
#SharePoint Designer? A: It's important, will look at it
Q: What about completing a task inside of Outlook like
#InfoPath? A: We are talking with teams on this; Not sure dev or IW yet #spc14
Q: Why about offline? A: Looking at caching; On radar; Looking at 1 yr in future;
Q: What about external data sources? A: Looking at least a year out.
Q: Are the
#Excel surveys just in Excel 2013? A: On-prem 2013, @Office365 and @onedrive
#FoSL support cascading combos? A: This was added to #Access this last year; Plan to make available to #FoSL
We are aware that
#InfoPath #Forms Services if very important to Enterprise customers. We are working on it.
Q: What about reusability with
#InfoPath / content types A: We are looking at structured documents to answer this.
Q: What about code behind? A: This is on the roadmap, for developers to customize even
#FoSL. Not sure if it will be "code behind"
#InfoPath has attached files. A: We are working through this now. SP lists support attachments. One of the 1st things we do
Q: Will we lose functionality? A: Nothing formal. Maybe code behind, as focused on Information Workers.
Q: When on-premises? A: Not sure yet. We can innovate faster on
@Office365. Will come to on-prem sometime.
Q: LightSwitch doesn't require HTML, JS, etc. A: True, but it pushes into Visual Studio. Not "IW" space. More "pro dev"
Q: Are you able to propagate environments for
#forms on envs? A: You can package it as an App Package. No story yet for #FoSL
At present, no workflow in
#Access #forms #spc14 <—need
Q: Can you change Views on structured docs? A: Probably not.
#FoSL #forms definitely will, based on current state.
Q: Is there
#FoSL integration for workflow with SP Designer? A: We are trying to figure out UI logic, data logic interact. Future
Q: With SP Designer losing design view, what about joining lists? A: Not looking at dev (no CAML intent)
#Excel survey replace #SharePoint survey? A: No
Q: Using K2 Forms with
#InfoPath. What about other data sources? A: That is further out. User Profiles will be 1st. Others later.
Q: Use repeating tables today.
#FoSL? A: Multi-value fields and repeating are something we are looking at for future.
Q: What is the driver for ending
#InfoPath? A: We have multiple paths for the tech needs, and #Access made more sense
#InfoPath will be supported for next 10 years, just no new innovation.
|( ! ) Fatal error: Call to a member function getUserUserBio() on a non-object in /mnt/HostVol01/deliveron/deliveron.com/wwwroot/packages/problog/helpers/blogify.php on line 370|
|2||0.0001||232320||require( '/mnt/HostVol01/deliveron/deliveron.com/wwwroot/concrete/dispatcher.php' )||../index.php:2|
|3||0.0003||235816||require( '/mnt/HostVol01/deliveron/deliveron.com/wwwroot/concrete/startup/updated_core_check.php' )||../dispatcher.php:20|
|4||0.0003||236648||require( '/mnt/HostVol01/deliveron/deliveron.com/wwwroot/updates/concrete18.104.22.168_updater/concrete/dispatcher.php' )||../updated_core_check.php:6|
|6||1.2431||8800448||include( '/mnt/HostVol01/deliveron/deliveron.com/wwwroot/packages/problog/page_types/pb_post.php' )||../view.php:945|
|9||1.2605||9061960||include( '/mnt/HostVol01/deliveron/deliveron.com/wwwroot/packages/problog/blocks/content/templates/blog_post/view.php' )||../block_view.php:311|