Categories
FDI Dataset Editor Filter Considerations

Reaching out to inquire re: anyone's experience running into filter limitations with FDI's dataset editor. We are trying to embed filters in the dataset editor page for a large table housed in an Oracle Data Connection. We have been able to accomplish this for comparable tables (along with other enrichments/transformations to the columns) without the need for data flows or expression filters; it would be preferable to keep the formatting processes standardized for each input (our current workaround is to embed the filter in a data flow). When attempting to apply the filter for an attribute, the following error message generates: "Please Further Filter Your Data (there was too much data to process your visualization… exceeded configured maximum number of allowed input records)." Does anyone have insight into what the exact record count number that this message begins to apply? (A feature to view total records contained in the dataset editor at each enrichment step would be very helpful for business users). Additionally, if there is an exact attribute filter expression statement that has been successful, we would be willing to try and leverage it (filter statements attempted to date have not validated for the table). Any thoughts or feedback is appreciated
Best Answer
-
Hi @Matt_B,
The 'Max input rows returned from any data source query' are defined in the OAC documentation here:
Your filters should be designed to take those into account.
Regards,
John
0