Troubleshooting - Tripletex Project synchronisation

Modified on Tue, 16 Jun at 10:59 AM

Troubleshooting - Tripletex Project synchronisation


This article explains two common errors in Tripletex Project synchronisation: project is not created in Tripletex, and a duplicate project is created.



TABLE OF CONTENTS




Introduction to troubleshooting


Errors in Tripletex Project synchronisation are often due to missing project configuration in Telaris, a missing integration reference, a duplicate project number, or the project already existing in Tripletex.

Project synchronisation goes only one way:

  • Telaris → Tripletex

This means projects should be created and maintained in Telaris. Changes and projects created directly in Tripletex are not imported back to Telaris.

This article covers two common support scenarios:

  • Project is not created in Tripletex

  • Duplicate project created in Tripletex


Tip: Always start by checking that the project in Telaris belongs to an object type where «Is Project» is enabled.




Review of common errors


Below you find an explanation, cause, and solution for the most common errors related to project synchronisation with Tripletex.


Guide: Tripletex – Project synchronisation


Project is not created in Tripletex


If a project exists in Telaris but is not created in Tripletex, this is usually because project synchronisation is not enabled, the object is not defined as a project, or Tripletex rejects the creation.

Common causes:

  • Module: Projectsync is not enabled

  • The object type in Telaris does not have «Is Project» enabled

  • The project is deleted or not available in Telaris

  • The project manager is not linked to Tripletex

  • Department or customer is missing a link

  • Tripletex rejects the creation due to a missing field or a duplicate project number

The error may appear as:

  • «Project is not found or deleted»

  • «Export Project Error: X»


How to solve the error:

  1. Go toInnstillinger → Integrasjonsinnstillinger → Tripletex API.

  2. Check thatModule: Projectsyncis enabled.

  3. Check that the project exists in Telaris and is not deleted.

  4. Check that the object's object type hasIs Projectenabled.

  5. Check that the project manager is linked to Tripletex.

  6. Check that any customer and department are linked correctly.

  7. Save the project again, or reference the project from an order/invoice to trigger export.

If the project manager is not linked to Tripletex, the system uses a fallback:

  1. The project's manager

  2. The integration's owner

  3. The API token owner

This means the project normally gets a valid project manager in Tripletex, even if the original manager is not synchronised.


NOTE: Only objects with an object type where «Is Project» is enabled are treated as projects when synchronising to Tripletex.




Duplicate project created


Duplicates usually occur when a project already exists in Tripletex but does not have an integration reference to the project in Telaris.

Project synchronisation does not import projects from Tripletex and does not match automatically against existing projects based on name or number.

When Telaris exports the project for the first time, a new project is therefore created in Tripletex if no integration reference exists.

Common causes:

  • The project was created manually in Tripletex before synchronisation

  • The project exists in both systems but without an integration reference

  • The project was re-created after deletion or incorrect linking

  • The same project number is used in Tripletex and Telaris without the link being set

How to solve the error:

  1. Check which project in Tripletex is correct.

  2. Check which project in Telaris should be the master.

  3. Avoid further editing of the duplicate in Tripletex.

  4. Contact support if an existing Tripletex project must be linked manually to Telaris.

  5. Clean up the duplicate in Tripletex if needed after clarifying with the accounting manager.

There is no function in the interface to link a Telaris project to an existing Tripletex project. Manual linking requires the integration reference to be set directly by a developer or support with the necessary access.


NOTE: Projects should always be created in Telaris first. Projects created directly in Tripletex are not automatically linked back to Telaris.



Summary and further troubleshooting


For problems with Tripletex Project synchronisation, you should always check:

  • That Module: Projectsync is enabled

  • That the object type has «Is Project» enabled

  • That the project exists in Telaris

  • That the project does not already exist in Tripletex without a link

  • That the project manager, customer, and department are linked correctly

In short:

  • If a project is not created: check Projectsync, Is Project, and the required links.

  • If a duplicate is created: the project probably already exists in Tripletex without an integration reference.

If the problem is not solved, check the synchronisation log for a more detailed error message from the Tripletex API.


Tip: To avoid duplicates, Tripletex projects should not be created manually when Telaris is the master for projects.








Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article