Sorry.. did I say that with a little too much excitement? I know there has been a lot of conjecture around the future of InfoPath and I’ve been pretty vocal that I think it’s a dead technology. Well, today, finally! Microsoft came out with an official statement.
Update on InfoPath and SharePoint Forms
Jennifer Roth (Mason) is officially my favorite person today for pointing me towards the article.
What’s important to note here is that not only do we have an official statement from Microsoft about the demise of InfoPath, but they clearly state there is a plan moving forward and it even sounds like they have a plan for migration. So, if you are using InfoPath, please don’t panic.. yet.
What IS the plan going forward? Well, there will be a session at the upcoming SharePoint Conference in March that talks about the SharePoint Forms Roadmap. I know I’ll be there, hope you will too.
In the meantime…
If you are looking for your own InfoPath replacement, feel free to check out a little free library I’ve been working on in my spare time which allows you to create forms using standard HTML.
Sounds like there might be a need for it.
So, let’s all raise a glass to InfoPath! Your performance and code behind will be giving us headaches no longer! You had a nice run, but it’s time for something better! InfoPath is dead! Long live… whatever comes next as long as it’s actually better and not a horrible disappointment…
Families in Germany who are facing divers soundness problem, such persons can buy drugs from the Web without prescription. With the market flooded with divers web-sites selling sundry medicaments, purchasing medicines from th WEB is no longer a trouble for common man. Certain medications are used to treat infections caused by dental abscesses. Of course it isn’t all. If you’re concerned about erectile soundness problem, you probably know about Xenical and Hoodia. Probably every adult knows about Garcinia. (Read more PhentermineXenical). The symptoms of sexual health problems in men turn on improbability to have an erection sufficient for sexual functioning. Certain medications may add to sex drive difficulties, so its substantial to cooperate with your soundness care professional so that the prescription can be tailored to your needs. Preparatory to capture Levitra or other medicament, speak to your pharmacist if you have any allergies. Talk to your health care provider for more details. Preparatory to ordering this remedy, tell your physician if you are allergic to anything.
Isn’t it a bit odd that the guy presenting SPC348 with Sonya looks alot like you mate 😉
I was thinking the same thing too!! Why didn’t they just ask ME to co-present 🙂
sorry, I know you hate InfoPath but you may still be able to help me, or send me in the right direction to get help (if there is any help to be had).
I want to modify a sharepoint designer workflow initiation form which is an InfoPath form. I simply want to display the value of a couple fields from the current item upon which the workflow is being run. Just a couple of fields for verification purposes so that the user who is filling out the initiation form knows which item the workflow is running on. (yes, yes, I know, they JUST clicked the link, but you know, you get distracted, you walk away, you come back, and there are no handy visual clues to validate the item on which the workflow was started.)
I open the initiation form in InfoPath but I do not see a way to access the data on the current list item. The only variable references are those on the initiation form which are for user input when the workflow is run.
I tried adding a data connection to the SP List, but the data that displays is simply the values of the first item in that list, having nothing to do with the item on which the workflow is running.
I tried playing around with Form Load rules, but again, I did not see a way to say get me the list item whose ID equals the one on which I am currently running.
I am on Office 365, SPD 2013, InfoPath 2013. Although created in SPD 2013, the actual workflow is of type SPD2010. (some problems with lookup fields in SPD2013…..)
Someone suggested creating a data source to the list, and querying for the item whose ID matches the ID in the URL that called the workflow. I know the URL has this format:
https://SPdomain/site/_layouts/15/IniWrkflIP.aspx?List={e6c2cff3-c74b-4e4e-b8c6-f28cd129b010}&ID=38&ItemGuid={83C51320-E2F0-485F-BE7D-F3CC3DBB3946}&TemplateID={239b33fc-44b4-4baf-904d-178cdc897918}&Source=https%3A%2F%2FSPdomain%2Fsite%2FLists%2FViewname%2Easpx
However, I do not know how to get InfoPath to extract a parameter value from the URL. Any ideas? or any idea who would have any ideas?