#adrien_docs

1 messages ¡ Page 1 of 1 (latest)

still 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/1423304659216502888

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

young helm
split trout
young helm
#

Sure

split trout
# young helm Sure

It doesn't seems to be possible with the dashboard. I will need more time to setup the python to try.
However, does it update the price for all the event (past and future) of the current billing period ?

split trout
# young helm Sure

Thank, that look perfects. The different pricing are tied to a date and it is written into the invoice so it is clear for the custormers.

#

It is just not possible to do it in the dashboard.

young helm
#

We're developers and we're happy to help with your API

#

Via the Dashboard, you'd just need to try and see if that works. I think it should work.

split trout
young helm
#

You would want to update the subscription and then remove the product, and a new one

#

Are you saying you can't see that?

split trout
#

yes, I can but if I do that. Then all the associated event are lost

#

and then I would need to add a new product that would start accumulating event without the previous one.

young helm
#

Hmm, that does not make sense.

split trout
#

but updating the subscription item as you suggested within the code works as expected. All the event remains but with the old price. And the new one have the new prices.

young helm
#

What events?

split trout
#

meter events

young helm
#

Ahhh!

#

The Dasboard and the API do not have 100% parity. It is possible that they behave differently

split trout
#

My bad for assuming the opposite

#

(It is normal with complex tools)