;

Skip to main content

 

  • arrow icon

 

Planview Customer Success Center

Portfolios/ProjectPlace Integration: Version 2

This Product Help content is available to all users. To access PRISMS content, contact your Planview administrator for details.

These short segments deal with the version 2 integration with Portfolios from the perspective of the ProjectPlace user experience. For more in depth information about the connector as a whole including the Portfolios user experience, please see here.

IMPORTANT

The version 2 integration between ProjectPlace and Portfolios requires that your organization leverages Planview Admin and runs sufficiently updated Portfolios software (Earliest: May 2024).

 

           

How do I work with a plan managed by ProjectPlace?

In a connected workspace where the plan is managed by ProjectPlace, everything works just as in a standalone workspace with the following exceptions:

  • In ProjectPlace, working days are set according to the calendar defined for the same project in Portfolios. If a day is closed out for work in Portfolios, it will be closed out in ProjectPlace too. 
  • If an activity in Planview Portfolios has allocations or reported time:
    • You cannot add sub-activities to it.
    • You cannot delete it.
  • The maximum hierarchy depth allowed in Portfolios is 15 levels. If a project is already at level 5, you can only add up to 10 more levels in the ProjectPlace plan structure. Creating activities or reorganizing the plan to exceed 15 levels in total depth is not permitted.
  • Progression runs in Portfolios may affect the plan in ProjectPlace and modify dates.

           

           

How do I connect an existing workspace with Portfolios?

Here's how to connect an existing workspace to Planview Portfolios:

  1. Click the Administration tab in a workspace.
  2. Click Planview Portfolios Integration in the drop down menu that appears.
  3. In the resulting view, click the "+ Select" to bring up a drop down menu of parent structure codes that you have access to in Planview Portfolios.
  4. Once you have selected a "Parent structure code" from the drop down, the input field below will reflect its ID.
  5. When satisfied with your choice in parent structure code, click the Sync button.

Only workspace head administrators may initiate sync with Portfolios. 

Info: A Parent Structure Code designates a specific place in the Portfolios work hierarchy which can contain a Project.


parent_structure_code_selection2.gif

Once you click the Sync button:

  1. You are informed that the connection is currently being established.
  2. Once done, you are notified that it has been successfully established.
  3. Reload the page to see updated information.

That's it! Your ProjectPlace workspace is now connected with a Planview Portfolios project. By default the plan is managed by ProjectPlace.

pending_sync_and_notification.png

sync_established.png

           

           

How do I create a workspace from a synced template?

ProjectPlace workspace templates can be synced with Portfolios project templates. When you create a workspace from such a template, it inherits content from ProjectPlace, while the linked Portfolios project reflects most elements from its own template (e.g., allocations). This sync can now be initiated directly from ProjectPlace—previously, it had to start from Portfolios.

Steps:

  1. In the New Workspace dialog, choose a template with the Portfolios icon.
  2. Select "Yes" under Planview Portfolios Integration.
  3. Choose a Parent Structure Code.
  4. Click Create and wait for the sync to complete.
  5. You'll receive a notification once it's done.

Known issue:

Initial sync can take several minutes. Improvements are in progress to reduce this time.

clipboard_e33bf77c6f8f02910ac10b639fc6073ea.png

clipboard_e12bf7648349fc83ad28f73ae65b577fa.png

clipboard_eed6d250220f9fbe0d171ce9477283efc.png

clipboard_e224746c98815a04e67c8b17335da54db.png

 

 

           

           

How do I decide which system should manage the plan?

The choice depends on your organizational needs. Planview does not specify a preferred system.

For projects requiring agility and adaptable structure, manage your plan in ProjectPlace. For those needing detailed control over multiple dependencies and constraints, choose Portfolios.

You can switch the managing system at any time, which will restrict plan editing capabilities in the alternate system.

If transitioning management to ProjectPlace from Planview Portfolios, ensure:

  • The project in Portfolios does not have any dependencies, either internal or linked to other projects, as these must be removed first.
  • The project is not using Partial Plan Sync.

Plans managed in ProjectPlace can be transferred to Portfolios at any time, but consider:

  • All days will be set as working days in ProjectPlace.
  • Any existing dependencies in ProjectPlace will be removed upon transfer.

IMPORTANT

We recommend selecting which system should manage the plan and then sticking to it, unless there is a compelling reason to switch.

Frequent changes to the which system manages the plan are discouraged:

  1. Multiple handshakes between systems are required to complete a handover of control. Switching back and forth often increases the risk of losing changes.
  2. Frequent changes create confusion for users, as they cannot rely on a specific system to manage the plan.

           

           

