# 🐠 Fibery product report: February 2026

**URL:** <https://community.fibery.io/t/fibery-product-report-february-2026/10513>\
**Category:** News & Announcements\
**Created:** [March 9, 2026, 12:36pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513 "2026-03-09T12:36:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [March 9, 2026, 1:04pm UTC](https://community.fibery.io/t/fibery-product-report-february-2026/10513/3 "2026-03-09T13:04:49Z")

</div>

Thanks for sharing these, as always!

> [@mdubakov](#):
>
> So we took _Show and edit related Entity Fields without a Lookup_:

This sounds really amazing!! Essentially solving this: [Editable Lookup Fields](https://community.fibery.io/t/editable-lookup-fields/8424)

As well better control over permissions. IE: only show the lookup if you have access to the other entity where that field is from. Opens up a lot of power!! I wonder if this could be set by formula? Get field x if a, and get field y if b. Of course, both fields must return the same type of data. It maybe would also allow going deeper into relations using a single field.

> [@mdubakov](#):
>
> If Dima will have time till permissions, we will do _Filter and sort relation selectors in Form View_.

Amazing!! Thank you Dima!

This was a great month, looking forward to the rest March.

---

_[View the full topic](https://community.fibery.io/t/fibery-product-report-february-2026/10513)._