Hello everyone,

i have to sort many portal on the same layout.

My idea is to use one field for the table display in the portal.

In the script i display layout with table used in portal, sort and then replace field content by serial.

Then go back to the main windows and the portal is sort.

What do you think about that ? is there a better way ?

Tom

I don't quite understand what you're requesting.  If it's a portal, why doesn't just the native portal sorting work?

Can you show some screen shots?

Hey,

 

It's not easy to explain with my poor english.

So i made an example empty and anoter explanation :

 

1/ I've got a main table contain only globals (user name, etc)

2/ I've got a layout with this table linked to another table so i use portal to display information

3/ The sort on portal have to change somes times by customer name, sometimes by city.

So i could make a calculation for sort but i tried another way :

I create a field in the table in the portal and use it to sort. This field is fill by a script which displaying datasort it by critera i sent and then come back to the main table.

Is it more clear ?

Tom

Portal.fmp12

15 minutes ago, Tom Assia said:

The sort on portal have to change somes times by customer name, sometimes by city.

I would use 2 portals, and show one of them according to the user's choice of sort order.

Alternatively, define an unstored calculation field that returns either customer name or city, based on a global field storing the user's choice of sort order, and use it to sort the portal. But this will be slower.

 

10 hours ago, Tom Assia said:

replace field content by serial

That's not a good idea because different users may have different viewing preferences. 

1 hour ago, comment said:

That's not a good idea because different users may have different viewing preferences.  

I know, in this specific case, not a problem, only one user have to use it,

thanks for help

12 hours ago, Tom Assia said:

in this specific case, not a problem, only one user have to use it,

It's still considered bad practice, because:

(a) if a solution is successful, the client may want to expand it to accommodate multiple users; this should not require a major rewrite;

(b) fields that track record modification become meaningless.