I think it would be very useful to have access to nested portals: insert the portal into a portal. Having this would have solved many problems.
You haven't voted on your idea. Sorry, it's not automatic done for you.
Can you explain further? Do you have any graphical representation of how this might be or where you have seen this type of design in any other form ( on web pages perhaps? )
very simple: in a portal I would like to be able to insert an additional portal. Simple example: the lines are simple and automatic. I am in the registry with the portal "invoices" and in the portal "invoices" I have "invoice lines". I am amazed that this is not possible.
Thank you, @grabo, you still have not voted on your own idea.
I understand what you desire. Have you seen this type of thing elsewhere? If so, where and do you have screenshots or links?
I need something like this on a regular basis. Maybe not directly in the visual sense, I would rarely want to squeeze a portal into a row.... But certainly structurally, to support progressive disclosure. Most often I would present this with pop-over buttons. Currently this type of feature requires trickery that could be made simpler.
Here is an example where a sales rep wants to asses the time needed to fill a backorder, right within the context of a portal line. Currently this is not allowed because it would be a Portal > Popover > Portal, which is technically nested portals.
See also Nested portals (portal > popover > portal)
Yep! As well, I see progressive reveals, but not tables within tables. Think List view with Portals <-- UGH! UI/UX. Portals inside portals would be just that. A "portal/view" of a list of related records with another portal in each row. No thank you.
I support the idea being created, but personally will not vote on it. Or I may vote no based on there being nothing for comparison. I just don't see this kind of interface in any app, any web site, any where!
PROGRESSIVE REVEALS, yes
NESTED PORTALS, no
I do not know if it's clear enough ... but imagine a normal invoice with lines that contain more items to justify a portal to manage them. Simply put, you have the table with customer data. From a format of that table insert the portal "invoices" and in the portal "invoices" insert the portal "invoice lines". If you understand this it simplifies very much. Try to imagine how comfortable it is to have nested portals. To solve this kind of problem I had to ask many times in forums how to do it. The solutions have always been effective, but for me they were complicated and I always told everyone that I thought the nested portal was useful.
are 3 tables, but I ask to insert in the first table a portal containing the second and in the portal insert a portal that contains the third ... a nested portal. (keep in mind that I translate with google ...) "Invoice line" are "billing line"
I do this now with INVOICES table (and a layout based upon it) where I show the related CUSTOMER (back) and the related INVOICE ITEMS (the only portal).
This is not a portal in a portal. I can go to customer list, choose to create a new invoice which has the customer id pushed into the new invoice. On the Invoices layout, the portal allows entry of the items.
I do the same for web sites. I do the same with SQL databases and whatever I use to display the data. No need for portal in portal. Just not needed.
a work around
Awesome! repeating fields inside the portal row to 'simulate' the "portal rows" inside the portal row! Another use case for repeating-field-as-display element(s)!
Thank you for sharing oceanwest !
I do not understand everything - for example I did not understand the last speech that refers to something I do not see. However I do not understand why there are difficulties or this possibility is hindered. If I had a nested portal I could register in a portal within a portal without the need for a script. This is my way of thinking, in this case in fact the "invoice lines" in the portal are simple to implement, but I had the case where the registry was the main, I had to fatten in a portal inside "registry" and at the same time I had to generate lines of income within the portal, but it was not the only case. If you provide a possibility, perspectives are open. Of course you can do it in many different ways, but the nested portal would take away the script. Not only that, but I could manage multiple tables through less screens. Personally I do not even know what the votes are for and I do not worry about having them. If my indication received 100 votes would they do it? I hope they do it if it can be done and if it can be useful.
"Scripting" is a part of FileMaker Pro. Doing (or not doing) something because it requires scripting is a little short-sighted. But look at the demo provided by oceanwest to see if this does as you need.
Retrieving data ...