How do I switch which system manages the plan?

  1. In a workspace, navigate to Administration > Planview Portfolios Integration.
  2. Select the system that should manage the plan.
  3. Click the Send button.

Once you have clicked Send, we recommend that you reload the page.

Only workspace head administrators may change which system manages the plan.

toggle_system_of_record2.gif

           

           

What Portfolios calendars are supported when ProjectPlace manages the plan?

(This documentation pertains to changes released 30 April, 2026. Previously only STANDARD calendar was supported.)

Planview Portfolios allows detailed customization of working days and hours, including partial days. ProjectPlace only supports fully open or fully closed days. However, ProjectPlace is aware of Portfolios calendars and adapts accordingly.

When ProjectPlace manages the plan: ProjectPlace uses the calendar specified on the project in Portfolios. Days closed in Portfolios are also unavailable in ProjectPlace. If a day has any open time in Portfolios, it appears as fully open in ProjectPlace. ProjectPlace uses the full calendar details when communicating dates and durations back to Portfolios.

Example:

  1. In Portfolios, a calendar is defined as: Monday through Friday have 8 hours open per day; Saturday has 4 hours open.
  2. In ProjectPlace, Monday through Saturday appear as open. A task spanning Monday to Saturday (inclusive) has a duration of 6 days in ProjectPlace.
  3. In Portfolios, the dates match precisely, but the duration will be 5.5 days (since Saturday only contributes 4 of the typical 8-hour workday).
  4. If someone then closes Saturday entirely in Portfolios, ProjectPlace detects the change and extends the task to span Monday to the following Monday (inclusive). The duration remains 6 days in ProjectPlace.
  5. The corresponding task in Portfolios now also shows a duration of 6 days.

What we guarantee: Dates match precisely, down to the minute, regardless of calendar configuration. Durations are not guaranteed to match, since ProjectPlace does not account for partial-day hours. Duration by days in Portfolios is also governed by what is the stated average workday time.

When Portfolios manages the plan: ProjectPlace treats all days as working days. Dates will align between the two systems, but durations may differ. For example, a task running from Friday morning to Monday afternoon shows as two days in Portfolios but four days in ProjectPlace.

Only workspace head administrators may resync calendars.

NOTE

When a calendar is updated in Portfolios, many connected ProjectPlace workspaces may be affected. ProjectPlace automatically queries Portfolios for calendar changes every three hours and updates affected workspaces in bulk.

To trigger an immediate sync:

  1. Go to Workspace > Administration > Portfolios Integration.
  2. Click Sync calendar.

This starts a background job that fetches all calendars from Portfolios and updates all affected workspaces with new calendar information. The manual sync can only be run once every 15 minutes.

           

           

What are overlapping dependencies and why do they appear?

Occasionally, in connected workspaces where ProjectPlace manages the plan, you may experience:

  1. An alert indicating overlapping dependencies in the plan.
  2. A button labeled "Fix dependencies" to assist in resolving these issues.

overlap_alerts.png

What does this mean?

An overlapping dependency occurs when a task is scheduled to start before its predecessor finishes, which is illogical. An alert notifies editors of the plan to address this issue. The accompanying button provides options to adjust dates, delete dependencies, or ignore the issue for manual correction later.

Why does it happen?

Overlapping dependencies can occur because of progression runs in Planview Portfolios. These are scheduled tasks that update various elements, including plan dates, typically outside of regular hours. These updates change dates in a connected project without considering existing dependencies, which may result in overlaps.

Persistence of the Alert:

This alert and button reappear for all editors every time the plan is accessed until the overlapping dependencies are resolved.

Can I get rid of the alert/button?

Yes, an account administrator can contact customer support to set an organization-wide default action, either automatically adjusting dates to resolve dependencies or deleting them. Currently, it's not possible to set default actions for specific workspaces. Once a default is established, informational alerts will replace the alert message and button, indicating the adjustments or deletions made.

           

           

Why do tasks move - even though I have locked them?

Sometimes, in connected workspaces where ProjectPlace manages the plan, a locked activity or milestone will show date changes by “Integration”. Locks are meant to prevent accidental moves, not to guarantee immutability. Anyone with write access can unlock, change, and re-lock. During sync with Portfolios, ProjectPlace may defer to Portfolios, for example during progression runs, and apply changes despite locks. In those cases, the item’s history shows “Integration” as the actor.

           

           

