Unfortunately I can’t read that language, so without you telling me that the fields are out of order, I have no clue what’s going on.
That aside, field order is always going to be arbitrary if you only ask Airtable to give you the fields from a specific table. However, if you ask it for fields in a specific view from that table, then the order should be maintained in the data that you receive. I’m not sure how this translates into what you’re doing with Kodular, but I’m hoping that this makes enough sense that you can apply a fix that will work.
Also keep in mind that you will might not get every field for every record. If a field is blank for a record, that field will not exist in the response from the REST API.
I also would not count on the fields being in a particular order when you request records from a view. Requesting records from a view only filters the records – the fields returned are not limited the fields that actually appear in the view.
In any case, I do not recommend relying on field order when using the API. Go by the field name.