Forum Discussion
Month-end Dataflow Refresh Process
There's no way to do what you're wanting while keeping the existing IR policy.
Once the accounting period closes, I'm assuming those "closed" records no longer change.
I would look at splitting the Dataflow into two, one for closed and one for current. You can then have separate IR policies on each and just combine the Dataflows in your model.
Super UserI'm pretty sure the suggestion from Anonymous is not possible with incremental refresh. I'd loved to be proved wrong though.
Do you have a 'last updated' date in your database? (I'm guessing not or you would have used it)
Is it efficient enough that you could change the IR period to last 2 months or last 45 days?
If your IR is in the Dataflows (I wasn't sure from your post), it might be worthwhile looking at splitting posted/completed (whatever terminology you use) from current, then you may be able to change the incremental logic and in your model, do a Table.Combine for the separate Dataflows.
Difficult to be any more definitive with the info provided.
Hope this gives you some options.