I have a complex case that I need help with that will probably end up in a store

reginaldm over 8 years ago

I have a complex case that I need help with that will probably end up in a stored procedure of some sort.

Here's an example: From your query entity, you retrieve 100 rows of data, many of them all containing the same information, except for 1 column, for the following 4 columns:Application #, Part Time Students, Full Time Students, School Number

Your data looks like this initially:
(The count matches for each set = 7)

Application #: {115111,115112,115113,115114,115116,115117,115118}
Part Time Students: {1000,2000,1000,2000,1000,1000,2000}
Full Time Students: {500, 500,1000,500,1000,1000,1000}
School #: {1,2,1,2,1,2,1}

From here, you want to retrieve only distinct values from each set (this may even include nulls at any given point).
So you want to truncate your data to this since there are many duplicates:

Application #: {115111,115112,115113,115114,115116,115117,115118}
Part Time Students: {1000,2000}
Full T...

Discussion posts and replies are publicly visible

Parents

0 Eliot Gerson
Appian Employee
over 8 years ago

So, it sounds to me like you're wanting to display a grid, and you don't want any of the rows in the grid to be an exact duplicate of another row in the grid (where a different application number does not count as making a row unique). Is that correct?

If so, for a small number of columns, as is the case in your example, one option might be to add a column in the database that is a combination of the three columns you wish to be unique. So, for your example, it might contain values such as "1-1000-1000". You could then use a!queryEntity() to retrieve the data from the database and aggregation to filter out non-unique results (see forum.appian.com/.../Query_Recipes.html ). This would be particularly easy to implement if you don't actually need to display the application #. The end result would be that you would only retrieve unique combinations of data to display in your grid.

Would this approach work for you?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eliot Gerson
Appian Employee
over 8 years ago

So, it sounds to me like you're wanting to display a grid, and you don't want any of the rows in the grid to be an exact duplicate of another row in the grid (where a different application number does not count as making a row unique). Is that correct?

If so, for a small number of columns, as is the case in your example, one option might be to add a column in the database that is a combination of the three columns you wish to be unique. So, for your example, it might contain values such as "1-1000-1000". You could then use a!queryEntity() to retrieve the data from the database and aggregation to filter out non-unique results (see forum.appian.com/.../Query_Recipes.html ). This would be particularly easy to implement if you don't actually need to display the application #. The end result would be that you would only retrieve unique combinations of data to display in your grid.

Would this approach work for you?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data