Release Notes for List Print

Release Notes for List Print

NOTE: Release Notes will open in a new browser tab

WSSv3/MOSS SharePoint 2010 SharePoint 2013 SharePoint 2016
Release Notes Release Notes Release Notes Release Notes
Microsoft ended mainstream support for SharePoint 2007 in October 2012. See Microsoft’s Lifecycle Support Policy.
At that time, Bamboo stopped enhancements to our SharePoint 2007 product line, but continues to provide support and bug fixes to customers with active support contracts until October 2017. Previously purchased licenses will continue to function after October 2017, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2007 products in October 2016 to ensure customers will be eligible to receive support for at least one year after purchase.
Microsoft plans to end mainstream support for SharePoint 2010 in October 2015. See Microsoft’s Lifecycle Support Policy. At that time, we will stop any enhancements for our SharePoint 2010 product line but will continue to provide support and bug fixes for our SharePoint 2010 products to customers with active support contracts until October 2020. Previously purchased licenses will continue to function after October 2020, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2010 products in October 2019 to ensure customers will be eligible to receive support for at least one year after purchase.

Visit our website where you can get the latest info about each of our products for SharePoint 2013.

A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles:

Bamboo Solutions has also begun releasing products for SharePoint 2016. For additional details, check the product release notes in the link above, or contact us.

For details on migration, see the Knowledge Base Article “Migrate Bamboo Products from SharePoint 2013 to SharePoint 2016”

Understanding Bamboo Releases:

  • Bamboo offers Trial, Basic and Premium support.
    • Free Trial support expires after 30 days.
    • For more information about Basic and Premium support, please see the Support Plans page.
    • There may be a fee to upgrade from a major version to another.

See Also:

Overview of the List Print user display

Overview of the List Print user display

When List Print is accessed a new window with the contents of the current list will open in a popup window.

Image of the List Print popup screen. Image is modified to show the three drop down boxes

The image has been edited to better display the configuration options

Item Function
1. Select the list View that you want to print.
2.

The Template selected will determine how the list information is presented when it is printed or exported. The following template options are available for all list views:

  • Basic Table

  • Column Form

If the selected View is Grouped two additional options will be available :

  • Grouped Tabular View

  • Grouped Column Form

NOTE: The Grouped templates will only be available when selected View is Grouped. The following message will display when an ungrouped view is displayed.

The selected view is not grouped by a column.  Grouped templates are not avaialble
3.

The Actions button gives you the option to:

  • Export all the contents of the selected list view to Excel

OR

  • Print all the contents of the selected list view

    Image of Printed results using List Print with Basic Table template

Migrating List Print from SharePoint 2007 to SharePoint 2010

Migrating List Print from SharePoint 2007 to SharePoint 2010

Be sure you have at least the Minimum SharePoint 2007 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2010 farm requires at least the Minimum SharePoint 2010 product release shown.

Icon-Warning IMPORTANT: When migrating from SharePoint 2007 to SharePoint 2010, you MUST select the option to change existing SharePoint sites to use the new user experience. Your Bamboo products will not perform as expected with the old look and feel.

Minimum SharePoint 2007 Product Release 1.4.5 Minimum SharePoint 2010 Product Release 10.4.18
In-Place Upgrade
Issues List Print functions properly on existing SharePoint lists and libraries. If a user creates a new SharePoint list or library from custom list or library templates in the List Template Gallery that were created prior to upgrading to SharePoint 2010, the List Print action button in the ribbon has no action.
Resolution The only way to resolve the issue with custom list or library templates created in SharePoint 2007 is to create new templates in SharePoint 2010 based on SharePoint 2010 list types (example: Contacts, Tasks, Calendar, etc.).
Database Attach Upgrade Method
Issues List Print functions properly on existing SharePoint lists and libraries. If a user creates a new SharePoint list or library from custom list or library templates in the List Template Gallery that were created prior to upgrading to SharePoint 2010, the List Print action button in the ribbon has no action.
Resolution The only way to resolve the issue with custom list or library templates created in SharePoint 2007 is to create new templates in SharePoint 2010 based on SharePoint 2010 list types (example: Contacts, Tasks, Calendar, etc.).

Migrating List Print from SharePoint 2010 to SharePoint 2013

Migrating List Print from SharePoint 2010 to SharePoint 2013

Be sure you have at least the Minimum SharePoint 2010 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2013 farm requires at least the Minimum SharePoint 2013 product release shown.

Icon-WarningIMPORTANT: When migrating from SharePoint 2010 to SharePoint 2013, the Database Attach Upgrade Method is the only method supported.

Minimum SharePoint 2010 Product Release 10.4.31 Minimum SharePoint 2013 Product Release 10.4.36.2013
Database Attach Upgrade Method
Issues The List Print migrates without any errors or additional steps required.
Resolution N/A

Localize Bamboo Applications or Custom Columns

Localize Bamboo Applications or Custom Columns

Overview of the localization process for Bamboo Products

