@Alejandro Pinzón what you linked are payment providers, for which i’m not super sure how they play into repeater fields.
I wasn’t saying that Polymorphic relations solve every use-case, but they can sometimes be seen as a workaround for repeater fields. As mentioned we don’t have those right now, but certainly want to revisit them.
I’m not completely sure how your amount example plays into this, but i’ll give you an example how Unions could play into this 😊
You could create a “Product Page” Model which gets a polymorphic relation (allowing multiple values for a many relation) to connect to a Product Model, a Gallery Model and maybe a Content Model. On these Models you add all the fields you want.
When you then create a Product Page Entry, you can connect a Product to it, maybe a Gallery, then a Content entry and then another gallery. You can even reorder them with sortable relations. It’s not the perfect replacement, but maybe helps in some cases and could potentially even be seen as a repeater.
This way you might be able “mimic” the behaviour of a repeater.
I hope that helps a bit clarifying what I meant with my previous message 👍