How long have you had this issue?
I developed this about a month ago and I am facing this issue since the start.
3.
Could you share your calculated field source code please?
collection.addField('full_name', {
// Create calculated field by concatenating two fields
columnType: 'String',
dependencies: ['profile@@@firstName', 'profile@@@lastName'],
getValues: (records, context) => {
return records.map(r => `${r['profile@@@firstName']} ${r['profile@@@lastName']}`);
}
});
Could you check your network requests and check if there are a “null null” values?
It’s null in network calls. I have attached the screenshot below. The first object is from “data” array and then starts the included array.
What i have tried so far:
- Could you please also focus on the fact that if I click on this “null null”, I am redirected to the correct user details page and when I come back to this listing page (without refreshing anything), I can see the actual full name of the user.
- I have also tried changing the reference field to first_name (not a calculated field), still the issue I mentioned in the first point is not resolved. The only difference it made was instead of null, it displayed ID of the record which was replaced by the actual value later after I visited the user details.
- I have also checked the other tables where users table is referenced, and the full_name is shown correctly
- Forest admin schema file also shows correct relationship between Users and Emails table