This Week in Bamboo (November 3rd, 2013 – November 9th, 2013)

If you have tried our latest SharePoint 2010 releases for Calendar Plus, Navigators, Data-Viewer, and Project Management Central, it is time to try for SharePoint 2013 versions today. This week in Bamboo, we released Calendar Plus R4.5, Navigators R1.5, Data-Viewer R3.6, and Project Management Central R4.1 for SharePoint 2013. The following patches were also released to the storefront at the same time for Task Master, List Rollup, Filters Collection, and Project Portfolio Dashboard. Please check out the latest releases for this week and see the list below for more details.

SA12 Project Management Central for SharePoint 2013 Release 4.1.109.2013

New Features:

  • Add a Reset Order Column button under the Show or Hide columns of the list forms tool to allow users to reset the order of the columns in Edit form, New Form, View Form, and List Settings for the Tasks list and the Project Health list based on the column ordering settings.
  • Bamboo Microsoft Project Add-in:
  • Uses InstallShield
  • Compatibles with both Microsoft Project 2013 (32-bit or 64-bit) and Microsoft Project 2010 (32-bit or 64-bit). Note: Using Bamboo Microsoft Project Add-in with Microsoft Project 2013 or Microsoft Project 2010, users can import, export, and sync tasks to both SharePoint 2013 and SharePoint 2010.
  • New Features in Components:
  • Runtime Filter View now is available for multiple lists.
  • More columns are available to select for filtering as well as using the combination of columns to filter when using the List Filter Web Part.
  • Dynamically filter the calendars using Web Part Connections.
  • Sort the Gantt view based on certain criteria/columns.
  • Ability to sort in Gantt view.
  • Allow defining the position of the legends to display in relation to each other as in the row (horizontal) or in the column (vertical).
  • Allow adding new nested list items directly from the Data-Viewer Web Part.
  • Allow for the display of all items without folders or showing items inside folders.
  • Allow set formatting for the column headers.
  • Allow for the printing of data.
  • Allow Inherit Site Theme for skin and font style.
  • Allow users to use the mega menu (Mega menu is a two-dimensional menu that allows users to display a large sitemap-like menu, expand menus, or link to pages with additional navigation.):
    • Drop-down menus are displayed when the mouse hovers over the top-level menu bar.
    • Allows images in the drop-down menu.
    • Menu items are defined in the Navigators list.
  • Allow users to set the size, color, and/or alignment of the individual TabStrip and menu.
  • Allow showing two levels for the TabStrips.
  • Allow users to show an icon for the TabStrip, menu, and icon.
  • Allow users to set the orientation of the TabStrips and menus.
  • Allow users to go directly to the page from the link, or open the link in another window.
  • Allow users to configure skin and font style via the tool pane configuration or using a custom style sheet (CSS) or inherit from the site theme.
  • Allow users to delete the Navigators list and/or manually create the Navigators list through the tool pane.
  • Allow more than one navigator per site by adding a “Navigation” view column to the Bamboo Navigators list, so it is easier for customers to have more than one navigator per site and the Web Part can use different views.
  • Allow users to show the number of sub-items next to the menu item.

