Calculating in the cube would be a challenge, as the payment term is derived on a more granular level (Contract and Customer) then what we are storing in the cube.
We are evaluating 2 approaches:
1: A second import as Fred suggests.
2: Derivative rule to get the future time periods in a separate UD and calculate this in the cube.
But would be good to understand if this is a limitation in the import or there is something syntax wise we can do :).
With kind regards,
Tim Vierhout
I believe derivative rules apply to the table that is created during your import for each workflow step. That is why I think using parameters that point to a different table in a different workflow step will not work.
Business rules, complex expressions or other creative solutions such as the one from FredLucas seem necessary.
