can not create index

[badboy-tian]

New Issue Checklist

• [ ] I am not disclosing a vulnerability.
• [ ] I am not just asking a question.
• [x] I have searched through existing issues.
• [ ] I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

can create _created_at index

Steps to reproduce

export const AVFile = {
    className: "AVFile",
    fields: {
        mime_type: {type: "String"},
        key: {type: "String"},
        name: {type: "String"},
        provider: {type: "String"},
        owner: {type: "String"},
        size: {type: "Number"},
        url: {type: "String"},
        objectId: {type: "String"},
    },
    indexes: {
        _AVFile_ownerIndex: {owner: 1},
        _AVFile_createdAtIndex: {_created_at: 1},
        _AVFile_updatedAtIndex: {_updated_at: 1},
        _AVFile_objectId: {objectId: 1},
    },
    classLevelPermissions: {
        find: {},
        count: {},
        get: {},
        update: {},
        create: {},
        delete: {},
        protectedFields: {},
    },
}

Actual Outcome

error: Failed to run migrations: Error during update of schema for type AVFile: ParseError: 102 Field _created_at does not exist, cannot add index

Expected Outcome

success

Environment

Dashboard

• Parse Dashboard version: 5.3.0
• Browser (Safari, Chrome, Firefox, Edge, etc.): chrome
• Browser version: 120.0.6099.109

Server

• Parse Server version: 6.4.0
• Operating system: mac os
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 7.0
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local

Logs

 10:12:07 AM - Found 0 errors. Watching for file changes.
[TS] DATABASE_URI not specified, falling back to localhost.
[TS] databaseUri: mongodb://localhost:27017/dev
[TS] redisUri not specified, falling back to localhost.
[TS] redisUri: redis://localhost:6379
[TS] warn: DeprecationWarning: The Parse Server option 'allowExpiredAuthDataToken' default will change to 'false' in a future version.
[TS] warn: DeprecationWarning: The Parse Server option 'encodeParseObjectInCloudFunction' default will change to 'true' in a future version.
[TS] app: 3.186s
[TS] Node app is running on port: 1337
[TS] info: Running Migrations
[TS] error: Failed to run migrations: Error during update of schema for type AVFile: ParseError: 102 Field _created_at does not exist, cannot add index.
[TS] info: Running Migrations Completed

[parse-github-assistant[bot]]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[badboy-tian]

  _User_objectId: {_id: 1},
        _User_createdAt: {_created_at: 1},
        _User_updatedAt: {_updated_at: 1},

 Failed to run migrations: Error during update of schema for type _User: ParseError: 102 Field _id does not exist, cannot add index.

[badboy-tian]

_User_objectId: {objectId: 1},
        _User_createdAt: {createdAt: 1},
        _User_updatedAt: {updatedAt: 1},

error: Failed to run migrations: Error during update of schema for type _User: ParseError: 102 Field objectId does not exist, cannot add index

[mtrezza]

Please add more details to the issue description. How is this a Parse Dashboard issue?

[mtrezza]

I'm closing this as it does not seem to be a Parse Dashboard issue and no further information has been provided.

• For help with Parse Platform we recommend our community forum or our community chat
• For general coding questions we recommend Stack Overflow using the parse-platform tag
• For network and server questions we recommend ServerFault using the parse-server tag