Release + Dev versions: JSON export wrong field name (object_id instead of public_id)

Report a Bug
1

Configuration: Debian 12.12, MongoDB 7, Datagerry 2.2.0 (till current dev)
Connection using HTTPS with Apache2 as reverse proxy

Up until the newest Dev version (2025-03-21) there is a continuous error (feature?) that
the JSON export writes the name “object_id” in the JSON instead of “public_id”

This makes the JSON export completely unusable to UPDATE an existing object, as the match is done
via the field “public_id”. A field “object_id” does not exist!

This bug is reproducible.

Workaround: Replace all occurrences of “object_id” with “public_id” and try the import again. For existing
objects with a matching public_id those objects should now be UPDATED instead of newly created.

Please fix permanently.

2

Hi @cmdbeval1,
we will have a look at it, thanks for the feedback.

BR Adnan

3

Hi @cmdbeval1 ,
wie the newest dev version the public_id is nolonger mapped on object_id and will stay public_id (issue also fixed for other formats).

BR Adnan