UI Rollback issue

Help me!
1

Hello, I’ve recently run into an issue, for some reason, UI keeps rolling back, for example:
I hide Users collection and make Cloudregistrations collection visible.
After I refresh the page these changes get rolled back. This currently applies to any changes I make, like renaming fields, creating segments, whatever. While this is happening changes counter (top bar) still increases.

Furthermore:

	collection.addField('passwordAgeTest', {
		columnType: 'String',
		dependencies: ['createdAt', 'passwordUpdated'],
		getValues: async records => {
			console.log('records', records);

			return records.map(_ => 5);
		},
	});

This code (added after the problem appeared) ONLY triggers when getting (clicking on) a single user (not triggering on a whole collection fetch).
While “passwordAgeTest” field is nowhere to be found in the UI.

Console output:

info: [200] GET /User - 72ms
// ---> Log is missing here <---
info: [200] GET /User/count - 43ms
records [
  {
    createdAt: '2023-04-18T08:35:04.640Z',
    passwordUpdated: '2023-04-18T08:37:06.968Z'
  }
]
info: [200] GET /User/643c563846403s2e9cddbb55 - 62ms

It seems like forest schema is updated correctly on my side, might be some problem with forest servers sync.

Observed behavior

UI changes are not persisted, “addField” triggers ONLY on a single document fetch

Expected behavior

I expect UI changes to persist, and also “addField” should trigger on a whole collection as well as a single document

Context

  • Project name: PayAtt Internal Admin Portal
  • Team name: All teams
  • Environment name: DEVELOPMENT | VLADYSLAVNIKIFOROV (REWRITE)
  • Agent (forest package) name & version: “@forestadmin/agent”: “^1.16.2”, “@forestadmin/datasource-mongoose”: “^1.5.1”
  • Database type: MongoDB
  • Recent changes made on your end if any: Migrating to a new agent
2

Hello @Vladislav and welcome to our community !

We have detected a number of errors happening and already rollbacked the commit causing the issue, you should be able to update your layout and see the changes applied properly.

We are sorry for the inconvenience this has caused.

Best regards,

2 Likes
3

Everything seems to work now! Thanks for the quick response!

3 Likes