In addition, it seems like both of these commands need to be executed twice for them to work 100% of the time. It also seems that some time must go by... running these immediately successively doesn't seem to be 100% accurate, unless a period of time goes by (the data is in SQL Azure, and yet the patch statement shows that it updated the data immediately).
Why doesn't it recognize in the View that data was changed: we have to refresh the ENTIRE table and the ENTIRE view, which should not be necessary.
Then we can rebuild the collection like this:
ClearCollect(CollectvwView1, AddColumns(Filter('[dbo].[vwView1]', Id = ThisItem.ItemId),"GUID",Text(GUID())));
And that provides the accurate data that we are looking for, but we cannot have the latency issue.
So we need the following to return the most up-to-date, refreshed data, and this would work, if PowerApps would correctly pull data this way:
Refresh(Filter('[dbo].[vwView1]', Id = ThisItem.ItemId));
We are somewhat constrained by the View, because it pulls from a 3rd party app.