Bamboo applications and custom columns are slightly different than web parts when it comes to localizing/translating. The user interface isn’t confined to a web part, but can exist as site definitions or other custom pages. For example, the configuration of a Bamboo custom column is within the SharePoint list settings area.
The text strings that require translation are located in different files than the strings that appear in a web part.

Changing the language or text for an application or custom column is a multi-step process:

Top

About the Language Files

Text displayed in a Bamboo application may be included in one or both of the following locations:

  • Provisioning Resources. These resources are located in the 12, 14, or 15 “Hive”, in the Resources folder. The number of the Hive depends on the version of SharePoint you are using (e.g., SP2007 has a 12 Hive, SP2010 has a 14 Hive, and SP2013 has a 15 Hive). 14Hiveresources.jpg

    The Bamboo.*.resx files include text used in site features, site definitions, list definitions, and other provisioning resource elements. Any changes you make in these files will apply to new product instances only.

  • Application/Runtime Resources. These are also located in the 12, 14, or 15 Hive, but in the CONFIGResources folder.The Bamboo.*.resx file in the CONFIG folder is different than the one included in the Resource folder.14HiveCONFIGResources.jpg This one includes text used in application pages, custom site menu actions, navigation elements, and other runtime resources. Any changes you make will apply to new and existing product instances only.

In each location, there may be multiple versions of Bamboo.*.resx files with identical content. The different files are provided for English (en-US), German (de-DE), French (fr-FR), and Spanish (es-ES). The content of all files is in English until you translate it to your language. If your site is configured to use a language that does not have a corresponding Bamboo product .resx file, copy an existing file and rename it to include the culture name for that language pack. For example, create a file for Italian by saving the default file as Bamboo.[Product].it-IT.resx. Make your changes to this new file. If your site is configured to use a specific language but you do not have a culture-specific file, the product will use the default Bamboo.[Product].resx file instead.

Icon-WarningIMPORTANT: If you customize one of the default resource files provided with the product, your changes will be overwritten when you upgrade.

To avoid losing customizations, copy the customized file to a different location (not the same folder) before upgrading. After the upgrade is finished, compare the new file with your customized file to incorporate any new entries. Then copy the merged file to the Resources folder. Culture-specific files created for languages that are not provided with the product will not be overwritten during an upgrade, but you still need to incorporate new resource entries.

Top

Editing text in resource files

Icon-WarningIMPORTANT: Before making any changes, back up your original file to a different folder.

To change text in a resource file, open it in a text editor and locate the text you want to change. Editable text is usually found between the <value></value> tags, as shown in the screen shot below. Do not modify the data tag. If you want to remove text completely, delete only the text; do not delete the <data> or <value> entries from the file, or the server will display an error message. In the example below, the editable text is highlighted in gray.

Common_resxEdit.jpg

When you are finished with your changes, save the file and copy it to the appropriate Resources *folder on *all Web front-end servers in your SharePoint farm. Follow the instructions below to make your changes take effect.

Top

Applying Language File Updates

To apply changes to Provisioning Resource Files:

If you modified the provisioning resources file, apply your changes by restarting Web services with the following command on all Web front-end servers.

iisreset

NOTE: changes to provisioning resources affect new instances of the Bamboo product only; existing instances of the product are not updated.

To apply changes to Application/Runtime Resource Files:

If you modified the application/runtime resources file, apply your changes by executing the following stsadm command on all Web front-end servers. This command copies the updated resource file to the App_GlobalResources folder of each Web application. Changes apply to existing product instances and any new instances you create.

stsadm -o CopyAppBinContent

NOTE: Changes apply to EXISTING product instances AND any new instances you create.

List Print Templates

List Print Templates

Overview of List Print user display

When using List Print the entire contents of the list view can be easily printed or exported to Excel. The template selected will determine the layout of the list view’s content.

The following options are available for all views:

Basic TableImage of the Basic Table Layout Column FormImage of the Column Table Layout. Shows all columns associated with an item in view stacked vertically

If the list view selected is grouped two additional template options are available:

Grouped Column FormImage of the Grouped Column View.  Shows a basic table grouped by the designated column Grouped Tabular ViewImage of the Grouped Tabular Layout. Items are grouped by the designated column all columns associated with an item in view stacked vertically

The images above were edited to fit the screen

How to find the version of List Print

How to find the version of List Print

NOTE: In order to find the version of List Print, you need to be able to access one of the Web Front End (WFE) servers in your SharePoint farm.

Step Action
1. On one of the Web front-end servers in the SharePoint Farm, browse to the %systemroot%assembly folder. This is typically in c:WindowsAssembly, but could be in a different location on your WFE server.
2. Locate the product assembly for List Print; its called Bamboo.ListPrint. Right click the assembly name and choose Properties from the menu that appears. The
List Print Assembly.jpg
The Properties dialog will appear.
3. Select the Version tab to view detailed version information about the assembly. Within the listing is an attribute labeled File Version. This is the version of the current installed product.
list print props.jpg