Home
General
Error when uploading JSON configuration

Error when uploading JSON configurationSolved

Participant

11 hours ago

Hey people, I’m running into a weird issue in the Hexnode portal. I‘m trying to upload a JSON configuration file into one of my existing policies, but every time I try to save or upload it, I get a JavaScript error that pops up on the screen.

The exact error is: TypeError: Cannot read properties of undefined (reading ‘id’)

The frustrating part is that this exact JSON file worked perfectly fine previously, and I haven’t made any changes to the code itself. Has anyone seen this error before or know what might be causing it?

Replies (1)

Marked SolutionPending Review

kylian_parker

Hexnode Expert

5 hours ago

Marked SolutionPending Review

@carter, thanks for bringing this up! Since you mentioned that the JSON file worked previously without any changes to the code, it’s highly possible that the error is related to how your browser is rendering the current policy session, rather than an issue with the JSON content itself.

To help us isolate the exact cause, please try the following troubleshooting steps when you have a moment:

Incognito/Private Window: Try doing the upload in an Incognito/Private window, or clear your browser cache. This ensures that no cached session data is interfering with the portal’s scripts.

Test in a Fresh Policy: Attempt to upload the exact same JSON into a brand-new, completely blank policy. If it works there, the issue likely lies in a conflict with an existing setting (such as a Wi-Fi configuration) in your original policy.

Manual Verification: As a general rule of thumb, if a script or configuration runs successfully when executed manually directly on a device, it is perfectly compatible with Hexnode. If it fails specifically during the portal upload process, it helps us pinpoint a potential console-side glitch.

Give those a try. If the fresh policy or incognito mode resolves it, you should be good to go. If it’s still throwing that error, please reach out to our support team directly so we can investigate the console behavior further.