SharePoint 2010 copy or moving multiple files

Tweet

 

In this blog I will show you how to copy or move multiple files from one library folder to a subfolder of a particular library. The following steps will assist you in getting this completed. 

 There are a couple ways to copy and move files from a network location or SharePoint list and library.  I have listed a few ways below:

1. First, go to the library of choice where the files exist that you want to move or copy.
2. Click on Library under the “Library Tools” then click on “Explorer” icon.

3. When you click on the “Explorer” icon, the window appears providing you the ability to copy and paste information from your source location to the SharePoint 2010 library.

The additional way of completing a copy and move is listed below:

First, go to the library of choice where the files exist that you want to move or copy.

Then Click on “Site Actions” in the upper left hand corner and click on “Manage Content and Structure”.

 Click on the folder where your files reside.

Either place a check on the individual files you would like to move or select the check box above the files to select all of them. Then click on “Actions” and select either move or copy.

 Select the Destination to move the files, and then click “OK”.

 Let me know if you have any comments or questions.  

Error Handling in InfoPath 2010 Forms when using SharePoint for BPA

Tweet

 

BPA and Error Handling in InfoPath 2010 Forms

Business Process Automation (BPA) with SharePoint and InfoPath includes subtle caveats such as “Error Handling” when warning users of application errors when a field needs to be populated.   Microsoft has placed some defaults within the application that are a bit obscure and sometimes inconsistent with the actual error that is occurring.  In this very brief post, I wanted to give you the idea of creating a new warning by using rules in an InfoPath 2010 form without using the default Microsoft message error message. 

Scenario:  Typically, when a form is created  in InfoPath, many of the fields may be mandatory or required to be populated.  The problem occurs when the message provided is not complete or informative enough for the users to understand what steps need to be taken.  The typical message resembles the following:

Fig 1.0

Some of my associates in the SharePoint realm have used and set policies for organizations using rules to make messages more consistent for all SharePoint developers. Instead of providing error messages like the above, create rules that will display messages that are relevant to the given field of error. In the following example both the “Title” and the “Company” are mandatory fields.

Fig 2.0

If these fields are not populated then the user will receive error messages like the following:

Fig 3.0

By Adding rules to the submit button the default error message in InfoPath 2010 can be avoided.

Example of Rules that were applied:

Fig 4.0

By limiting your user group's exposure to erronious error messages, there will be less user frustration, and they will be more likely to embrace the benefits of your solution. 

If you liked this article, have additional questions, or want additional information, please post your comments below or contact me directly at dlang@orinoco-systems.com.