# Release + Dev versions: JSON export wrong field name (object\_id instead of public\_id)

**URL:** <https://community.datagerry.com/t/release-dev-versions-json-export-wrong-field-name-object-id-instead-of-public-id/713>\
**Category:** Report a Bug\
**Created:** [March 21, 2025, 1:49pm UTC](https://community.datagerry.com/t/release-dev-versions-json-export-wrong-field-name-object-id-instead-of-public-id/713 "2025-03-21T13:49:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmdbeval1](https://avatars.discourse-cdn.com/v4/letter/c/f14d63/32.png) [@cmdbeval1](https://community.datagerry.com/u/cmdbeval1)\
**Post date:** [March 21, 2025, 1:49pm UTC](https://community.datagerry.com/t/release-dev-versions-json-export-wrong-field-name-object-id-instead-of-public-id/713/1 "2025-03-21T13:49:25Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\
**Post date:** [March 21, 2025, 2:52pm UTC](https://community.datagerry.com/t/release-dev-versions-json-export-wrong-field-name-object-id-instead-of-public-id/713/2 "2025-03-21T14:52:55Z")

</div>

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

BR Adnan

---

<div class="post-metadata">

**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\
**Post date:** [March 25, 2025, 10:25am UTC](https://community.datagerry.com/t/release-dev-versions-json-export-wrong-field-name-object-id-instead-of-public-id/713/3 "2025-03-25T10:25:59Z")

</div>

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