Forest Admin UI and deployments.
Recently I have made many changes to the names of models, smart fields and enums. The
.forestadmin-schema.json is successful updating on builds, however, the Forest Admin UI is referencing tables and fields that no longer exist (in the schema and in our database). For example, the Collection
DbLateFeeConfigs no longer exists in the schema but still appears as a Collection.
For more context, this issue appeared locally. After about 5 restarts of the local environment, the issue seemed to fix itself. But the issue is still being found on our hosted Staging environment, and ideally we would not like to have to restart it more times than needed.
.forestadmin-schema.json is updated, then changes should appear on the UI.
- Project name: Bridgement.1
- Team name: Bridgement
- Environment name: DEVELOPMENT and STAGING
- Agent (forest package) name & version:
- Database type: Postgres
- Recent changes made on your end if any: Many changes were made that affected the