These are for views inside Entities only
1 Like
These are for views inside Entities only
that makes so much more sense 
Thanks, good to know! 
I’ve tested your solution and it works! That is great, now I can do everything I want to do for my client! 
And good to know that you’ll think about better url schemas.
Great work as always, thx!
1 Like
Yes, we embed the custom app as an iframe in our “Portal” app. That’s the exact case that triggers it: clicking the doc link from inside the Portal iframe does absolutely nothing unless we add our own manual fallback to catch the rejection and open a new tab ourselves.
I also rolled back to a the first version and retested standalone access (pasting the app’s URL directly into a fresh tab, no Portal involved) and can confirm that one works as you described — the entity opens correctly there. It’s specifically the Portal-iframe case that fails.
Portal is our primary navigation path for every custom app in the workspace, so that’s the scenario that would make the biggest impact for us. Thanks for digging into it!
1 Like
Great update — background refresh was actually going to be my next request, so this is fantastic!
I’m not quite following what’s being discussed here — could someone explain with a video? I built a dashboard app, and for me, entities have always opened in a new tab when clicked. Maybe I’m missing something?
I’m on the standard plan, so I can only put the app in the private space. But I don’t really use the private space, since I work solo. So instead, I embedded the app in a page. The issue is that doing this also opens the app’s own left sidebar, which means I end up with two sidebars — and I have to keep closing the extra one. (I prefer working with my sidebar open.) Is there any way to fix that?
Also — I’ve seen it mentioned that apps might be made open to the world at some point. I’m guessing that’s not possible right now unless you’re on the Pro plan? I’m currently using forms for proposal inquiries, but they’re not very customizable and end up looking a bit unprofessional on my website. I was thinking an app could be a nice way to build a proper form page instead — but I assume I still wouldn’t be able to share it publicly, right?
Thanks to the Team for the amazing work!
1 Like
I have not tested it yet Eva but I believe it means it opens in a panel instead of a tab, meaning a section/box on the screen that contains information or controls - in this case about an entity:
┌─────────────────────────────────────┐
│ Header │
├───────────┬─────────────────────────┤
│ Navigation│ Main Content │
│ Panel │ │
│ │ ┌─────────────────┐ │
│ • Home │ │ Settings Panel │ │
│ • Profile │ │ Notifications │ │
│ • Help │ │ Account │ │
│ │ └─────────────────┘ │
└───────────┴─────────────────────────┘
So you don’t have to switch from tab to tab, so less context switching, so less cognitive load.
I have to run, your other questions I will look into later or someone can!
Ah, then no — mine don’t open in a panel, I can’t get that to work. Not from the embedded app view, and not from the app itself either.
By the way, am I the only one who’d love to see the divider between panels become draggable, so you could resize one panel to be bigger or smaller? Like Notion does.
2 Likes
can i fix this problem with fibery?
I currently use Google Sheets to track my sales and rentals. Right now, I type everything into one single cell: the customer’s name, contact number, notes, and the rental period. Sometimes the customer rents the product, sometimes they buy it permanently, and sometimes they’ve taken the product but haven’t paid yet. Keeping all this logged in a single cell is just very comfortable and fast for my workflow.
However, I want to upgrade this to a more structured system without losing that “single-cell” convenience. Here is exactly what I am trying to achieve inside one single cell:
-
Customer Name: Formatted as a tag/chip. If I click it, it should open a card/page with their other details (phone, etc.).
-
Due Date: Clickable, so I can easily change the deadline from a calendar pop-up.
-
Status Tags: Labels like “Rental” or “Permanent”.
I also need to be able to filter my entire database based on these specific tags.
I know Airtable is great as a relational database, but it doesn’t seem to support this exact structure. In Airtable, you can’t combine a lookup, notes, and a functional date all inside one single field.
I think you may want to consider thinking about this in 2 ways: a UI problem (‘single cell’ interaction) and a data problem (structured relationships).
It would be fairly trivial in Fibery to setup the data structure as relational databases — this has all sorts of advantages including data accuracy, reporting, etc. — I won’t re-hash this here because it’s probably as easy as taking the description you just wrote and ask Fibery AI to build you a space … just leave out the ‘single cell’ requirement for this part.
Then, create a custom app (again, by just explaining to AI — even uploading a sketch of an example of how you want it to look — which works really well) that allows you to interact with the data with what ‘feels like’ a ‘single cell’. The UI can create that feel and the app can handle interacting with the Fibery data structure in the background.
Yes — you can have your cake and eat it too in this case!
2 Likes
I’ve deployed the fix. Now Entity should open normally in new tab when you embed App as an iframe
2 Likes
Thank you!! Just tried it out, and it looks like it’s working! Much appreciated.