#jessa-terminal-configuration
rapid moon
visual crescent
We have lots of configuration objects, which one are you referring to?
hearty sandal
sorry, the terminal configuration that you can assign to locations
visual crescent
jessa-terminal-configuration
So yeah this is a property. It maps to what's configured as the default in the Dashboard. You can't set that to a different one
hearty sandal
so i can create a configuration via the api, then i have to go in the dashboard and set it as the default?
visual crescent
no
you create one in the API, and it won't be the default and that's it
if you want to change the default you have to do it manually in the Dashboard
hearty sandal
sorry, but this is confusing me a little:
"if you want to change the default you have to do it manually in the Dashboard"
where can i do it manually in the dashboard?
ultimately i'm trying to set a configuration with tipping turned on as the default
i understand i can't change which configuration is the default, but i guess i will try to get the default configuration and add tipping to it instead of creating a custom one
visual crescent
hum you're righ, let me check. Sorry today is a weird day and I'm off my game
hearty sandal
no worries
visual crescent
trying for a bit
okay so I tried, you can use the List API https://stripe.com/docs/api/terminal/configuration/list to find the default one and then you can update it
hearty sandal
got it, thanks
visual crescent
sorry for the confusion earlier!
usually when we have an "is default" concept it's because there's a clear Dashboard UI for this 😅
hearty sandal
no worries. seems you can't set the tip configuration anywhere in the dashboard either, so i'm guessing this isn't a widely used feature yet
visual crescent
yeahhhhhhh still it feels like it should be, and per location.
hearty sandal
per reader would be best IMO, but i realize that doesn't work with the paradigm. i'm working with a movie theater that needs tips at the bar and concessions, but not in the box office window
but earlier you told me i can create separate locations in the same physical address, so that's what i'll do
visual crescent
yeah I think this is the perfect example of separate locations with different default configs
hearty sandal
although per reader seems like a common use case (thinking of a grocery store that needs tips at the sandwich counter, but not at regular checkout)
seems like locations could be named to groups or something, to make it seem less tied to the physical address
hearty sandal
right. but even that seems a little wrongly named, since it's not even a "location" that dictates using the same config.
it made sense when the only thing in the config was the splash screen, but now that tipping is part of the config, that has nothing to do with location, just the use case for the readers. so i'd call it group or subclass or something. anyway i think i can figure this out now, thanks for the help
visual crescent
yeah that's fair
hearty sandal
i take that back, it's reasonable to call it sublocations, if you want to say the location inside the location, like bar or sandwich counter. so i agree with you. and you're busy, so i'll stop wasting your time chatting about semantics now 😅 thanks again for your help
visual crescent
yeah I think you want "groups of readers" where Location is just one of the "grouping criteria"