We are using the Data Export Service to take a copy of our business data (Opportunities, etc) and making them available for read-only integrations and reporting.
We ran into a snag. To calculate the value of our opportunities, we have a calculated field on the Opportunity Product, which rolls up to a Rollup field on the Opportunity. It always looks correct in the Opportunity itself, but when the data export service gets the data, it sometimes has 0.00 and other times the real value. Out of hundreds of thousands of opportunities, only 5,000 have a non-zero value in this rollup field (in the Data Export Azure SqL database).
Interesting I recently had an issue where we had a bulk deletion job delete things it shouldn't have - it had a query saying "Opportunity Count = 0" but it was deleting items with opportunities - also this is a roll-up field. My sense is that possibly the rollup fields are 0 while they are in the midst of recalculation.
I don't see this as a limitation on roll-up fields but I wonder if it's a hidden limitation. Not sure how to fix aside from making a scheduled job to copy the rollup field value into a standard currency field. And even then, how do I make sure it's non-zero when I copy it?
