Hi,
The Distinct clause will always consider all the columns of the view unless specific columns are specified in query. You could try different options to accomplish this.
* You could use analytical functions like [Row_number](https://community.denodo.com/docs/html/browse/latest/vdp/vql/appendix/syntax_of_condition_functions/analytic_functions_window_functions#row-number) to handle the duplicate values and order the result based on the another column. You could do it in the underlying data source or in Denodo platform either way the data source has to support the analytical function.
* Write a query in Denodo platform to handle the duplicates and use that to create a view. See below sample query.
```
SELECT b.field_B FROM view_B AS b INNER JOIN
(SELECT field_B, min(field_A) AS field_A FROM view_B GROUP BY field_B) AS a
ON (b.field_B = a.field_B AND b.field_A = a.field_A)
```
You can take a look at [Defining a Derived view](https://community.denodo.com/docs/html/browse/latest/vdp/vql/defining_a_derived_view/defining_a_derived_view) to check the syntax and details for creating a view.
For storing multiple row values in a single row check if[ Pivoting the data](https://community.denodo.com/kb/view/document/How%20to%20Pivot%20and%20Unpivot%20views?category=Combining+Data) can help you. If the underlying data source supports Pivoting you could do that in the data source itself and create views on top of that output. If you would like to store the data (after pivot) in a array like structure take a look at [Compound Types](https://community.denodo.com/docs/html/browse/latest/vdp/vql/advanced_characteristics/management_of_compound_values/management_of_compound_values) in Virtual DataPort.
Hope this helps!
