#dbugger_product-lookupkey

1 messages ยท Page 1 of 1 (latest)

tall radishBOT
#

๐Ÿ‘‹ 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/1245042172869349528

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

fossil ferry
#

@small iron looks like a Dashboard bug. Try using the API instead and pass lookup_key: '' and it should work

#

dbugger_product-lookupkey

small iron
#

You mean a bug, in the sense that it is not being updated? Or that it is being updated, but not shown? I am not sure if you are telling me to use the API to update it, or to check the value

fossil ferry
#

I think it's not being updated so try the API to unset it

small iron
#

Cool, I will

#

I tried this:

await stripe.price.update(prices.data[0].id, { lookup_key: null });

And it threw an exception with the message:

[18:04:45.831] ERROR (705580): Cannot read properties of undefined (reading 'update')

#

I checked the id value. It is the correct one

fossil ferry
#

yeah you went way too fast

  1. It's prices with an S not price
  2. It's an empty string '' not null
small iron
#

Oh ๐Ÿ˜›

#

I should have seen that one. I though that "update" was an internal thing of yours. Sorry.

#

Yes, that worked

#

even though null also worked

fossil ferry
#

we'll get the Dashboard bug fixed

small iron
#

Thanks for everything!