Smart collection display broken with v8?

[alex42]

Hello guys,

I’m new on ForestAdmin and I’m loving the projet, very nice work guys!

I’m trying to setup this feature (Display and edit MongoDB array as virtual collection - Developer guide) but it’s seems broken with the forest-express-mongoose v8.0.0…

Here is my code:

const { collectionName } = require('../models');
const testRecordGetter = new RecordGetter(collectionName);

And I get this error

Any ideas?

Thanks,
Alex

[morganperre]

Hello @alex42 ! Welcome to our community

This example wasn’t update to the last version.
The forest-express-mongoose v8.X introduce a breaking change on RecordGetter.

You should instantiate the RecordGetter with more informations.

const { query, user } = request;
new RecordGetter(collectionName, user, query)

Let me know if it helps. In the meanwhile I will communicate to the team to update the documentation.

Kind regards,
Morgan

[alex42]

Hello @morganperre,

Thanks a lot for your fast reply, it’s worked!!!

But now when I’m trying to update a nested element (using: Display and edit MongoDB array as virtual collection - Developer guide)

I’m using the findById function

It’s seems that the findById does not return the nested data (steps array in my case)

When I’m using collectionRecordGetter.get, I’m able to get the steps but the record.save() function is undefined…

Any trought?

Thanks a lot,
Alex

[morganperre]

Hey again,

@alex42

I’m using the findById function

You’re directly using mongoose findById fonction. Your behaviour seems weird but If you need to do something really custom you should look directly at the mongoose documentation.

@alex42

When I’m using collectionRecordGetter.get , I’m able to get the steps but the record.save() function is undefined…

If you want to update records you can either use custom mongoose implementation (example: findById/find/findOne+ record.save) (you can also use collection.update) or use the RecordUpdater that is in the forest-express-mongoose library, you can find some example in our documentation.

Kind regards,
Morgan