10
Views
2
Comments
Solved
Dropdown Search + Table
Question

Preciso de uma orientação Estou desenvolvendo uma funcionalidade em que desejo utilizar o componente Dropdown Search para selecionar um paciente. Após a seleção, gostaria que os dados do paciente (como nome, telefone, e-mail, etc.) fossem exibidos em uma tabela (Table).

Alguém poderia compartilhar a melhor forma de implementar esse comportamento?

I need some guidance

I'm developing a feature where I want to use the Dropdown Search component to select a patient. After selection, I'd like the patient's data (such as name, phone number, email address, etc.) to be displayed in a table.


Could someone share the best way to implement this behavior?

Teste.oml
2026-01-28 16-57-48
Mihai Melencu
Champion
Solution

Hi @Pedro Vinícius ,

If you want to display a table, you’ll need to bind it to a list. Are you trying to implement search for the table, so that if no patient is selected, all patients are shown?

At the moment, the logic you have is good, I don't see the need to use a table, unless you want to implement an actual search feature for the aggregate.

2019-01-07 16-04-16
Siya
 
MVP
Solution

@Pedro Vinícius : In the shared OML, you’re using the Dropdown Search component, which loads data from the client side. What you implemented is fine, as mentioned by @Mihai Melencu 

However, since you’re building a patient portal, you’ll likely need to handle many more records than the 50 currently hard-coded in your GetPacientes Screen Aggregates. For larger datasets, the recommended control is Dropdown Server Side.

You can find more details here: https://success.outsystems.com/documentation/11/building_apps/user_interface/patterns/using_mobile_and_reactive_patterns/interaction/dropdown_server_side/

2026-01-28 16-57-48
Mihai Melencu
Champion
Solution

Hi @Pedro Vinícius ,

If you want to display a table, you’ll need to bind it to a list. Are you trying to implement search for the table, so that if no patient is selected, all patients are shown?

At the moment, the logic you have is good, I don't see the need to use a table, unless you want to implement an actual search feature for the aggregate.

2019-01-07 16-04-16
Siya
 
MVP
Solution

@Pedro Vinícius : In the shared OML, you’re using the Dropdown Search component, which loads data from the client side. What you implemented is fine, as mentioned by @Mihai Melencu 

However, since you’re building a patient portal, you’ll likely need to handle many more records than the 50 currently hard-coded in your GetPacientes Screen Aggregates. For larger datasets, the recommended control is Dropdown Server Side.

You can find more details here: https://success.outsystems.com/documentation/11/building_apps/user_interface/patterns/using_mobile_and_reactive_patterns/interaction/dropdown_server_side/

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.