#trina_api

1 messages ¡ Page 1 of 1 (latest)

uncut starBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1366763822890876928

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

maiden gate
#

Hey there -- looking into this for you, give me a few minutes

#

however, I expect this is in the case of share the same meter A on both price A1 and price A2

#

if you instead have a meter A for price A and a meter B for price B, that may not be the same

#

You can't have two active meters with the same event name, but if you deactivate the first as you say then you will be allowed to do that

#

If they're separate meters, I would hope we do invoice the amounts correctly like you describe for the transition period

#

Note the deactivating the meter would impact any other prices/customers using the same meter

uncut starBOT
solar rose
#

Hey, thanks for the doc- I did see that but that's not acceptable for our use case. We need to record the usage before the price increase for that price and usage afterwards for the new price in the same billing cycle for the subscription

solar rose
simple light
#

It is on the roadmap, though I'm not sure on an ETA for it. At the moment, the best workaround I am aware of at the moment is to preview the upcoming invoice on your subscription and then create one-off invoice items that represent the existing usage when making the update on your subscription (you can do this with the update call's add_invoice_items param)

solar rose
simple light
#

You can charge right away or on the next invoice for the subscription. Basically when you add invoice items to a subscription, they will get added to the next invoice on the subscription whether it is for an update or on the subscription cycle. So if you add the invoice items via add_invoice_items and specify proration_behavior='always_invoice' an invoice for that usage will immediately be created. Otherwise they will be included on the next invoice when the subscription cycles

solar rose
#

Thanks, we would want to wait until the next billing cycle on Ma y 16th so in that case I can avoid that parameter when adding the invoice item

#

Thansk for both of your help