Forest admin cannot access to the newly created collection where the error message is shown as the image 403 Forbidden. It is only affected to the new collection. Is there any ways that can solve it?
“meta”: {
“liana”: “forest-nodejs-agent”,
“liana_version”: “1.29.0”,
“liana_features”: null,
“stack”: {“engine”: “nodejs”, “engine_version”: “18.14.0”}
}
Hi @Simon_Chen ,
Could you please share the following information with us:
What is the schema of your new collection ?
Best regards,
Shohan
Sure, here are the information needed
Project name: Durian
Team name: Operations
Environment name: Production
Agent (forest package) name & version: "@forestadmin/agent": "^1.16.2",
Database type: PostgreSQL
I am using the automatic schema generation. This is what I can find in forestadmin-schema.json regarding the new collection schema
{
"actions": [],
"fields": [
{
"defaultValue": null,
"enums": [],
"field": "commission",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "Number",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "date",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "Number",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "month",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "String",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "no",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": true,
"isReadOnly": true,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "Number",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "type",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "String",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "uid",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "Number",
"validations": []
},
{
"defaultValue": null,
"enums": [],
"field": "year",
"integration": null,
"inverseOf": null,
"isFilterable": true,
"isPrimaryKey": false,
"isReadOnly": false,
"isRequired": false,
"isSortable": true,
"isVirtual": false,
"reference": null,
"type": "String",
"validations": [ ]
}
],
"icon": null,
"integration": null,
"isReadOnly": false,
"isSearchable": true,
"isVirtual": false,
"name": "commission_report",
"onlyForRelationships": false,
"paginationType": "page",
"segments": []
},```I can see other errors in console above in your image.
Can you share the other logs from your browser ?
Do you have any error on your agent as well ?
Regards,
Shohan
Can you check your roles and see if you have read this collection ?
I cannot see any issue on my end.
Could you please restart your agent ?
Also, do you have your default permissions at true for the new collections ? Or did you change the roles manually ?
Best regards,
Shohan
I have restarted few times before this, its still same. Yes I have the permission true for the new collection and I didn’t change the role at all.
Just my assumption, is there any limits for the number of collections in a project?
No there is it is no limitation for the number of collections.
Could you please try to disable and re-enable the permissions for this collection?
Nice!!! , it works now by just disable and re-enable it.
