# 🦜 April 2, 2026 / Show Fields from relation without Lookup, AI Integration Agent **URL:** \ **Category:** Changelog\ **Created:** [April 2, 2026, 1:09pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679 "2026-04-02T13:09:40Z")\ **Posts on this page:** 9\ **Page:** 3
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [April 16, 2026, 1:27pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/41 "2026-04-16T13:27:40Z")
Agreed. Really enjoying this one more and more. ---
**Author:** ![bikesupplies](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bikesupplies/32/15290_2.png) [@bikesupplies](https://community.fibery.io/u/bikesupplies)\ **Post date:** [May 22, 2026, 2:43am UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/42 "2026-05-22T02:43:27Z")
These are all fantastic releases. I’ve been trying to build an integration to [Stock&Buy API Reference](https://api.stockandbuy.com/#/) with the AI integration agent and can’t for the life of me get it to work with endpoints which have multiple pages. I’m somewhat technically competent (often write basic python) and was able to set up an app hosted on our own server to do data syncing. I was hoping the agent could make setting up new datastreams easier. Does anyone have any experience with the new integration agent that they could share for newbies? any suggestions for how to do this more easily ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [June 3, 2026, 3:58pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/43 "2026-06-03T15:58:27Z")
I just wanted to say that “Show Fields from relation without Lookup” is one of the best features Fibery has added since multiple entity views! The functionality doesn’t seem to allow the relation’s relation fields to get displayed as “levels” in embedded views though, unless I’m missing something. Can we expect that to come in the future? ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [June 3, 2026, 4:06pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/44 "2026-06-03T16:06:13Z")
> [@interr0bangr](#): > > I just wanted to say that “Show Fields from relation without Lookup” is one of the best features Fibery has added since multiple entity views! Agree with you that’s a good feature. On my use case I a would say that one thing is missing : having the possibility to set the relation field read only. Sometimes I want to use a field from a relation for an informative purpose. In this case, I need to create an additional field (formula). ---
**Author:** ![Eva\_Folch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eva_folch/32/11814_2.png) [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)\ **Post date:** [June 3, 2026, 4:12pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/45 "2026-06-03T16:12:13Z")
In that case, you might want to use a lookup. But I could imagine that if they just added the feature to choose between allowing a change, then the lookup field could disappear… Less clutter in the workspace! ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [June 3, 2026, 4:21pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/46 "2026-06-03T16:21:37Z")
Yes, the idea is to reduce the qty of stuff. I’m not sure about all the use cases that a Lookup can cover but at least, if Read Only is added there, then the Lookup is probably no more necessary, for this use case. ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [June 3, 2026, 4:44pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/47 "2026-06-03T16:44:17Z")
“having the possibility to set the relation field read only” — would be very nice! ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [June 3, 2026, 5:17pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/48 "2026-06-03T17:17:34Z")
> [@interr0bangr](#): > > The functionality doesn’t seem to allow the relation’s relation fields to get displayed as “levels” in embedded views though, unless I’m missing something. > [@Eva\_Folch](#): > > In that case, you might want to use a lookup. But I could imagine that if they just added the feature to choose between allowing a change, then the lookup field could disappear… Less clutter in the workspace! > [@Jonathan1](#): > > Yes, the idea is to reduce the qty of stuff. I’m not sure about all the use cases that a Lookup can cover but at least, if Read Only is added there, then the Lookup is probably no more necessary, for this use case. As a clarification, [lookup fields](https://the.fibery.io/@public/User_Guide/Guide/Lookups-16) and [related fields](https://the.fibery.io/@public/User_Guide/Guide/Fields-on-Views-491/anchor=How-to-show-a-related-Field--ba061ff1-725c-4e50-b91e-d8d56add43c5) have different behaviours which all basically stem from the fundamental difference in how they work technically: - Lookup fields are true backend fields, which belong to the database where they are defined. They behave like formula fields: calculated using a backend service (with a slight latency). A user can query the value of a lookup field via API as well as choosing to show them anywhere the entity can be shown. - Related fields are merely frontend ‘fields’ (that allow visualising field values from a related entity) rather than being true backend fields. When a user chooses to display a related field, the value(s) are being retrieved (from the linked entity) at display time. An API query of an entity does not allow a user to get these values. Hopefully, this explains the differences in behaviour, e.g. why lookups are read-only, and hard to make behave otherwise, even though the two types appear rather similar on the UI. ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [June 3, 2026, 7:37pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/49 "2026-06-03T19:37:16Z")
> [@mdubakov](#): > > 🦜 (beta) AI Integration Agent: Create, test and deploy integrations via chat I tried making a custom integration using WFS _(web feature service - we geo people have our own web service standards, they come from the OGC which is just 6 days younger than the W3C - yes Fibery, you wanted nerds, you get nerds! 😄_ )… using this prompt: > can you make a custom integration with tables for me like the ‘World’ integration, but then with country, provinces, municipalities in the netherlands? > Here is the WFS from PDOK: [Gemeenten](https://service.pdok.nl/kadaster/brk-bestuurlijke-gebieden/wfs/v1_0?request=GetCapabilities&service=WFS) > this contains the necessary data. ~~However, it said it made an integration (and I saw it in the Editor) but I didn’t see one under integrations. I wonder what went wrong.~~ I believe it’s working. Edit: look at the screenshot below. I have 3 levels of administrative divisions - Country, Province, Municipality. It comes from the official data service so when they merge municipalities then I can just sync again. Amazing. ![Screenshot 2026-06-03 at 21.57.44](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3dba22b486e973c1c907eeadb871777774175e43.jpeg) [Previous page](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679.md?page=2)