Documentation/ Purchase orders and projects/ Projects
Projects: what they are and what they are for
A project is a free label documents are classified with: a job, a site, a client, a department, a campaign. They are optional, but they are how you answer the question of where the money has gone.
Management › Projects
On this page
What they are
The application's own guide describes them as optional but the best way to organise your information, letting you create categories, sites, companies, clients and more to classify things by.
In other words, the application does not dictate what a project stands for. That decision is yours, and whether the classification turns out to be any use depends on it.
| Kind of business | What a project usually is |
|---|---|
| Construction | Each job. |
| Hospitality or retail with several sites | Each site. |
| Accountancy practice | Each client you handle. |
| Services | Each engagement or campaign. |
| Manufacturing | Each production line or centre. |
The guide points one case out expressly: for an accountancy practice, projects are ideal for handling several clients in a single Dijit account.
What they are used for
- Filtering the document lists by project, to see only one job's or one site's documents.
- Filtering the dashboard, to see one project's figures.
- Keeping work apart when one account handles several different realities.
- On some ERP destinations, as a required field of the sending.
Creating a project
The guide sums it up in a line: go to the Projects module, press New, enter a code or name and, optionally, a description.
- Press New.
- Type the project's name. It is what will show in the drop-downs.
- Add a description if it helps identify it.
- Save.
There is no limit on projects. The guide says as much: you can create as many as you need, with no maximum set.
To create a lot at once there is a quicker route: generating them from your suppliers, recipients or companies.
The list
| Column | What it holds |
|---|---|
| Name | The project's name. Can be sorted. |
| Description | The free text attached. |
| Origin | Where it came from: created by hand, or generated from a supplier, recipient or company. |
| Linked to | The particular record it is linked with, where it has one. |
The Guide button at the top opens the step-by-step explanation inside the application itself.
Linking a project to a record
A project can be linked to a supplier, a recipient or a company. The screen makes the scope clear: it links this project with one of them, and the project's name and description do not change.
The link is one to one: if another project is already linked to that record, the application refuses and asks you to unlink it first.
You can also choose no link, which is the normal case for projects that do not stand for anybody, a job, a campaign.
Projects do not carry down to the lines
This is the limitation to know about. The guide says it outright: the project assigned to a document's header is not inherited automatically by its lines. If you need a particular item to have a project, it has to be given to it by hand on that line.
The practical consequence: for a report of spend by project at document level, the header is enough. To split one document between two projects, you have to go down to the lines.
Deleting projects
Several can be ticked and deleted at once. The confirmation says how many and that it cannot be undone, and the result says how many were deleted and how many were not.
A project with documents assigned cannot be deleted from the screen. The guide points you to support to have it handled safely, precisely because deleting it would leave those documents unclassified.
Things that come up
| What you see | Why | What to do |
|---|---|---|
| A project will not delete | It has documents assigned. | Get in touch with support so it is handled without orphaning documents. |
| Spend by project comes out incomplete | Some documents have no project assigned. | Assign it in bulk from the document list. |
| A document's lines have no project | The header's project is not inherited. | Assign it line by line if you need that level of detail. |
| It will not let you link a project to a supplier | Another project is already linked to that record. | Unlink the other one first. |
| There are too many projects and they are hard to find | They were created with no plan behind them. | Delete the ones with no documents and bring the rest together. |