We are tasked to develop Forms for Sharepoint 2019 modern pages. Can anyone enlighten if Infopath is supported with Sharepoint 2019 Modern experience? If not, what are the native alternatives? We cannot install 3rd party tools like nintex or other solutions. Any suggestions will be highly appreciated.
Thanks
You can use PowerApps or SharePoint framework (SPFx)
InfoPath is not supported with SharePoint 2019 modern experience.
You could connect PowerApps with SharePoint 2019 by using gateway.
Reference:
https://powerapps.microsoft.com/en-us/blog/support-for-sharepoint-on-premises/
Related
I'm currently using Microsoft Office Professional in version 16.0.4266.1001, and it has Word JavaScript API 1.1.
I'm wondering if I can update Word JavaScript API to 1.3 without updating my Microsoft Office Professional?
In that case I would have Microsoft Office Professional version 16.0.4266.1001 and Word Javascript API 1.3.
Thank you for reply :)
New features in the Office.js API have dependency on the updates in the product. so you need to update office if you want to use the 1.3. BTW we are now in Builds 16.0.8229, so your build is quite old, I strongly recommend you to update. thanks!
Unfortunately not; the JS APIs and the supporting host code are intricately connected.
See https://dev.office.com/docs/add-ins/develop/office-js-versioning
Does anyone know what happened to the Powershell power tools for TFS 2017?
I have existing scripts for TFS and would like to keep using them.
I tried installed the 2015 tools but they will not install because it requires VS 2015 and I am using 2017.
To my knowledge there are no Power Tools for Team Foundation Server 2017 (see https://www.visualstudio.com/en-us/news/releasenotes/tfs2017-relnotes).
That said you can leverage #igor-abade Powershell CmdLets (https://github.com/igoravl/tfscmdlets) which offer a good deal of features.
does anyone know if there is a GitHub plug-in available for InstallShield 2008 Premier Edition? I haven't had much luck googling it. I submitted a question to GitHub Support and they actually suggested submitting a question on Stack Overflow (which I likely would have done anyway). If anyone can assist it would be greatly appreciated. Thank you.
Regards,
Randy Maddocks
InstallShield supports MSSCCI plugins on its own, or when used inside Visual Studio, InstallShield can interact with the source control provider used by Visual Studio.
I don't believe there are any MSSCCI GitHub plugins, and I'm unclear whether you have Visual Studio. Personally I find it straightforward to work with the GitHub desktop client.
I did dig through the SugarCRM CE documentation and forums but could not find answer to this
how to enable mobile browser access for SugarCRM community edition 6.. ?
For mobile access of Sugar CRM community edition, you need a third party application like
CE Mobile CRM
Rolus Sugar CRM
The CE version does not support Sugar Mobile (see Edition Comparison).
I have a requirement to create an installer for an Outlook 2003 add-in that was created with VSTO.
We currently are using Wix for our installers as they play nice with MSBuild and I need to use it to create the installer for the outlook add-in.
I have no experience with outlook add-ins and am unsure exactly what is involved and how to go about creating the installer.
Can anyone share any experience/tips/examples that would help me please?
Thanks in advance,
B
I found this Microsoft article on VSTO add-ins deployment to be an absolute life-saver; I don't know about Wix, though. http://msdn.microsoft.com/en-us/library/bb332052.aspx
I've not done this in WiX but I have done it in InstallShield. Below with my notes from that time:
http://blog.deploymentengineering.com/search?q=vsto
One problem you will have is that WiX doesn't have a bootstrapper so you will have to find a way to chain the .NET Framework and VSTO redist ( also possibly the Office 2003 PIAs; you didn't say which version of VSTO you are using ) with your installer unless you choose to take the route that merely gates the install if those aren't found.
I recall using a DTF custom action to publish a certificate but I can't recall if that was needed for Office 2003 or only for Office 2007.