Hi! I have a question regarding entities
Hi! I have a question regarding entities. In my case, I'm using entities to track seats. When calling the checkout function, I need to provide an entity id. When creating an entity, I also need to provide a feature id. So how should I handle the scenario where a seat gets upgraded? I don't see an API call to update an entity. Do I need to do that? Would Autumn automatically "upgrade" the entity on check out? I don't see a way to update an entity, so should I delete and recreate the entity if the feature id changed (e.g. the seat got upgraded)?
Background: my app will charge per seat and at least for now I'll have 2 types of seats, each with different prices. So as suggested, I created 2 products, each attached to a different feature. AFAIK, need then to pass the entity Id to the checkout function. So that means I need to create the entity before the call to the checkout function.
I may be over complicating this. Perhaps all I need to do is to pass an entity ID on checkout but I see the docs saying I do need to create the entity if the entity is billable (which is the case here). Or perhaps I can just have 2 different products with the same feature and control access using the product instead of the feature?
Background: my app will charge per seat and at least for now I'll have 2 types of seats, each with different prices. So as suggested, I created 2 products, each attached to a different feature. AFAIK, need then to pass the entity Id to the checkout function. So that means I need to create the entity before the call to the checkout function.
I may be over complicating this. Perhaps all I need to do is to pass an entity ID on checkout but I see the docs saying I do need to create the entity if the entity is billable (which is the case here). Or perhaps I can just have 2 different products with the same feature and control access using the product instead of the feature?
