Documentation/ ERP integrations/ Integration parameters
Integration parameters: where they are set
The keys, the servers and the settings for each integration live on a single screen: Parameters. They are grouped by program, and each group only appears if that integration is switched on for the company.
Account › Parameters
On this page
The groups you may see
| Group | What it sets up |
|---|---|
| SAP | The connection details for SAP. |
| Ágora POS | The connection to Ágora and the status documents are posted with. What goes in each field: Ágora. |
| ICG | The connection to ICG. |
| ICG — database | The access details for the ICG database. |
| Diagram | The connection to Diagram. |
| Holded | The Holded API key and whether the PDF is attached. |
Only the groups for the integrations switched on appear. A company with Ágora sees the Ágora block and nothing else.
Integrations that work by file export, Contasol, a3, Cegid, Monitor, have no parameters: there is no connection to set up, only a button that downloads.
The kinds of field
| Kind | How it looks | Used for |
|---|---|---|
| Text | An ordinary field. | Server, user, codes, references. |
| Password | Hidden behind dots. | Keys and passwords. What is stored is not shown. |
| Switch | On or off. | Options about how things behave. |
Password fields do not show the stored value, for safety. To change one, type the new value over it; leaving it empty keeps what was there.
Saving
The screen saves every group at once. Changes take no effect until you save, and there is no automatic saving.
Testing the connection
The Holded group includes a Test connection button, with a warning worth reading:
It checks the key already saved. If you have just pasted one, save before testing. The button does not test what is typed on screen, it tests what is stored. It is this screen's commonest confusion.
The test comes back with a specific diagnosis:
| Answer | What to do |
|---|---|
| The connection works | Nothing. You can start sending. |
| The API key is missing | No key is stored. Paste it and save. |
| The key is rejected | It was copied wrongly or has been revoked. Get it from the other program again. |
| The integration is not switched on for this company | It has not been set up. Write to support. |
| The call quota has run out | The other program's hourly request limit. Wait. |
The switches
Some settings are about behaviour rather than connections. Two examples you come across:
- In Ágora, the status documents are posted with: draft or posted. The switch shows the two labels rather than a yes and a no.
- In Holded, whether the original PDF is attached to the invoice. This one is on by default where it has never been touched.
Who sets them up
It is not a screen for daily use. The connection details are normally filled in by whoever administers the ERP, with help from the Dijit.app team when the integration is set up.
Once in place, they do not need touching again unless the other program's credentials change.
When they get filled in
- When the integration is set up. Support switches it on and the parameters are configured.
- When the other program renews its keys. A revoked API key makes every sending fail until it is replaced.
- On a change of server in on-premise installations.
Things that come up
| What you see | Why | What to do |
|---|---|---|
| The connection test fails after pasting the key | It tests the stored key, not the typed one. | Save first and test afterwards. |
| My ERP's group is not there | The integration is not switched on, or it is one of the file-export ones. | Check with support. |
| The password looks empty | Password fields do not show what is stored. | Normal. Leaving it empty keeps the previous value. |
| Sendings started failing all at once | The other program's key was revoked or expired. | Get a new key, paste it, save and test. |
| A parameter was changed and had no effect | The screen was not saved. | Go back in and check the value is stored. |