Everyday workflows
Viewing & editing documents
Explore BSON values, edit properties, save changes, insert documents and duplicate existing data.
Inspect a document
Query results appear in a table. Expand a row to see its BSON fields, then expand objects or arrays as needed. Type badges and value colours distinguish strings, numbers, dates, IDs and containers. Table columns can be pinned, reordered and resized.
Right-click a field for copy and editing actions. Date presentation, property order, string quote markers and object summaries can be adjusted under Settings → Documents. These display preferences do not rewrite stored values.
Click or Tab into the results to use the keyboard: ↑/↓ move through visible document and property rows and scroll them into view. → expands a row, or enters its children when already expanded; ← collapses it, or returns to its parent. Press Enter on a field or table cell to quick edit, or on a document row to open its document editor. These shortcuts also work across large, virtualized result pages.
Edit a property
- Run a collection query with an empty server projection
{}. - Double-click a supported scalar value in the table or expanded fields, or focus its cell/field row and press Enter, to edit it in place.
- Enter the new value. Press Enter or move focus away to apply valid input; press Escape to cancel it.
Inline editing retains the BSON type. Complex values use a source popup; you can also right-click and choose Edit value. Edit the value, then choose Done. Invalid input remains editable with an explanation.
The root _id is immutable. View, aggregation and Shell results are read-only; open the underlying collection in a normal query tab to edit its documents.
Editing legacy UUIDs
Values marked luuid are legacy UUIDs (binary subtype 3). In inline and property-popup editors, a plain GUID or LUUID("…") uses your legacy UUID preference. Use CSUUID(), JUUID() or PYUUID() to override it. Both editors accept lowercase names and unquoted shorthand such as pyuuid(00112233-4455-6677-8899-aabbccddeeff).
In full-document source, quote the argument: PYUUID("00112233-4455-6677-8899-aabbccddeeff"). Generated source and copied legacy values use explicit constructors so they preserve bytes even with a different default. The JSON viewer's default BSON constructors format also uses explicit helpers; its Extended JSON formats preserve the original base64 and subtype. Changing your preference alone never rewrites stored values.
Edit full-range BSON dates
BSON dates outside the ISO calendar range retain their exact signed-64-bit epoch milliseconds. Palryn displays and edits them as DateMillis("9223372036854775807"); inline date editing also accepts the millisecond integer directly. This is a Palryn-specific source helper, not a JavaScript date constructor. Use canonical Extended JSON {"$date":{"$numberLong":"9223372036854775807"}} when exchanging these dates with other tools. Calendar controls support years 0001–9999; use text editing for dates outside that range.
Edit MD5 digests
Sixteen-byte binary subtype-5 values display as 32 lowercase hexadecimal digits with an md5 badge. Inline and property-popup editors accept plain hex, MD5("d41d8cd98f00b204e9800998ecf8427e"), or shorthand such as md5(d41d8cd98f00b204e9800998ecf8427e). Full-document source requires quoted arguments. These helpers encode an existing digest; they do not hash text.
Copied digest values, generated source and the JSON viewer's BSON constructors format retain the MD5() constructor. Extended JSON uses the original bytes and subtype 5. Values with other byte lengths stay generic binary. Digest colours can be customized under Settings → Value colours.
Understand when changes are saved
Immediate save is enabled by default for property edits. Completing a valid property edit writes that document. Each expanded document has an Edit document pencil icon and a labelled Immediate save switch at the top right. The lightning icon and switch position/colour indicate the save mode; hover for details. Switching modes does not save pending changes. Settings → Documents controls the default.
With Immediate save off, changed fields have unsaved markers. Choose Save Changes to save the document's pending edits together, or Discard Changes to restore the loaded values. Turning Immediate save on does not itself save; the next completed property edit includes any other pending edits to that document.
Full-document source editing has an explicit Save action that writes immediately, regardless of the property-edit setting. Use the optional original/proposed preview to compare the draft before saving.
Drafts are memory-only. The Unsaved documents list can recover pending edits after navigation or a query rerun, but they do not survive an application restart. Remember workspace state saves query drafts, not unsaved document contents.
Insert or duplicate
Choose Insert document… from the collection menu or the action above query results. Enter one document object:
{
name: "Example customer",
active: true,
createdAt: ISODate("2026-09-27T09:00:00Z"),
creditLimit: Decimal128("1250.00")
}
Omit _id for a generated ObjectId, or provide your own valid ID. Choose Insert document to write. The current query filter does not add fields to your inserted document.
To start from existing data, right-click a complete result row and choose Duplicate document…. The new draft omits only the root _id. Review other unique fields before inserting; nested IDs remain intact.
After insertion, rerun the query to recalculate matching rows and ordering. A newly inserted document may not match the current filter.
Rename fields and apply wider changes
Use Rename property from a field's context menu to change its name. Property editors also expose wider scopes where the operation is supported: All documents matching the query or All documents in the collection.
Choose the scope deliberately, review the generated operation and matching count, then confirm the bulk action. A query-wide change is not limited to the currently loaded page. Availability depends on the field path and pending edits. Bulk operations are not a multi-document transaction, and another client may change matching data between counting and execution.
Delete and handle conflicts
Right-click a full, unprojected result row and choose Delete document. Review the connection, collection and ID in the confirmation before deleting. Save or discard local changes to that document first.
Palryn checks the original document snapshot when saving or deleting. A conflict means the server document no longer matches it. An unknown outcome means the write may have reached MongoDB but could not be confirmed. Keep the draft for reference and inspect a fresh query before deciding what to do next; these outcomes are not automatically retried.