As for your first issue, ForestAdmin does not support default values for reference fields in their smart actions forms. If that’s really something you need, I can make an entry in our board for future priorization.
Same goes for filtered references. The reference field only state the target collection’s primary key, no scopes are taken into account in the process. I can also make an entry for that.
However, if you really need to scope this reference field select, I may have two workarounds (both having drawbacks):
- The first one consist of making the comparison after the validation on the
forest_items_clone function. That way you could send back a message stating that this entry isn’t a valid one. But as stated the drawback here is that you check it after pressing the
Clone item button, which isn’t a great flow.
- The second one would be to define your own smart collection which would be a scoped copy of the targeted table (by filtering directly in the get). That way, making the reference points to this newly created smart collection, you would ensure a scoped list.
However, let’s be transparent, this last workaround will not be easy to implement and probably hard to maintain too.
Anyway, I hope my answer will help you!