Documentation/ ERP integrations/ Other programs
Other programs: exporting to Excel
If your management program is not among the integrations available, the data still comes out: almost every table in the application exports to Excel. And if your program is a common one, an integration can be looked at.
Any list › the export action
On this page
The position
Dijit.app has an integration of its own with a specific set of programs. With the rest, data goes out through Excel and loading into the other program is done by hand or through its own importer.
| With an integration | Without one |
|---|---|
| A specific send or export button. | A general export to Excel. |
| The format that program expects. | A spreadsheet format, which can be adapted. |
| Validation beforehand on direct sendings. | None. |
Exporting to Excel
The document lists and the master screens offer an export to a spreadsheet. The behaviour is the same on all of them:
- With rows ticked, it exports just those.
- With nothing ticked, it exports whatever matches the filters or search in force.
- The download includes every field, not only the visible columns.
Combined with the filters, that lets you pull out exactly the set you need: a period, a supplier, a project, a status.
What can be exported
| Screen | What comes out |
|---|---|
| Document lists | The documents with their header details. |
| Product master | Each item's complete record. |
| Supplier and client masters | The records with their details and their accounts. |
| Chart of accounts | The accounts. |
| Product categories | The classification tree. |
| External catalogue | Your own trade references. |
Preparing the file for your program
The general export is in no particular program's format. To load it into yours, the usual course is:
- Export the filtered set.
- Reorder and rename the columns to suit what your importer expects.
- Check the delicate formats: dates, decimals, and codes beginning with a zero, which Excel eats if it treats the column as a number.
- Import into your program.
Worth building the transformation once, with a template sheet, rather than redoing it every month.
Asking for an integration
The application's own answer to this question is direct: if your program is a common one, tell us and we will look at it.
For the request to be useful, worth including:
- The program's name and version.
- Whether it has an interface or only file imports.
- An example of the file your program imports, if it is documented.
- Your monthly volume of documents.
The programs named at sign-up
The sign-up form lets you say which management program you use. Naming it does not switch the integration on by itself: it is so the team knows what needs preparing.
Actually switching it on is done by support, company by company. Until then, that integration's buttons do not appear in the application.
Things that come up
| What you see | Why | What to do |
|---|---|---|
| The ERP was named at sign-up and the button is not there | Naming it does not switch the integration on. | Ask support to switch it on. |
| The export brings more rows than expected | No rows were ticked and everything filtered was exported. | Tick the rows, or narrow the filters before exporting. |
| The codes lose their leading zero | Excel treats them as numbers. | Format those columns as text before saving. |
| The other program's importer rejects the file | The columns do not have the names or the order it expects. | Transform it with a template of your own. |
| The transformation has to be repeated every month | It is done by hand each time. | Build the template once and reuse it. |