Hello, Lorenzo,

Interesting ) I think I know the reason. Could be nice to see Excel file itself, but here is a suggestion. When you export data, your job has some Id, and job tasks have some IDs. After you delete a job from database, those IDs are not valid anymore. To correctly import data back, you have to erase ID for a job, and for each individual job task in Excel file. Also, reference from job task to job should also be changed, as you change job number. Like this:

I believe it must work )

Hi Eugene,

Thanks for the explanation.

Using your explanation, the import does work!

However, I just discovered that when I was trying to import the file, I imported the wrong job tasks to the wrong job.

In my case the translation job cell of each task was 1291/18/06/2020, and TBM imported those tasks to job 1291.

I like the export/import function because it would allow a user to keep templates, or to put away for later jobs "waiting for approval" without them showing up in the list, or to exchange jobs with others, but this issue of the tasks being applied to the wrong job is dangerous.

It would be nice if TBM could just recreate it automatically

Thanks for the clarification

Lorenzo

Hello, Lorenzo,

Agree that it could lead to unexpected results or broken data. But it's not easy to implement some protections (like in your example with importing tasks into a wrong job), for 2 following reasons:

1. Excel file may contain data about many jobs, and Tasks part could contain many tasks linked with different jobs. So, it's not possible to programmatically re-create a link.

2. This functionality is universal, and works in the same manner for all tables in TBM.

So, to create a template, and then use it when needed, it's better to clear sensitive values and then fill them before importing.

Just thoughts, maybe possible to find some solution...

To put a job on hold, I just change the status to "on hold" and apply a filter so those jobs aren't displayed.

Wouldn't that work for you, Lorenzo Martinelli?

Hi Emma,

Maybe. It would affect some view filters and some reports I have...

But in that specific instance, I exported the job because I wanted to keep track of some unusual tasks and counts and notes to refer to in a possible, rather than plausible, future.

Lorenzo