JDisc Connector Add-on: Known issues and solutions

The JDisc Connector Add-on (available since i-doit v36) replaces the classic JDisc integration. This article documents known issues and their solutions.

Sync Profiles not displayed / error message

Symptom: Under "Sync Profiles" a red error message appears instead of the profiles, or the list is empty.

Possible causes:

• GraphQL not enabled: The JDisc Connector Add-on requires an active GraphQL connection to the JDisc server. Check the GraphQL configuration under Discovery Server (port 443, protocol HTTPS).
• Incorrect credentials: The WebService/GraphQL credentials are wrong. Use the "Check GraphQL" button to test the connection.
• Browser error: Open the developer console with F12 and check the "Console" tab for JavaScript errors. This information helps support with diagnosis.

Sync profiles can be created but not opened (json_decode error)

Symptom: A sync profile can be created, but opening the profile or the profile list shows the message "Seems like something went wrong - Please try again by reloading the page." The profile remains selectable when synchronizing an object. The Apache error log contains an entry of the form:

PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, null given in .../synetics_jdisc/src/Model/JDiscProfileDao.php

Cause: When an object type assignment is saved in a profile without a port filter, the corresponding database fields remain empty (NULL). When the profile list is displayed, these fields are read and trigger the error.

Solution: Set the empty port filter fields to an empty value. Please create a backup beforehand. You can find the database credentials (user, database name) in the config.inc.php of your i-doit installation; adjust the user and database name in the following commands accordingly.

mysql -u idoit -p idoit_data -e "UPDATE isys_jdisc_object_type_assignment SET isys_jdisc_object_type_assignment__port_filter_type = '[]' WHERE isys_jdisc_object_type_assignment__port_filter_type IS NULL;"

mysql -u idoit -p idoit_data -e "UPDATE isys_jdisc_object_type_assignment SET isys_jdisc_object_type_assignment__port_filter = '[]' WHERE isys_jdisc_object_type_assignment__port_filter IS NULL;"

After running these, the affected profiles can be opened and edited again. A permanent fix is planned for an upcoming version of the JDisc Connector Add-on.

JDisc Connector Add-on not visible in menu

Symptom: After installing the add-on, no menu item appears.

Solution: The affected user needs permissions for the JDisc Connector Add-on. Under Administration > Permissions there is a dedicated section for the JDisc Connector Add-on with granular permissions (Dashboard, Device List, Sync Profiles, Discovery Server, Logs, Console Commands).

Import settings are overwritten

Symptom: Configured settings in the Sync Profile are reset to default values after saving.

Status: Known issue, escalated to the development team. As a workaround, export the profile and save the configuration locally.

Profile filters are lost

Symptom: Filters configured in Sync Profiles are not correctly applied after saving.

Status: Known issue, escalated to the development team.

Device list shows no devices

Symptom: The device list in the JDisc Connector Add-on is empty.

Possible causes:

• No GraphQL connection: The device list requires an active GraphQL connection. Use the "Check GraphQL" button under "Discovery Server".
• JDisc Discovery not executed: No devices have been scanned yet. Start a discovery run or verify that the JDisc server contains devices.

Migration from classic integration

When installing the JDisc Connector Add-on, existing JDisc profiles are automatically migrated to Sync Profiles. This process is irreversible. The classic JDisc integration remains available for up to 2 versions after v36 if the add-on is not installed.

Detailed documentation: JDisc Connector Add-on in the Knowledge Base