Online Information:

  • For information about Save and Create Portfolio or Stand-Alone Site From the Saved Template in the Site Creation Area, see KB.13007 Info: Save and Create Portfolio or Stand-Alone Site From the Saved Template in the Site Creation Area.
  • Follow these KB articles for installing and using the Bamboo Microsoft Project Add-in with Microsoft Project 2013 and PM Central:
    • HOWTO: Installing the Bamboo Microsoft Project Add-in for PMC 4.0 for SharePoint 2013 (http://store.bamboosolutions.com/KB/article.aspx?id=13005)
    • HOWTO: Synchronize tasks from Microsoft Project 2013 to the PM Central Tasks list in PM Central 4.0 for SharePoint 2013 (http://store.bamboosolutions.com/KB/article.aspx?id=13002)
    • HOWTO: Import Microsoft Project tasks into a SharePoint Tasks list using the Microsoft Project Add-In for PM Central 4.0 (http://store.bamboosolutions.com/KB/article.aspx?id=13003)
    • HOWTO: Export Project tasks to Microsoft Project in PM Central 4.0 for SharePoint 2013 (http://store.bamboosolutions.com/KB/article.aspx?id=13004)

Include updated versions of the following components:

Resolved Customer-Reported Bugs:

  • Anonymous users are prompted for a username and password to access some PM Central pages.
  • Task Master shows incorrect Predecessor Tasks when the title contains special characters such as | / *.
  • In the Datasheet view of the list, the user cannot assign using the Assigned To field.
  • When the milestone’s predecessor due date is ended at 5:00 PM and working hours are from 8:00 AM to 5:00 PM, Task Master recalculates the milestone to the next day with the time of 8:00 AM.
  • When Assigned To is not null, Assignment Units’ value is not automatically defaulted to 100% until the user manually updates this field.
  • In the Gantt View of Active Projects on the portfolio site Schedules tab, special characters in the Project Manager field are expanded to their corresponding numeric value. For example, “D’Angelo” will be displayed as “D&#39Angelo”.
  • In Project Management Central, Site Creation Plus does not show the custom saved templates from the list of site templates and allows users to select as default templates to create new projects or new department site
  • If the Resource column in the tasks list is set to “No” for “Select resources from Resource Pool site” when editing a task and changing the assignee in the Assigned To field PM Central does not save the new assignee value.
  • Reports – If the resource’s profile does not contain a Display Name, the reports display a special character and cannot calculate the working hours of the resource. For example, the resource is DomainabcJSmith. The Resource field will show as DomainabcJSmith. And the Resource Timeline Management cannot display the working hours
  • (Microsoft Project Add-in) Microsoft Project 2010 contains a component that is required during the installation of the Bamboo Microsoft Project Add-In in order to for it to work correctly with Microsoft Project 2013. To work with MS Project 2013 and Bamboo Microsoft Project Add-in, Microsoft Office 2010 requires to be installed first. See KB.12977 for more information
  • Bamboo Microsoft Project Addin-Import function – If the Risks list is selected in SharePoint to import the tasks from Microsoft Project 2013, they will show an error during import.
  • After an in-place upgrade, then click “Update All” and “Update Project” from the All Tasks tab results in an error. The workaround for this issue is to run iisreset.
  • Bamboo Microsoft Project Addin-Import/Sync function – If Import/Sync with Project lite, the option Map “Resource Names” to “Resource” field is not grayed out.
  • The lite project site template cannot be saved as a site template to be used later to create another project site template.
  • In Site Creation Area, Project Management Central does not show the custom saved templates for portfolios (full or lite) or stand-alone sites.
  • If creating a Portfolio site that is the child of a Team site, the Bamboo Project Central Content Types feature must be activated before creating them.

Limitations:

  • When using the Microsoft Project Add-In, if users modify the Outline level field in Microsoft Project without adjusting the WBS field, they will see an error during the merge between PM Central Tasks and Microsoft Project tasks, e.g. Outline Level field is 1 and WBS is 1.1.
  • If you import or export tasks to and from Microsoft Project using the Bamboo Microsoft Project Add-in, it skips the accounts that contain characters such as “[” and “]”.
  • Addin – New/Merge/Append to Microsoft Project – If the Cost and Actual Cost fields for the tasks and parent tasks are populated using Cost (Enter) and Actual Cost (Enter), when exporting to Microsoft Project for new/merge/append, the Cost and Actual fields in the Microsoft Project will not match what is in PM Central’s SharePoint tasks list.
  • When tasks are exported to Microsoft Project using the “Merge” option with the Bamboo Microsoft Project Add-in, child tasks may be merged to the wrong summary task if multiple summary tasks have the same name.
  • When importing tasks from Microsoft Project to a SharePoint Tasks list using the Bamboo Microsoft Project Add-in, the Constraint Date field cannot be updated if the Constraint Date in Microsoft Project is equal to “NA”.
  • Addin – Export to MS Project – Show Duration in MS Project don’t like Duration in SharePoint Task list with use case working mode between MS project and Task Master different. => WAD
  • The User Profile Import Utility can only map User Profile properties with a privacy setting of “Everyone”.
  • If data displayed using the Data-Viewer Web Part is grouped and a group of data spans multiple pages, all data for the same group may not be displayed continuously on the next page. For example, page 2 may start with a different data group instead of continuing the list of items from page 1.
  • After exporting a PM Central Tasks list using the “Connect to Microsoft Project” feature, new tasks created in Microsoft Project with a blank Start Date and Due Date will be incorrectly updated when the task is synchronized to PM Central with the “Synchronize” feature. The Start Date will be set to the Project Start Date from Microsoft Project, and the Due Date will be the next day.
  • When Microsoft Project synchronizes task updates to a connected PM Central Tasks lists, the “Assigned To” field value is not copied if it was updated in Microsoft Project to a resource name that does not exist in Active Directory.
  • If a Calculated column type is displayed in SharePoint Task Master, the calculated value is not updated when the user clicks Recalculate. To view the updated values for Calculated columns, refresh the browser using Control + F5.
  • When users create a new Web Part Page in the portfolio site and try to make this page the default page updating the URL in /_Layouts/AreaWelcomePage.aspx, they will receive the following error: “The site is not valid. The ‘Pages’ document library is missing.” This is a SharePoint limitation.
  • Users logged into the portfolio site with a site collection administrator account will not see rolled-up data in the following tabs: My Summary, Resources, Schedules, Issues and Reporting. This is a SharePoint limitation. To change the limits, go to Central Administration > Manage Web Applications. Select the desired site collection, and then select General Settings > Resource Throttling from the ribbon to change the values.
  • In the “Tasks” tab of the project site under Tracking View, the headers for “Cost”, “Actual Cost” and “% Complete” are not aligned to the left like in other fields

Known Issues:

  • When upgrading PM Central, you must restart the Windows SharePoint Services Timer service before upgrading PM Central sites in Central Administration.
  • When customizing any site page in SharePoint Designer, you must check out the page first. When you are finished editing in SharePoint Designer, save the page and check it back in.
  • When using Workflow Conductor with PM Central, the user cannot deploy workflow using the “Deploy” button. This issue occurs with Windows 2012 Standard or Data Center and Microsoft SharePoint Foundation 2013.
  • In the Resource Center > Resource Assignments, the Gantt Chart shows a JavaScript error when the Project Name contains special characters such as ‘, {, [, …, *.
  • From the project site > Tasks > Progress Management, then click the Update Project Cost & Schedule, the data in the added columns will display with extra data in the additional columns and with the text “System.Data.DataRowView”. By refreshing the page or clicking Ctrl + F5, the data will show as normal.
  • Workflow Conductor and Windows Server 2012 – In Windows Server 2012 environment, if deploy using the deploy button they will see a javascript error “Sys.ArgumentException: Cannot Deserialize.”.
  • Resource Assignments (Gantt chart and Performance) – If there are a lot of resource assignments and projects and therefore a large volume of data to update, information will not be updated immediately even after clicking Run Now with the Bamboo Gantt Chart Timer Job. See the troubleshooting section for the Resource Assignment not showing data online documentation for more information.
  • Resource Availability report – If a user selects to view the Resource Availability with a date range span across 2 years such as 12/1/2012 to 1/15/2013, the capacity for the first year will display as 0 instead of 8 hours for 1 day or 160 hours for 1 month.
  • When PM Central tasks are merged with Microsoft Project tasks using Microsoft Project Add-In and with Microsoft Add-In is set using the Auto Schedule option, if the tasks in SharePoint have a Start Date different than the Start Date of the project and tasks in Microsoft Project after a merge, the tasks will show up with the wrong Start Date and may result in breaking the parent-child relationship.
  • If you merge tasks between PM Central and Microsoft Project using the Microsoft Project Add-in, and the tasks have the same name with different Work Breakdown Structure, after the merge the tasks will show the wrong parent-child relationship and the wrong work breakdown structure.
  • When using the Request New PMC Project Site workflow, the title is missing in the breadcrumb in the form for Start Workflow.
  • If you export tasks to Microsoft Project using the Bamboo Microsoft Project Add-in and then move a task in Microsoft Project, the task will be incorrectly displayed as a child task if you export the PM Central Tasks list again using the “Merge” option.
  • When exporting the Resource Task Timeline report to Excel, the Gantt bar does not show an accurate time span.
  • In User Profiles Import search results, the contents of the About Me field include HTML markup.
  • The User Profiles Import utility displays a maximum of 1000 results.
  • If you change an existing selection for the Project Department or Project fields in a report, the Resource field does not update with the choices that match the new Project Department and Project combination.
  • When Microsoft Project synchronizes task updates to a connected PM Central Tasks list, “Constraint Date” values of “NA” in Microsoft Project—which indicates a constraint type of “As Soon as Possible”—may be set to today’s date when synchronized to the PM Central Tasks list. This does not impact the project schedule.
  • When browsing a PM Central site in HTTPS, chart images exported from the Reporting Web Part to Microsoft Excel are displayed as a red “X” in the Excel workbook.
  • If a project site has unique permissions and its users do not have access to the portfolio site, data from the Enterprise Resource Pool in the portfolio site is still visible in the project site Contacts list.
  • After upgrading PM Central, the Project Portfolio Dashboard does not display data on the portfolio site’s Schedules tab or in the Portfolio Dashboard List after clicking Refresh for the first time. To resolve this issue, restart the SharePoint 2010 Timer service. See KB.12641 for more information.

Known Issues for In-Place Upgrade:

  • When the project site has been created from a saved lite template and the tasks belonging to this project do not get edited again, then the Resource Work By Project and Resource Work Project Department tabs under Report Center on the portfolio site will display an error. This issue only occurs when migrating from SP2010 to SP2013. The workaround is to edit and save the tasks of this project site – where the project site was created from a saved lite template.

Limitations for In-Place Upgrade:

  • Any customizations made to the sites (master pages, CSS, logos, etc.) will not be retained after running the in-place upgrade to SharePoint 2013.
    The upgrade must be run on a new SharePoint 2013 server with content that was upgraded from a SharePoint 2010 server using the database attach and upgrade method.
  • Upgrading PM Central on a server that was upgraded from SharePoint 2010 to SharePoint 2013 (Foundation or Server) on the same hardware will not work.

HW20 Calendar Plus for SharePoint 2013 Release 4.5.182.2013

New Features:

  • Runtime Filter View now is available for multiple lists. Additional option “Show Selected List” to show specific lists with specific views instead of a single list with a single view.
  • More columns are available to select for filtering as well as using the combination of columns to filter when using the List Filter Web Part R1.3.37.2013.
  • Dynamically filter the calendars using Web Part Connections.
  • Sort the Gantt view based on certain criteria/columns.
  • Ability to sort in Gantt view.
  • Allow defining the position of the legends to display in relation to each other as in the row (horizontal) or in the column (vertical).

Bug Fixes:

  • When the data source is a List Rollup and sorting for the Gantt View using the ID column of the Calendar list, Web Part shows error “RenderCalendar: Input string was not in a correct format….”.

Known Issues:

  • Calendar Plus does not work with the data source that is created List Rollup Schema using the Bamboo Aggregation Service on the German site.
  • The data is not shown clearly when the list data contains 4999 items/ 200 items per month.
  • Web Part goes to Day view after viewing then closing an item at Today view.
  • Selecting a column for filtering using Web Part Connection or List Filter Web Part does not work when the column is a lookup column, which gets the data source from datetime type or number type.
  • When the data source is a SharePoint list and sorting for the Gantt View using the ID column of the Calendar list, Web Part shows the error “RenderCalendar: Input string was not in a correct format….”.
  • If a Lookup column with multiple values is used for filtering, the filter results when Calendar Plus is using List Filter Web Part are different than the filter results when Calendar Plus is using Web Part Connection to a list.
  • The data of the Schedule Status custom column from Project Management Central is not shown in the Gantt view.
  • The ID column is not supported for filtering including filtering in tool pane, filtering in Web Part Connection to list, or from List Filter Web Part.
  • When selecting the people picker for color coding or for Item Identifications and if the site has over 100 users, the configuration shows the error “OnPreRender: An item with the same key has already been added”.
  • When there are more than 100 users on a site if users want to color code User filed, use the people picker. Check user’s name function for this field in the tool part is disabled in this release.
  • In Day view, if an item expands to between 11:00 PM and 12:00 AM, the item cell ends before the defined time.
  • Bamboo List Filter Web Part can only connect to Calendar Plus Web Part if the data source is SharePoint List or Library or Bamboo List Rollup Classic Edition.
  • When the data source is List Rollup classic mode, at quarter, year, or week view Calendar Plus does not show event that belongs to “More… “ when filtering on connection with SharePoint list or HW62 any column.

Limitations:

  • When using List Filter Web for filtering, the following columns are not supported for filtering and therefore are not showing in the drop-down for selecting the target column: “All day events”, Multiple lines of text, Calculated, Attachments, Recurrence, Hyperlink, Workspace, and ID.
  • This product can be migrated from SharePoint 2010 to SharePoint 2013. However, there are limitations to the migration procedure. Read KB.12896: How to Migrate Bamboo Products from SharePoint 2010 to SharePoint 2013 for more information.
  • If Calendar Plus Web Part is added on a page created a ListView (example: allitems.aspx), the user will receive the error: “ListRollupSettings :: btnWegPart_Click :: Invalid URL argument.” Work Around: Use the Calendar Plus Web Part on a page that was not generated creating a List View.
  • If Calendar Plus Web Part’s data source is a SharePoint List or Library, and a selected List or Library View is applied as the filter, the view’ Item Limits are not honored.
  • If Calendar Plus Web Part’s data source is a SharePoint List or Library, only one SharePoint List or Library can be displayed in the Gantt View. Work Around: Utilize the Bamboo product List Rollup Web Part to aggregate multiple lists into a single view then connect Calendar Plus Web Part to the resulting List Rollup.
  • In the SharePoint List and Library category of the Calendar Plus Web Part Settings window, the column headers in the included SharePoint Lists and/or Libraries grid cannot be modified the Bamboo Language files.
  • If Calendar Plus Web Part’s data source is Bamboo List Rollup, when configuring Step 8 – Item Identification, the top 200 distinct records are returned.
  • Calendar Plus Web Part’s Print functionality uses HTML to generate the Print Friendly page. As a result, the calendar view spans multiple pages.
  • Calendar Plus Web Part’s Print functionality for Gantt view is limited to what you see is what you get. If items in the Gantt View span beyond the initial view, causing scroll bars to view, you will only see the items shown in the Print Friendly window.
  • Can only display one SharePoint List in Gantt View.
  • Unable to change the column header text in the Select List/Library grid.
  • Calendar only prints HTML and doesn’t do page breaks for each view.
  • Gantt print doesn’t print all items, it prints the scroll bars on the view.
  • New values added to the column configured for color coding are not automatically configured for color coding, resulting in values not appearing in the color legend and events associated with the new value showing no color identification.

HW55 Navigators for SharePoint 2013 Release 1.5.74.2013

New Features:

  • Allow users to use the mega menu (Mega menu is a two-dimensional menu that allows users to display a large sitemap-like menu, expand menus, or link to pages with additional navigation.):
    • Drop-down menus are displayed when the mouse hovers over the top-level menu bar.
    • Allows images in the drop-down menu.
    • Menu items are defined in the Navigators list.
  • Allow users to set the size, color, and/or alignment of the individual TabStrip and menu.
  • Allow showing two levels for the TabStrips.
  • Allow users to show an icon for the TabStrip, menu, and icon.
  • Allow users to set the orientation of the TabStrips and menus.
  • Allow users to go directly to the page from the link, or open the link in another window.
  • Allow users to configure skin and font style via the tool pane configuration or using a custom style sheet (CSS) or inherit from the site theme.
  • Allow users to delete the Navigators list and/or manually create the Navigators list through the tool pane.
  • Allow more than one navigator per site by adding a “Navigation” view column to the Bamboo Navigators list, so it is easier for customers to have more than one navigator per site and the Web Part can use different views.
  • Allow users to show the number of sub-items next to the menu item.

Online Information:

  • For information on how to customize the skin, see KB.13015 HOW TO: Customizing the Skin for Bamboo Navigators Using the Custom Style Option
  • For information on how to add the mega menu, see KB.130017 HOW TO: Add Mega Menu to Bamboo Navigators Menu Web Part

Known Issues:

  • None.

Limitations:

  • The Navigator menu does not show the menus in sort order if one of the items is blank for “Sort Order” field. This is working as designed.
  • For TabStrip menu, the text does not wrap when TabStrip has Size = 50 pixels or when the TabStrip menu’s orientation is in the horizontal position. This is working as designed.
  • For Migration: Cannot edit the tool pane if the icon URL’s value is using the absolute path. The workaround is for the end user to manually modify the URL for the items in the list.
  • For Migration: Custom style does not take effect when migrating to SharePoint 2013. The workaround is to move the information that defines the custom style from the SP2010 style.css file to the SharePoint 2013 xxx.CustomSkin.css file where xxx = TabStrip, Menu…etc. (Navigators for SP2010 and SP2013 have many differences in defining the class name in the CSS file as well as the name of the CSS file. For example: In SP2010, we are using “..TabStripSkinsCustomSkinstyle.css”, but in SP2013 we are using “..TabStripSkinsCustomSkinTabStrip.CustomSkin.css”.).
  • For Migration: When using the Navigators Tree Menu, the “Inherit from site theme” option does not take effect if there are more than 32 Navigators Web Parts on the same page. This is a limitation of Internet Explorer that imposes a maximum limit of 32 individual stylesheet (The reason is that there is a limit on the number of stylesheets per page for IE8, and IE9. When a user adds many Navigator Web Parts to the page, Navigators will register many stylesheets into that page. And if the number of the stylesheets is 32 then the CSS for Navigator Web Parts does not take effect.).

HW37 Data-Viewer Web Part for SharePoint 2013 Release 3.6.81.2013

New feature:

  • Allow adding new nested list items directly from the Data-Viewer Web Part.
  • Allow for the display of all items without folders or showing items inside folders.
  • Allow set formatting for the column headers.
  • Allow for the printing of data.
  • Allow Inherit Site Theme for skin and font style.

Resolved Customer-Reported Bugs and Known Issues/Limitations:

  • When connecting to Rollup Schema as the data source, Web Part shows the Site Name instead of showing the List Name.

The following have been fixed and are no longer limitations:

  • Data Source: All
    • Feature: Calculated Settings
      • If the column that is being Calculated is also used for grouping the data, the resulting Calculated value is shown as the last item in the grouping instead of the bottom of Grid View
    • Feature: Export to Excel
      • Master and Nested Data sets are exported in separate Excel files.
    • Feature: Grouping (Dynamic)
      • Dynamic Grouping only occurs on the current page in the grid and does not group the full data set. (When using List Rollup schema.)
    • Feature: General configuration of Web Part
      • In certain cases, if configuring the Web Part for the first time, the option “Allow Columns to be resized” checkbox found in General Settings is not saved first time selected.
  • Data Source: Bamboo List Rollup Web Part
    • Feature: Export to Excel
      • The following column types are not formatted correctly:
        • Calculated column
        • List Rollup special columns: List Name and Site Name return blank values
    • Feature: Filtering (Default)
      • The following column types are not supported:
        • Calculated column (When using List Rollup schema.)
        • Choice (Multiple Selection mode) (When using List Rollup schema and with the operator “contains”.)
        • Date & Time (When using List Rollup schema.)
        • Hyperlink or Picture (When using List Rollup schema.)
        • Number (When using List Rollup schema.)
        • Yes/No (When using List Rollup schema.)
        • List Rollup special columns: List Name and Site (When using List Rollup schema.)
    • Feature: Filtering (Dynamic)
      • The following column types are not supported:
        • Calculated column (When using List Rollup schema.)
        • Choice (Multiple Selection mode) (When using List Rollup schema and with the operator “contains”.)
        • Date & Time (When using List Rollup schema.)
        • Hyperlink or Picture (When using List Rollup schema.)
        • Number (When using List Rollup schema.)
        • Yes/No (When using List Rollup schema.)
        • List Rollup special columns: List Name and Site Name 1294 (When using List Rollup schema.)
  • Using the [Me] SharePoint variable is only supported with the operators Contains and Equals. (When using List Rollup schema and People is a single value.)
    • Feature: Sorting (Default)
      • Date & Time columns are sorted as text instead of numbers. (When using List Rollup schema.)
    • Feature: Sorting (Dynamic)
      • Date & Time columns are sorted as text instead of numbers (When using List Rollup schema.)
      • Person or Group columns are not sorted correctly due to the data including the profile ID. (When using List Rollup schema.)
  • Data Source: SharePoint List or Library
    • Feature: Export to Excel
      • The following column types are not formatted correctly:
        • Calculated column
  • Data Source: Business Connectivity Services (BCS)
    • Feature: Filtering
      • Certain filter criteria return no results even though items do match the criteria.

Known Issues:

  • When connecting to SQL as the data source, unable to move the pop-up window of the new item using the mouse.
  • When using dynamic sorting in a group, “Calculating Header” and “Calculating Footer” show in the wrong position, e.g. Calculating Footer is at the top and Calculating Header is at the bottom.
  • When using dynamic grouping, calculating results such as “maximum =” are both showing at the top instead of showing one at the top of the grid and one at the bottom of the grid.
  • When using List Rollup as the data source and the Lookup column is set to show additional fields, filtering against these additional Lookup fields does not work. Data-Viewer does not support these types of filtering.
  • When connecting to SQL as the data source and configuring for “group ” and format color for a calculated group, unable to edit the data.
  • The configuration of the Nested list in the Conditional Formatting section is not applied when changing the column display setting.
  •  When using List Rollup as the data source, the ID column sorts incorrectly.
  • When selecting “Yes” for “On Grouping” in the  “Define Parent List Data Calculations” section, the grouping result always shows on the right of the grid view.
  • When grouping where SharePoint list, SQL, or List Rollup Classic is the data source, all of the types of lists or libraries without text types are not supported for sorting. And when grouping where List Rollup Schemas is the data source, all of the types for list or library without text, number, and datetime type are not supported for sorting.
  • When using the SharePoint list as the data source and adding a new nested item, Data-Viewer does not automatically get and populate the value for the mapping column.
  • When using the skin Web20 and connecting to any data source with nested data, expanding and collapsing a nested data set causes an extra line to appear.
  • After initially configuring the Web Part to use Asynchronous Mode, the user requires to navigate away from the page and comes back for the data to show for the first time.

Limitations:

  • When Web Part inherits a Site Theme with the following themes: Wood theme, Purple theme, Red theme, Immerse theme, Orbit theme, City theme, or Lime theme, some text on the WebPart and the tool pane are not displayed clearly.
  • When grouping a single text type and connecting to SQL as the data source, the Web Part shows the message ” Error PreRender:: The data type text and varchar are incompatible in the equal to operator”.
  • When connecting to SQL as the data source, the calculation does not update the result when editing an item on the Web Part interface.
  • When grouping using the People and group type column, the calculation result such as count is showing the wrong result for the group.
  • When connecting to List Rollup as the data source, Data-Viewer does not support the option “Show items inside folders”.
  • “Count, Sum, Average, Maximum, or Minimum” is not correct when nested is used since it sums up the counts from multiple subgroups instead of its own subgroup, e.g.
  • Project 1 has 1 budget and the count is 1; Project 2 has 1 budget and the count should be 1, but the count is shown as 2 since it also counts the budget from Project 1.
  • The Content-Type field does not support sorting or grouping. It cannot be used in the Web Part settings for grouping or sorting.
  • When SQL is selected as the data source, and in the Web Part settings if “Define Item Grouping” is set to use the Column_NText or Text and for the Calculation section in the tool pane is set to  “Yes ” for “on Grouping” field, the Web Part shows an error message.
  • When SQL is selected as the data source, and the Calculation section in the tool pane is set to  “Yes ” for the “on Grouping” field, the Value of that column is not shown after dragging the column for grouping from the Web Part interface.
  • Showing wrong calculated data after changing Locale when summarizing data using calculations.
  • Calculate group is not supported by dynamic grouping.
  • The date field in a group is sorted as a text string instead of a date on the Rollup Classic data source.
  • When grouping using the Content-Type for the document library, the grouping is now displayed in a continuous order due to the limitation of the Content-Type in SharePoint 2010 – For example, it shows the Documents group, then Folders group, and Documents group again. See Microsoft Discussion for more information.
  • Data Source: All
    • Feature: Datasheet Mode
      • Editing a Person or Group column that allows multiple selections will replace the current list of values stored in the column.
      • Choice fields that allow multiple selections do not include a “Select All” choice.
      • Reordering columns with drag and drop is not supported in Datasheet mode.
    • Feature: Grouping (Dynamic)
      • Dynamic Grouping only occurs on the current page in the grid and does not group the full data set. (Except when using List Rollup Schema).
      • The loading icon does not display if using Internet Explorer 8.
    • Feature: Sorting (Default)
      • Default sorting is not honored if default grouping is enabled.
    • Feature: Filtering (Dynamic)
      • The loading icon does not display if using Internet Explorer 8.
    • Feature: Sorting (Dynamic)
      • The loading icon does not display if using Internet Explorer 8.
    • Feature: Language Resource String
      • No resources string is available to modify the text “None” in the Calculated Settings section of the tool pane.
      • No resource strings are available to modify the runtime filter conditions.
    • Feature: General configuration of Web Part
      • After configuring the Web Part, if the user modifies the columns displayed for Master List, the nested list, calculated, and conditional formatting options will be reset
    • Feature: Resize Columns in Runtime Mode
      • Resizing columns in the runtime mode for Nested Grid View causes display issues.
    • Feature: Selection of Columns in Runtime
      • If the grid view has few records, the drop-down menu for the selection of columns in runtime will be cut off.
  • Data Source: Bamboo List Rollup Web Part
    • Feature: Conditional Formatting
      • Columns of the type Hyperlink or Picture and Multiple Lines of Text are not supported.
    • Feature: Datasheet Mode
      • Does not support modification of columns of type External Data Type.
      • Does not support modification of columns of type Multiple Lines of Text (Enhanced rich text).
      • Does not support modification of columns of type Recurrence and Workspace.
    • Feature: Filtering (Default)
      • Filtering lists of type Calendar on either Start Date or End Date will not return items with “All-Day Events” enabled.
      • The following column types are not supported:
        • Choice (Multiple Selection mode) (Except when using List Rollup schema and with the operator “contains”.)
        • Date & Time (When using List Rollup Classic)
        • Hyperlink or Picture  (When using List Rollup Classic)
        • Lookup (Multiple Selection mode)
        • Number (When using List Rollup Classic)
        • Person or Group (Multiple Selection mode
        • Yes/No (When using List Rollup Classic)
        • List Rollup special columns: List Name and Site Name (When using List Rollup Classic)
    • Feature: Filtering (Dynamic)
      • The following column types are not supported:
      • Calculated column (When using List Rollup Classic)
      • Choice (Multiple Selection mode) (Except when using List Rollup Classic with the operator “contains”)
      • Date & Time (When using List Rollup Classic)
      • Hyperlink or Picture (When using List Rollup Classic)
      • Lookup (Multiple Selection mode.
      • Number (When using List Rollup Classic)
      • Person or Group (Multiple Selection mode)
      • Yes/(When use List Rollup Classic)
      • List Rollup special columns: List Name and Site Name 1294 (When using List Rollup Classic)
      • Using the [Me] SharePoint variable is only supported with the operators Contains and Equals. (Except when using List Rollup schema where select a single value for People )
    • Feature: General Data Display
      • If a user modifies their local in the “My Regional Settings” page, columns of type Currency and Calculated (output = Currency), the comma “,” and decimal point “.” are displayed in the wrong position.
    • Feature: Inline Edit Mode
      • Does not support modification of columns of type External Data Type.
      • Does not support modification of columns of type Recurrence and Workspace.
      • Columns of type Multiple Lines of Text – Rich Text and Enhanced Rich Text modes display HTML tags. Alternatively, use the Content Editor provided in Datasheet mode.
    • Feature: Nested Data
      • Association between Parent Data and Nested Data is not supported if mapped columns contain multiple values (People and Group, Lookup, and Choice).
      • Cannot link Nested Data set based on Lookup column in Master List.
    • Feature: Sorting (Default)
      • Date & Time columns are sorted as text instead of numbers.  (When using List Rollup Classic)
      • Person or Group columns are not sorted correctly due to the data including the profile ID.
    • Feature: Sorting (Dynamic)
      • Date & Time columns are sorted as text instead of numbers. (When using List Rollup Classic)
      • Person or Group columns are not sorted correctly due to the data including the profile ID. (When using List Rollup Classic)
  • Data Source: SharePoint List or Library
    • Feature: Conditional Formatting
      • Columns of the type Hyperlink or Picture and Multiple Lines of Text are not supported.
    • Feature: Datasheet Mode
      • Does not support modification of columns of type External Data Type.
      • Does not support modification of columns of type Multiple Lines of Text (Enhanced rich text).
      • If the source is External List, Datasheet mode is not supported.
      • If modifying a column of type Multiple Lines of Text that contains text surrounded tag characters (i.e… <…>), the text will clear upon saving.
      • If modifying a column of type Multiple Lines of Text that contains hyperlinks, the hyperlinks are lost upon saving the changes.
      • When users are modifying a cell of the following Column Types, the users will see the raw data instead of the formatted data. Upon navigating away from the cell, the format will be displayed correctly.
        • Choice (Checkboxes)
        • Lookup (Both Single and Multiple Selection modes) Multiple Lines of Text (Rich Text and Enhanced Rich Text Modes)
        • Person or Group (Single or Multiple Selection modes)
      • Viewing or modifying columns of type Hyperlink or Picture displays only the Description text. User is not able to modify the URL.
      • Viewing or modifying columns of type Multiple Lines of Text (Plain Text mode) removes line breaks. If user modifies the column and saves changes, line breaks are removed from original column text.
      • Columns of type Business Data are not supported. Data-Viewer Web Part hides these columns automatically from view in Datasheet Mode.
      • All Bamboo Custom Columns are not supported.
      • Does not support modification of columns of type Recurrence and Workspace
    • Feature: Export to Excel
      • Column display names with special characters are formatted incorrectly in the resulting Excel column headers.
    • Feature: Filtering (Default)
      • Columns with multiple values are not supported.
    • Feature: Filtering (Dynamic)
      • If the backslash “” is included in the filter string, it will be removed automatically.
      • If Filtering on the Person or Group column, Bamboo recommends using the Contains operator and entering the User Name in the value instead of First or Last Name.
      • Columns with multiple values are not supported.
    • Feature: General Data Display
      • If the user modifies their local in the “My Regional Settings” page, columns of type Currency and Calculated (output = Currency), the comma “,” and decimal point “.” are displayed in the wrong position.
    • Feature: Inline Edit Mode
      • Does not support modification of columns of type External Data Type.
      • If the source is an External List, Inline Edit Mode is not supported
      • Columns of type Business Data are not supported. Data-Viewer Web Part hides these columns automatically from view in Datasheet Mode.
      • Columns of type Multiple Lines of Text with Append Data feature enabled, only the current version text is displayed.
      • Columns of type Multiple Lines of Text – Rich Text and Enhanced Rich Text modes display HTML tags. Alternatively, use the Content Editor provided in Datasheet mode.
      • Does not support modification of columns of type Recurrence and Workspace.
      • Columns of type Lookup with Multiple Selections are not supported.
      • No support for the following Bamboo Custom Columns:
        • Bamboo Column Level Security
        • Bamboo Lookup Selector
        • Bamboo Rating
        • Bamboo Rich Text
        • Bamboo Validator
    • Feature: Nested Data
      • Association between Parent Data and Nested Data is not supported if mapped columns contain multiple values (People and Group, Lookup and Choice).
  • Data Source: SQL Server Table/View
    • Feature: Datasheet Mode
      • Not Supported

HW45 Task Master for SharePoint 2013 Release 3.5.126.2013

Bug Fixes:

  • In the Datasheet view of the list, the user cannot assign using the Assigned To field.
  • When the milestone’s predecessor due date is ended at 5:00 PM and working hours are from 8:00 AM to 5:00 PM, Task Master recalculates the milestone to the next day with the time of 8:00 AM.
  • Task Master shows incorrect Predecessor Tasks when the title contains special characters such as | / *.
  • When Assigned To is not null, Assignment Units’ value is not automatically defaulted to 100% until the user manually updates this field.
  • When clicking on the Assignment Units “Green – Refresh” button, the Assignment Units column does not get updated based on the Assigned To field if the root site collection no longer exists.
  • In the German language, the Start Date in the Calendar week is displayed as Sunday instead of Monday.

New Known Issues:

  • If the parent task has a predecessor and the parent task is a milestone, the Start Date of the parent task and the child task change based on the predecessor’s Due Date. For example, the working hours is set from 8:00 – 5:00 PM and the Start Date for the parent task and child task is 09/18/2013 8:00 AM. If the predecessor’s Due Date is 09/18/2013 5:00PM, the Start Date and Due Date for the parent and child task are now changed to 09/19/2013 at 8:00 AM.
  • Cannot see items in the Web Part interface when changing the theme to black/green (e.g. Lime, City, Orbit, Immerse, Red, Purple, Wood site themes).

New Limitations:

  • When assigning multiple resources in the form and save and the assignees are not sorted in ascending order, in the Datasheet View from the Assigned To’s drop-down the last assignee is unchecked even after clicking on the Recalculate button and Save.

HW24 List Rollup Web Part for SharePoint 2013 Release 6.0.84.2013

Bug Fixes:

  • “Page cannot be displayed” error when saving a large CAML query in the “Define a Filter” settings.
  • The Digital Signature Information for the setup file is invalid and missing information.
  • The error message is displayed when editing/viewing an item while using the German Language pack.
  • When an item is checked out, List Rollup Grid View may show the option to “check out” instead of showing “check in” as it would in SharePoint.
  • The size of the dropdown menu is too wide when choosing a Choice column for filtering.
  • List Rollup Grid View filters incorrectly when using two filter options in “Show Settings”, including using the “Show items only when the following is true” option in Filter settings with “Allow Filtering in Grid View” option in Grid View General Settings.
  • Bamboo Visual Indicator is missing when a list containing it is included in a rollup.
  • Site Columns are not available in Grid View settings.
  • When rolling up lists with versioning controls enabled, “Compliance Details” is not displayed in the List Rollup Grid View, and “Unpublish This Version” is erroneously displayed.
  • An error message is displayed in List Rollup Grid View when clicking on “Version History” in the context menu.
  • The error is displayed when using List Rollup with Calendar Plus when recurrence is enabled and multi-lookup and multi-user columns are present.
  • Error message displayed when accessing a page with a List Rollup Web Part as an anonymous user.

New Known Issues:

  • Cannot access list items by clicking links in Bamboo List Rollup Grid View when rolling up Bamboo Video Library lists.
  • Error message “SystemInvalidException: Specified Cast Is Not Valid ” is displayed when previewing a rollup or showing data on Grid View from a data list that includes a “Scheduling End Date” site column.
  • The presence indicator is not shown for the People and Group columns when using List Rollup Grid View.
  • Unable to create a schema using the “Bamboo Aggregation Service” on a German site.
  • “CheckedOutUserID” error displayed when rolling up a Survey List
  • When exporting Grid View items to Excel, an extra column called “ctx-menu” is added.
  • Cannot export to Excel on a site that contains an apostrophe in the site name.

New Limitations:

  • Filtering on the filename in a Library List requires the file extension when using the EQUAL TO operator. For example, setting filename EQUAL TO “A” will not return “A.docx”, but filtering on EQUAL TO “a.docx” will.

HW61 Filters Collection for SharePoint 2013 Release 1.3.37.2013

Bug Fixes:

  • Minor fixes for compatibility with a new version of Bamboo Calendar Plus Web Part R4.5.

New Known Issues:

  • None.

New Limitations:

  • None.

SA35 Project Portfolio Dashboard for SharePoint 2013 Release 1.8.82.2013

Bug Fixes:

  • Fixed bugs for SA12 Project Management Central:
    • In the Gantt View of Active Projects on the project portfolio dashboard, special characters in the Project Manager field are expanded to their corresponding numeric value. For example, “D’Angelo” will be displayed as “D’Angelo”. Note: For Project Management Central R4.0 and newer, it is on the portfolio site’s Overview tab.
    • When mouse over, the tooltip is showing the tag “<nobr>…” as part of the Show Gantt View of Active Projects Web Part’s description in the tool pane settings.