Jump to content

Sorting by value list changed in 7


Fitch

This topic is 7211 days old. Please don't post here. Open a new topic instead.

Recommended Posts

When you sort ascending on a field, blanks go to the top of the list. You can get around this by sorting on a value list. Non-value list members, including blanks, sort to the bottom.

In FM6, this also held true for sorting portals. But in FM7, whether you sort on a relationship, or sort the portal directly, blanks go to the top of the portal.

Anyone else been bitten by this? It bites.

My workaround is to use a calculated field Case( SortField, SortField, 999 ) /* I hate this */

Link to comment
Share on other sites

In FM7, whether you sort a portal by a value list using its relationship, or sort the portal directly, blanks go to the top of the portal. In FM6, blanks went to the bottom when the relationship was sorted by value list. Is anyone else bothered by this? Would anyone care to verify or comment on this? Is this old news?

Link to comment
Share on other sites

I'm not seeing it. Here's a sample file that I think is setup like your describing, one portal is sorted itself, the other uses a sorted relationship.

There are bugs with using valuelists from other files, if that's the problem, I think you can make a copy of the valuelist in the file that uses it.

Link to comment
Share on other sites

Thanks. Apparently the problem is indeed with external files. See attached for example. The internal table sorts correctly, but the external doesn't. Seems like a genuine bug.

Link to comment
Share on other sites

This topic is 7211 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.