​@LizAtSafe This idea does not seem to capture the same idea as the one I submitted, so merging it doesn’t seem to fit.  Being able to sort on a column is not the same as beign able to search (or filter) on a column.  If this idea is modified to include both capabilities, then that’s good (and better).  If that is the case, then please update this idea to include both capabilities so it’s clear.

However, if this idea is only going to include sorting, then please separate out my original idea for searching/filtering back to it’s own idea please, or let me know to re-submit it as it’s own.  Thanks for your consideration.

​@LizAtSafe Is there an update on my reply about the merge of these two requests that I beleive are two separate things?  Should I submit a new request or is the merged request being updated to include searching or filtering?

​@bruran I think it’s all going to come under the same project, from the Safe end of things, so that’s why the ideas have been merged. I was just in a meeting where we talked about the importance of both searching and sorting. I understand product managers are going to do a sweep through the ideas as well, updating the titles and making explanations where necessary, so they may have more info.

​@mark2atsafe ​@LizAtSafe Is there any progress on the search capabilities being addressed?  Have the product managers finished their sweep through the ideas yet?  Will searching and filtering functions be included in the product development plan, and if so, when could we reasonably expect to see it in the product?  Thanks for any insight you can provide.

​@bruran Hi there! Great questions and thanks for raising them. I’m working directly with the teams on this so I’ll step in to respond for ​@mark2atsafe and ​@LizAtSafe.

Yes, we’ve made progress on improving search and filtering in FME Flow. Our product and UX teams have completed a sweep throughout FME Flow to identify where improvements to data tables (e.g. search, sort, and filter) would provide the most value. We’re going to prioritize the most-used, high-volume pages—for example, the Completed Jobs page.

To set expectations clearly:

• We do have a plan. Initial designs are complete, and development work is being scoped.
• It’s not an “everything everywhere” update. Not all columns will become sortable/searchable—our focus is on usability, not complexity.
• You can expect a larger batch of improvements in the initial rollout. These will be followed by smaller, iterative updates based on feedback and continued use.
• Release timing? We’re aiming to start rolling this out in an upcoming release, but we don’t have a fixed date to share just yet. We'll do our best to keep the community posted. 

(As an aside, I see now that I’ve created an automated link to a more specific idea, where in hindsight this idea may have been more appropriate to use—I’ll aim to reconcile that overlap once we have development scoped.)