How do I fix dependencies?

  1. Click the Fix dependencies button in the toolbar upon seeing the alert.
  2. Choose to either remove overlapping dependencies,
  3. or adjust dates.
  4. Confirm your choice by clicking the button.
  5. Once complete, the plan data refreshes automatically, and a confirmation message verifies the successful resolution.
  • Adjusting dates involves shifting dependent activities forward until they start after their predecessors have finished. This action automatically generates a snapshot before the adjustment, allowing you to review and manually tweak the changes. Benefit: Keeps dependencies intact and provides a reference for adjustments.
  • Removing overlapping dependencies involves deleting relationships where a dependent activity starts before the predecessor has finished. Benefit: Keeps original dates unchanged. Drawback: Deletes the dependencies causing the overlap.

overlapping_dependencies2.gif

           

           

Why is the plan locked even though I have edit permissions?

There are three possible reasons:

  1. The plan is managed in Portfolios - and therefore the plan is locked for everybody in ProjectPlace.
  2. The plan is managed in ProjectPlace - but there are insufficient permissions in Portfolios to allow editing.
    1. the head administrator of the workspace MUST have at least read permission to the corresponding Project in Portfolios for anyone to be able to edit the plan
    2. workspace members must have edit permissions both within ProjectPlace and in Portfolios to edit activities and milestones,
    3. workspace members must be members of the organizational account to qualify for edit permissions.
  3. The plan is managed in ProjectPlace - but the corresponding project in Portfolios is marked as Cancelled, Denied, On Hold or Completed. At that point we prevent updates in ProjectPlace from occuring at all. The corresponding project must first be re-opened in Portfolios. The workspace head administrator can re-open directly from ProjectPlace.

How can I tell what permissions I have to edit the plan?

Begin by accessing the plan tool in your workspace and check the toolbar.

  1. If you see options to add activities and milestones, you have permission to edit the plan.
  2. If there's a Planview Portfolios logo and the tooltip says, "The plan in this workspace is syncing with Planview Portfolios," the plan is managed by Portfolios.
  3. If the logo appears with a tooltip stating, "You lack edit permissions for the corresponding Project in Planview Portfolios," this indicates the plan is managed in ProjectPlace but you do not have the necessary permissions to edit it as per ProjectPlace and/or Portfolios requirements.
     

toolbar_edit_permissions.png

           

           

How can I check who can edit a connected plan?

(This is relevant only for workspaces managed by ProjectPlace)

As a workspace administrator, you can verify which members can edit the plan in a connected workspace by navigating to Administration > Planview Portfolios Integration.

  1. If managed by ProjectPlace,
  2. the bottom part of the page will display a table listing workspace members.
  3. This table shows whether each member has edit permissions in both Portfolios and ProjectPlace.
  4. Edit permissions in Portfolios are checked several times daily. You can manually update this check by clicking the "Refresh" button.
  5. The "Last updated" column indicates the last permission check in Portfolios. 

NOTE

The list includes only workspace members who are also part of your organization as configured in Planview Admin.

edit_permissions.png

           

           

How do I work with synced workspace templates?

Version 2 of the ProjectPlace/Portfolios integration introduces control over the plan within workspace templates.

  • A synced template must be initiated in Portfolios.
  • Once set up, the managing system can be toggled to ProjectPlace, just like in a normal workspace.

When ProjectPlace manages the plan in a synced workspace template:

  • The template's calendar aligns with the STANDARD Portfolios calendar, marking Saturdays and Sundays as non-working days.
  • The ProjectPlace UI for templates uses offsets and durations instead of dates, but actual dates are set in the background and reflected in Portfolios. These dates adjust automatically when creating a workspace based on the template, according to the chosen start date.

NOTE

When creating a workspace from a ProjectPlace template and syncing it to Portfolios, resources defined in the Portfolios project template will not automatically transfer to the new project in Portfolios.

To ensure assignments, financials, and other details from the Portfolios template are carried over, initiate the workspace/project creation from within Portfolios.

           

           

Can I manage the Portfolios Lifecycle Administrator from ProjectPlace?

Yes, this will be automatically attempted if a workspace sync is started in ProjectPlace. 

If you start the sync-process of a ProjectPlace workspace to Portfolios, ProjectPlace will attempt to set the Lifecycle Administrator in Portfolios to match the ProjectPlace workspace head administrator. ProjectPlace will only set the value immediately after an initial sync, any subsequent changes will have to be conducted in Portfolios.

Prerequisites:

  • The head administrator must exist in Portfolios and have the same email across the two systems
  • They must have “Administer Projects” Role Feature enabled for their user role in Portfolios. (Read more about the Lifecycle Administrator here)

NOTE

There may be an up to 15 minute delay between a workspace having been fully synced to the lifecycle administrator field being updated in Portfolios.