you can refer below microflow,
This way data’s retruned as list is to be copied to entity climatelog_2.
You can add a loop after your query that iterates over the list. Within the loop you can create an object of climatelog_2 for each climatelog in the list.
the “Result object” param of the java action only cares about the meta object type so that it can create the result list of that same object type. So you could just call the execute query statement configured with a newly created object “$climatelog_2”.
If you’re interested in having two lists of both object types (one list of climatelog and one of type climatelog_2), the you can perform two execute query actions, one with your created climatelog and one with a newly created climatelog_2 object as result object param.
This is assuming that your attribute names of climatelog and climatelog_2 are indeed the same. If they differ, you need to make sure in the SELECT statement that the column names are returned with the same attributes names as your climatelog_2. So for example if ‘TEMPERATURE’ is called MaxTemp in climatelog_2, then you need to write your select statement as ‘SELECT ResultTableName.TEMPERATURE as MaxTemp’.
Alternatively, you can of course still apply the proposed solutions above and copy on list to another according to your needs (e.g. using community commons Clone java action (for same attribute names) or using default Mendix Create Object where you copy over the attributes according to your own needs.