#palo_docs

1 messages ¡ Page 1 of 1 (latest)

meager steepleBOT
#

👋 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/1376860096155484160

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

covert slate
meager steepleBOT
covert slate
#

the limitation you mentioned is not documented, but I'm further looking

ashen lotus
#

For the number of product it here: When you allow customers to switch plans, you can specify a maximum of 10 products for them to choose from.

covert slate
#

Can you share why that would not work?

ashen lotus
#

2 prices per product could be the perfect way but the user can see when he chose a price (during the first subscription in the checkout session) if it's with or without engagement of 12 month because there is only the product name shawn and not the price description

normal onyx
#

10 is just the limit today unfortunately. If you need to model your products/prices that way then that's just a limit you'll need to work within

user can see when he chose a price (during the first subscription in the checkout session) if it's with or without engagement of 12 month because there is only the product name shawn and not the price description
Can you elaborate on this part? Not sure what you mean by 'only product name shown'

#

Screenshot may help

ashen lotus
#

I do screenshot wait a minute pls

#

Here it's only the product name, if i can have the product name for example Amiral + the price name or description that could be perfect for example: Amiral - Price without engagement

normal onyx
#

Yeah that's unlikely to be supported. Why not model them as separate line items?

ashen lotus
#

hum what do you mean ?

normal onyx
#

I guess I don't really understand the problem overall. But what you want to do today isn't supported