Skip to main content

Troubleshooting Templates & Project Access in GUIDEcx 2.0

Learn how to resolve common issues related to template dependencies, project creation, user access, customer permissions, and project invitations in GUIDEcx 2.0.

Written by Elan Maynez

Introduction

When configuring templates and projects in GUIDEcx 2.0, you may occasionally encounter issues related to task dependencies, project creation errors, or user access permissions. This guide walks through the most common problems and provides steps to quickly identify and resolve them.


Understanding Circular Dependencies in Templates

When building templates in GUIDEcx, certain dependency configurations are not supported. These restrictions exist to prevent circular dependencies.

A circular dependency occurs when two or more tasks rely on each other in a way that prevents any of them from starting.

Example of a Circular Dependency

Incorrect Dependency Structure

  • Task A depends on Task B

  • Task B depends on Task A

Because both tasks rely on each other, neither task can begin, preventing the system from successfully creating a project from the template.


Best Practices for Task Dependencies

1. Avoid Parent/Subtask Dependency Loops

Subtasks should not be dependent on their parent task.

Supported Dependency Structures

Subtasks may depend on:

  • Other tasks that occur earlier in the project

  • Other subtasks within the same parent task

Unsupported Dependency Structures

Subtasks should not depend on:

  • Their own parent task

Improper parent/subtask dependencies can create circular dependency issues and prevent project creation.


2. Use Cascading Task Dependencies

Task dependencies should always follow a forward-moving sequence.

Recommended Structure

Task A → Task B → Task C

This means:

  • Task B depends on Task A

  • Task C depends on Task B

Avoid Backward Dependencies

Backward or looping dependencies can prevent templates from being used to create projects successfully.


Troubleshooting Template Dependency Issues

If your template appears correct but still cannot be used to create projects, there may be a hidden dependency issue within a milestone.

Follow these steps to isolate the problematic milestone.


Step 1: Templatize Your Milestones

From the template view:

  1. Locate each milestone

  2. Click the three dots next to the milestone name

  3. Select Templatize Milestone


Step 2: Create a New Test Project

  1. Navigate to the Projects page

  2. Click New Project

  3. Open a blank project plan with an empty milestone section


Step 3: Add Milestones Individually

Add each milestone template one at a time.

If you receive the error:

“Failed to create Milestone from template”

the milestone you just added likely contains the problematic dependency.


Step 4: Adjust Dependencies

Once the problematic milestone has been identified:

  1. Return to the template

  2. Review the milestone’s task dependencies

  3. Make small dependency adjustments

  4. Retest by adding the milestone again

  5. Repeat until the milestone successfully creates


Common Project-Related Issues

Internal User Cannot Access a Project

If an internal user cannot access a project:

  • Verify they have been assigned the appropriate role

  • Ensure they have access through Resource Management if Resource Management is enabled


Customer Cannot Access a Project

If a customer receives a Permission Denied error after receiving a project link:

Verify the Project Status

Customers and lower-level internal users can only access projects when the project status is set to:

  • On Time

If the project is still in:

  • Pending

the customer may receive a permission denied error.


“Failed to Load Service Render Components” Error

This error commonly occurs when using Create Project From Template with a template that does not contain any phases.

Resolution

Add at least one phase to the template and try again.


Unable to Add Internal Team Members to a Project

If Resource Management is enabled:

  • Users must first be assigned to their appropriate roles within Resource Management

  • Once assigned, they can be added to projects

  • This requirement also applies to third-party users


Changing Customer View Permissions

To switch a customer between:

  • Full Plan View

  • Portal View

update their permissions within the Resource Management tab.


Customer Did Not Receive a Project Invite

Customers only receive a project invitation email when the project status changes:

  • From: Pending

  • To: On Time

If the project has not been moved to On Time, the invitation email will not send.


Frequently Asked Questions

Why can’t I create a project from my template?

The most common cause is a circular dependency within the template. Review task and subtask dependencies to ensure there are no loops or backward dependencies.


Can subtasks depend on parent tasks?

No. Subtasks should not depend on their own parent task, as this can create circular dependency issues.


What does “Failed to create Milestone from template” mean?

This error typically indicates that the milestone contains an invalid dependency structure. Templatizing and testing milestones individually can help isolate the issue.


Why is my customer receiving a permission denied error?

Customers can only access projects when the project status is set to On Time. Draft or Pending projects are not accessible to customers.


Why didn’t my customer receive a project invite email?

Project invitation emails are only triggered when the project status changes from Pending to On Time.


Why can’t I add users to a project?

If Resource Management is enabled, users must first be assigned to the correct roles within Resource Management before they can be added to projects.


What causes the “Failed to Load Service Render Components” error?

This typically occurs when attempting to create a project from a template that does not contain any phases. Adding at least one phase resolves the issue.

Did this answer your question?