Feature(s) impacted
Rendering a collection (Profile) that contains a native PostgreSQL enumeration array (Industry[]) using the Forest Admin Node.js agent with Prisma and PostgreSQL.
Observed behavior
After our nightly reset of the staging database (we recreate a fresh PostgreSQL instance every night), navigating to the Profile collection in Forest Admin throws the following error:
TypeError: value.map is not a function
at BinaryCollectionDecorator.convertValueHelper ...
It appears that Forest Admin expects value to be an array, but it isn’t interpreted correctly post-reset — specifically when the field is a native Postgres enum array.
The field in question is defined in our Prisma schema as:
enum Industry {
...
realEstatePropTech
...
}
model Profile {
...
industries Industry[] @default([])
}
To be clear, this Industry enum is a native PostgreSQL enum, declared and used via Prisma.
See attached:
Expected behavior
Forest Admin should support native PostgreSQL enum arrays without issues — even after a full DB instance reset — and should not require a manual redeployment of the agent to function.
Failure Logs
TypeError: value.map is not a function
at BinaryCollectionDecorator.convertValueHelper ...
at BinaryCollectionDecorator.convertValue ...
...
Context
- Project name: Roundtable
- Team name: Roundtable
- Environment name: staging
- Database type: PostgreSQL
- Recent changes: We reset the entire DB instance nightly for a clean test environment
Self-hosted agent info:
- Agent technology: Node.js
- Agent package:
@forestadmin/agent - Agent version: 1.64.0
{
"@forestadmin/agent": "1.64.4",
"@forestadmin/datasource-customizer": "1.67.0",
"@forestadmin/datasource-sql": "1.17.1",
"@forestadmin/datasource-toolkit": "1.50.0",
"@forestadmin/plugin-flattener": "1.4.16",
}
This issue is consistently resolved by redeploying the agent — but that’s not sustainable. We’re looking for insights into what causes this mismatch (maybe a metadata caching issue?) and if there’s a better workaround or permanent fix.
Thanks a lot!