SQLite - Reading SQLite files and converting them into Excel files with global and project data.

Process One Row at a Time - Disable batching completely when dealing with large changes, such as deleting code types, UDF types, and projects. This can also be useful when loading data, if P6 is unable to save certain updates.

Layout Usage Sheet - Know which layouts and filters are in the database, and which filters exist and/or are active inside each layout, as well as which of these filters are user, layout, or global filters. The sheet also lists the Gantt bars in the layout, if they are visible or not, and which filter they reference.

Layout Usage Sheet Loader - Allows the team to clean up user filters from layouts, including global layouts. Replace a layout/user filter reference with a global filter, change the filter reference, and save the filter blob in the proper area in the layout, so that Gantt bar filters can be edited by users other than the original creators of the filter. This is a key tool for keeping your layouts usable over time.

Task Dissolving - The P6-Loader can now dissolve tasks, keeping relationships working correctly in the project.

Better resource assignment and unique loading options - an auto-assignable UDF in the resource assignments can be used to match UDFs when loading and is assigned automatically when loading and extracting resource assignments.

Record action column - adds the ability to specify which action is expected from that record. For example, if you want to ensure that a given user can only be updated but not inserted, the action would be UPDATE.

Layout backup option - you can now include layouts, reports, changes and filters in the daily P6-Loader backup.

Export shift/shift periods from Primavera P6 and convert shift and shift periods from XER/XML files.

Allow custom "CLEAR" cell values, and the value <CLEAR> is the default value to clean up P6 field values, UDFs, and codes.

Easier to work with hierarchical fields - WBS, Resources, Roles, Codes, EPS, OBS, and Cost Accounts.

Full path extracting and loading for all hierarchical codes makes working with these hierarchies easier in Excel. Several new fields were added including the full code path field and a field showing the level of the hierarchy. This makes building hierarchies in Excel easier and loading them into P6 less error prone. Separator definitions are now also configurable.

Allows importing of WBS with their codes (without needing the path) if they are unique across a project

WBS template fragnet loader - You can take advantage of WBS templates built in P6 within P6-Loader to copy WBS nodes, activities, resources assignments, logic, steps, and expenses from one or many templates and fill in any placeholders for activity ID and names as you generate new WBSs into your project. You can also assign UDFs and codes to WBS, activities and resource assignments while applying a template. This is like the old P3 Fragnets on steroids.

Improving the handling of spread information to allow quarterly and yearly spread extractions are back. Manual spread loading of these spread periods is not supported.

Automatically starts activities when loading resource assignment period actuals.

Client required their Primavera P6 database to be upgraded to v21.

Along with the upgrade, areas were identified where data needed to be cleaned up.

P6 security is a little different in the new version of P6, and the client asked for assistance with security for P6 users in the new P6 version.

Client was updating P6 manually at the end of each shift during their turnarounds

They needed a way to make P6 updates quick and error-free

Client also wanted to help streamline their scheduling processes

The client wanted to move their in-house Primavera P6 environment to a cloud option with full time support.

Internal IT was overloaded with other initiatives and lacked expertise in maintaining their Primavera P6 environment.

They required the ability to maintain and analyze their Primavera P6 data in an easy, reliable manner.

The client needed to consolidate several Primavera P6 databases, both shared and standalone, to move to the Oracle Cloud.

They needed the ability to manage appropriate levels of user access to the data for different business units once the databases were combined.

Required the ability to support and execute the Capital Delivery Model (CDM) with Phases and Stages defined.

Each business unit had different schedule requirements that were sometimes unique that needed to be maintained.

This client receives information on a regular basis for managing schedules for different companies. They needed an easier way to create resources and update rates in their P6 database to accommodate the creation of the schedules.

Client receives spreadsheets with activities and resource assignments. They needed an easier way to get this information into P6 to develop schedules.

They receive regular updates to existing schedules and required an easy method to change existing data in P6 to reflect changes made.

The user needed to upgrade their current P6 environment to the latest version but had minimal technical experience to do so.

The client had trouble getting contractor/scheduler updates for pre/post turnaround work

They were upgrading to the latest version of Primavera P6

They had unclean data that needed cleaning up