European Sharepoint 2013 Hosting Blog

Here, we will discuss how to add a new line in multiline textbox using XML file in InfoPath.

Let’s start to create the XML file with standard coding. Please follow the below steps to achieve this.

You can copy the code directly from here as well.

Now, your file is ready with code. Now, follow the below steps to implement this task.

Upload your file under SharePoint Site Asset Library.
Try to create a data connection with the connection type as retrieve data.
Click on “Next” and choose the XML file option.
Go to SP site asset and try to copy your XML file path and paste here.
And, finish the Data Connection Creation here.

You have to create a simple text box control, go the textbox properties, and enable the multiline textbox.

Now, you can manage the rule and apply the data connection for a new line in a multiline textbox. I hope your issue has been resolved now.

SharePoint 2013 Hosting Recommendation

HostForLIFE.eu’s SharePoint 2013 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2013 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2013 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2013 plans as well as dedicated SharePoint 2013 Foundation options.

When working with different versions of SharePoint, we have the respective PnP modules installed. This article explains how to easily load the appropriate Module automatically. I use SharePoint PnP PowerShell cmdlets almost every workday to make a lot of customizations and to perform administrative tasks. I guess no introduction is needed about PnP PowerShell with its huge usage and popularity.

Now, if you are a user like me who is working on different versions of SharePoint, 2013, 2016, 2019 & Online, using the right PnP PowerShell module to target the SharePoint version is tedious. When you install different PnP PowerShell modules (i.e., 2013, 2016, 2019 & Online), we have a cmdlet name conflict because all the modules have the same name for the cmdlets. And none of the modules are loaded initially when you open a PowerShell session.

How are the modules loaded?

When you first run any PnP PowerShell cmdlet (obviously Connect-PnPOnline), the PnP PowerShell module is automatically loaded based on the modules path. Though most of the cmdlets work the same in all versions of SharePoint, there are significant changes in how the authentication is handled and SharePoint Online always has few more cmdlets compared to the On-premise versions. So, we need to load the specific PnP Module depending on the SharePoint version we are using.

Which module (2013, 2016, 2019, Online) is loaded?

When you have different modules installed, PowerShell picks the modules to load from the default modules path (in environment variables). As this appears to be alphabetical, 2013 module is loaded by default in my case.

PowerShell by changing the PSModulePath in environment variables, and using Import-Module whenever we need to target for a different version of SharePoint. This is quick workaround is helpful, but we have to run the Import-Module cmdlet every time we need to use a different version of the PnP SharePoint module.

Another approach to do this

Isn’t it cool to have different icons like this to target the PnP PowerShell module for the specific SharePoint version? This way, you don’t have to manually run any Import-Module cmdlets. These are desktop shortcuts for PowerShell specifying which module to load using the shortcut parameters. And when we open any shortcut, PowerShell is opened with the respective PnP Module already loaded.

This way, I can easily open a PowerShell session for the respective SharePoint version without the hassle of typing Import-Module cmdlets always.

How to do this?

• Right click on your desktop to create a new shortcut
• In the create shortcut window, in the location of the item text box, type the following command.

  C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoExit -Command “Import-Module -Name ‘C:\Users\ram\AppData\Local\Apps\SharePointPnPPowerShell2016\Modules\SharePointPnPPowerShell2016\SharePointPnPPowerShell2016.psd1’ -DisableNameChecking;”

•  And click Next. This basically specifies that we open PowerShell and load the module targeted for SharePoint 2016.
  
• Type the name (target version of SharePoint) and click Finish.
  

Now, whenever I open PowerShell with this shortcut, I am ready to write cmdlets for SharePoint 2016. Similarly I keep 4 different shortcuts for 2013, 2016, 2019 and SharePoint Online which is handy, as I dont have to run the Import-Module cmdlet whenever I need to target a different version of SharePoint.

Summary

This shows a simple solution using the windows shortcuts and the -Command parameter to start the powershell, and to load a specific PowerShell module, enabling us to create quick shortcuts for opening the right PnP module.