Forum Discussion
Building a date-centric measure for sparse data snapshots
HI creeves,
It seems like a common date range define by multiple date fields analysis requirement. I'd like to suggest you take a look at the following blog start date, end date part if helps:
Before You Post, Read This: start, end date
Regards,Xiaoxin Sheng
HI creeves,
It seems like a common date range define by multiple date fields analysis requirement. I'd like to suggest you take a look at the following blog start date, end date part if helps:
Before You Post, Read This: start, end date
Regards,
Xiaoxin Sheng
@v-shev-msft
Thank you again for the reference material. I went through each example and believe that I now understand the underlying principle: a virtual table which, for each entity (Customer or Ticket #) holds the key data in question (the customer obligation each month, or the dates the ticket is open). The measure is calculated as the the sum of the value of open accounts in a period, or the count of open tickets in a period.
In my case, the key is similar: to envisage a table that shows the value of, say, estimated revenue, in each period for each opportunity. For example, the estimated revenue for product A in May 2022 is $2,000; for B it is $3,000; total $5,000.
The challenge I still face is how, for months for which I have no snapshot of estimated revenue, to use the most recent prior value. I've expanded the example to clarify the problem .. which is how to infer the intermediate/missing monthly snapshots. The actual snapshots are in black and those to be inferred are in red. I'd welcome any additional advice.