Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

LCA Search Input – Limit Search to specific columns

79 views18 hours agoGQI LCA
1
Felix Wesemeier [DevOps Catalyst]1.84K 1 day ago 0 Comments

Hello Community,

Is there a way to search within one or more columns without re-executing the query?

The search input component offers a convenient search, but isn't restricted to a specific column.

Or is there a special syntax for this?

The query filter component simply highlights the results. Is there an option to completely hide non-matching entries?

Thanks,

Felix

Wout Mahieu [SLC] [DevOps Catalyst] Answered question 18 hours ago

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
1
Wout Mahieu [SLC] [DevOps Catalyst]7.69K Posted 18 hours ago 3 Comments

Hi Felix,

The Grid, Node-edge, Maps & Timeline components have a 'Highlight' option in their layout settings. When this is enabled (default), the items not matching the filter from the query filter component will be grayed out. If you disable the setting, they will be completely hidden. As long as the component is linked to the query filter using its columns as a filter and not by using the query as data, the query will not re-execute.

An alternative option that will only work for the table is to use the quick-filter on the component itself. Note that this filters on all columns and will fetch more query pages when needed.

Felix Wesemeier [DevOps Catalyst] Posted new comment 10 hours ago
Felix Wesemeier [DevOps Catalyst] commented 15 hours ago

Hi Wout,
thanks.
Unfortunately I need it for a table.
Is it on the roadmap to add this disable highlighing/hide non-match entries setting also to the table component?
The table quick filter is what Im looking for, but limited to specific columns.

Wout Mahieu [SLC] [DevOps Catalyst] commented 10 hours ago

Hi Felix,
This setting doesn't really work the table component because this component fetches its results page by page. Applying a filter to hide non-matching entries could also mean fetching more result pages to fill the view. This would be the same config as adding the query from the query filter component as data.

We have no feature planned to make the quick filter only look at specific columns, this could lead to confusing behavior.

Is there a specific reason why you would not want the table to re-execute the query? This would probably be the best approach, combined with a custom operator that does the filtering itself.

Felix Wesemeier [DevOps Catalyst] commented 10 hours ago

The reason is the execution time of the query and unnecessary work for the server.
The client already has the data.
Why should we retrieve it again from the server?
The table build in search does it well, but is not limited to a column, which could confuse the user when entering something which is not visualized directly (some helper columns).
How does the build in table search handles paging?

1
Miguel Obregon [SLC] [DevOps Catalyst]18.91K Posted 1 day ago 1 Comment

Hi Felix,

You could link a search input, numeric input or a text input to filter a specific column:

Hope it helps.

Felix Wesemeier [DevOps Catalyst] Posted new comment 1 day ago
Felix Wesemeier [DevOps Catalyst] commented 1 day ago

Hi Miguel,
thanks.
It tried it, but it looks like the query is executed again when entering something.
This is what I want to avoid.

Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin