Then you should have a list/table view of problema… And a list view of Fechados… When you select a problema the Fechados list should filter down for you.
I don’t understand what your trying to do?
What is your end goal, how do your users interact with this data?
Your data currently appears to be a list of Fechados, with a complete duplication of the problemas into another table… the problema field in fechados is simply a text field, not an enum… I quite literally can not make sense of your end goal.
If you try what I said you will end up with an interactive dashboard, which I think you may find neat.
If you want a detail view with a dropdown, then each user would need their own detail view, so now you will need to create a user table, with “problema” as an option. Then use a security filter to only show the users their single user record in which they can choose from a drop down the problema. That dropdown would need to have a list built in the valid_if section of the available problemas… Then you would need to create a slice of the Fechados table with expressions looking toward the single user record. (It’s an awful lot of work, I do it often. But without understanding exactly what you’re trying to do, and the way your users would interact with this I was hesitant to recommend this approach.)
The view on the left should be atop a slice. The slice should have a row filter that uses the column values of the row being updated by the view on the right.