You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update daily overview model, or a more fitting model, to account for subscription-based transactions in order to build MRR reports on top of our package.
We need the invoice table in order to connect to the subscription table, which the daily overview model currently doesn't pull from. The closest model that would feed into an MRR report I'd say is the invoice_line_item_details model.
It seems that the daily overview model amounts come from the balance transaction table. The way subscription data would be brought in would be: balance transaction > charge > invoice > subscription. The most downstream models where some of them exist together is in the balance transactions and subscription details . But there isn't a model that ties all of those source tables together.
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Yes.
Yes, but I will need assistance and will schedule time during your office hours for guidance.
No.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing feature request for this?
Describe the Feature
Update daily overview model, or a more fitting model, to account for subscription-based transactions in order to build MRR reports on top of our package.
We need the invoice table in order to connect to the subscription table, which the daily overview model currently doesn't pull from. The closest model that would feed into an MRR report I'd say is the invoice_line_item_details model.
It seems that the daily overview model amounts come from the balance transaction table. The way subscription data would be brought in would be: balance transaction > charge > invoice > subscription. The most downstream models where some of them exist together is in the balance transactions and subscription details . But there isn't a model that ties all of those source tables together.
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
No response
The text was updated successfully, but these errors were encountered: