parse-community / parse-community/parse-dashboard
Unable to edit an objectId / create a new objectId on the dashboard
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
I have a server that allows for custom objectIds, I am unable to enter an objectId when creating a new row, nor am I able to edit an objectId of an existing row.
Steps to reproduce
- Create a new row in any given object
- Attempt to enter the objectId you want
-or-
- Edit an existing row
- Attempt to edit/change the objectid
Actual Outcome
It is completely uneditable this pops up with no ability to edit said id.
Expected Outcome
For me to be able to edit it in some way shape or form
Environment
Dashboard
- Parse Dashboard version: 8.1.0
- Browser (Safari, Chrome, Firefox, Edge, etc.): Safari
- Browser version: 26.2
Server
- Parse Server version: 8.4.0
- Operating system: macOS 15.7.3
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local
Database
- System (MongoDB or Postgres): MongoDB
- Database version: 8.2.0
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local
Logs
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Parse Dashboard 8.1.0 with Parse Server 8.4.0 and MongoDB 8.2.0, using Safari as reported. Check both creating a row with a custom objectId and editing an existing objectId; done means both actions allow the requested ID without the reported blocking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100