Hi @jja ,
If your intent is for the combo to have the last number, you could run into issues when you list grows beyond your data row limit. Last(source) will become the last record of the subset of data returned, up to a maximum of your data row limit (default 500, max 2000) rows.
So, if your list has 5000 rows and your data row limit is 500, Last(source) will only ever return the 500th row.
A better way to get this might be to instead select the first of the list when its sorted by descending values. Because SortByColumns(source, "column", Descending) is delegable, you can be sure you will always get the last record in the first place.
Then, to set the DefaultSelectedItems: property of your combo to the last 'Uzsakymo numeris', you just have to specify a record that exists in the ComboBox Items: output - to make this easier, just make sure your filter statements for both Items: and DefaultSelectedItems: return the same subset of data.
Try this - if your Items: property for your combo is;
SortByColumns(Remontai, "Uzsakymo numeris", Descending)
then your DefaultSelectedItems: property on your combo would be;
First(SortByColumns(Remontai, "Uzsakymo numeris", Descending))
Lastly, capturing data to a source in Power Apps automatically refreshes the source for that user session - so if you're the only one running this app you wouldn't need to Refresh the source to see your combo update after a patch - however, if someone else is running this app at the same time and adding records, then your session wouldn't know about it until it Refreshes, either by saving data to the source, or using the Refresh() function - be careful using a field value that is generated by PowerApps based on the Last() record of a source, because it might not be the last record when you run your Patch() and you could end up with duplicate auto-gen'd numbers...
Hope this helps,
RT