Hi everybody, We are looking for advices/best practices prior to deve

Hi everybody,

We are looking for advices/best practices prior to develop an application around data manipulation. Among the requirements, we need to:

- create a table from an excel file
- improve data quality using matching alogrithm
- display the matching result and get approvals from users

The expected number of input rows is around 10k+ but the number of distinct "matching" is more about a couple of hundreds I suppose.

For now, we have been thinking at the following solutions :

1- To create the table : use the excel file plugin + create CDTs + use write to data store entity Smart Service
2- To perform the matching, we have a custom expression that works just fine
3- To display distinct matchings: use the Query Database Smart service (SELECT DISTINCT... ) + create CDTs + use of paging grids for display

We encounter some limitations for 1&3 (nodes limit (1000), number of max rows returned by a query (10), latency) and prior to move on custom...

OriginalPostID-57770

OriginalPostID-57770

  Discussion posts and replies are publicly visible

Parents
  • I suppose you could display the data via an excel file?

    I think there is a component that does this via SQL data. At least this way you get a potentially large data set in one go and excel will allow users to filter etc.

    Another way would be to display the data via a paging grid and query rule to support this. The downside is if it is a big data set then they could be paging for a while!

    If I was looking at this I think I would be looking to keep the process as light as possible and perhaps take the approver to the data somehow and then a task to indicate whether it was approved or not.
Reply
  • I suppose you could display the data via an excel file?

    I think there is a component that does this via SQL data. At least this way you get a potentially large data set in one go and excel will allow users to filter etc.

    Another way would be to display the data via a paging grid and query rule to support this. The downside is if it is a big data set then they could be paging for a while!

    If I was looking at this I think I would be looking to keep the process as light as possible and perhaps take the approver to the data somehow and then a task to indicate whether it was approved or not.
Children
No Data