Reference field show id when text is set from table


A user showed me a strange bug today regarding reference field. It has been working smoothly, but suddenly today many reference fields displayed the id of the table instead of the name. The user gets confused becouse the ids of the numbers are much harder to understand than the name.

Feature(s) impacted

Reference field.
When looking into the problem I also see that the permission tab had turned of many permissions for the role opperations. I toggled them back on again, but it indicates to me that there is a strange bug somehow.

Observed behavior

Expected behavior

reference field

it should show the company_name and not the id in table and other views:
Image 2023-12-18 at 11.25.30 AM

Failure Logs

When I look at the network calls I observe that it looks to get the id as number from the backend and not the company_name.
Image 2023-12-18 at 11.28.00 AM


  • Project name: FORE
  • Team name: AFcode
  • Environment name: Production
  • Agent (forest package) name & version: 9.3.3
  • Database type: Microsoft sql server
  • Recent changes made on your end if any: no recent changes before bug was reported.

Hello @larssbr ,
If found that vessel owner should refer to the “vesselOwnerId” model, and not “company”, and the vesselOwerId model does not have any reference field set.
Can you check if that’s the case ?

Hello @Enki.

That is not the case at was working fine before and that it has this relationship allready.
Also there is multiple relationshipst that are affected. As in the failure logs above a contractor is a company.
Image 2023-12-18 at 2.01.05 PM
My guess is that there is a code change that had side effects.
Could you look into that?

These columns seem unrelated to the “company” model.

The 14/12, a schema has been pushed on your project that did not contain some collections (contractorId, vesselOwner, developerId).
the customisations linked to these collections has been lost at that time.
Yesterday, you seem to have fallback to the old schema, recreating these collections.

The layout configuration for these collections need to be recreated manually.

The 2 different schemas that have been pushed come from 2 different agents, with not the same version. There should be only one agent for each environment, maybe check that the environment variables of your agents are well defined, especially the FOREST_ENV_SECRET that should be unique to link one agent with one environment.


Thank you @Enki!

You are correct, to revert that commit solved it :see_no_evil:.
Have a great day and thank you for your help!


Glad to help you !

Have a nice evening