We have millions rows of data, and we're implementing ODAG to handle it. In certain scenarios, the users want a big cluster of the receipts only, hence we're binding the 'ReceiptID' field for the template app.
However, there's an issue when the receipts selection are more than half a million, the 'odag app generation' is not working after we click it.
We'd be really appreciate it if anyone could provide some advices. Not necessarily only in ODAG method, other methods to handle the passing of plenty selections are welcome too.
I don't think ODAG is meant to handle parameter passing for hundreds of thousands of values. Presumably, these values have something else in common - perhaps a time period, perhaps some other dimension - and you can pass that along instead. You're not limited to a single field being passed.
I don't think ODAG is meant to handle parameter passing for hundreds of thousands of values. Presumably, these values have something else in common - perhaps a time period, perhaps some other dimension - and you can pass that along instead. You're not limited to a single field being passed.
Yes, I totally agree with you, and that's what we've been doing with ODAG.
It's just that recently, users reflected that they wished to further analyze the cluster in another app. The apps were separated in the first place; that's why we tried to explore the possibility of using the features.
