Is this something where Microsoft has made a change in the parameter from one to the other or is just inconsistent and is a comma in some places and semicolon in others?

Ah, that's good to know. I could see that being an issue almost akin to the way we have to escape > and < signs in xml because commas are used differently in different jurisdictions especially when you talk about numbers and whether the jurisdiction uses a decimal or comma separator.

@Darren Neese Great information and way to think through the potential bottlenecks that will keep an application from scaling. So many times, people forget that data retrieval has a cost, sometimes in actual dollars (or insert whatever currency you are using here), but most often in terms of performance and user experience. In the database world, we would provide views for developers around the data that they actually needed for an application as it is always faster to retrieve just the data you need rather than all columns and potentially, rows from a table. There was always that developer that couldn't help themselves from retrieving more data than they need thinking they will need it later. These days, when you are developing in a platform such as Power Apps, you don't have a DBA to advise you on those types of performance issues (in my day, not all that long ago, DBAs were really responsible for the performance of not only the database, but the apps, helping the devs constantly tune their queries to achieve the best performance) and you have to act as both the developer and the DBA thinking through all of the performance ramifications of your design decisions. I am hearing more and more about how the constant changes Microsoft is making to things across the Power Platform and Dataverse stacks have killed an application's performance overnight, so thanks for sharing from your experience in this aspect. We won't be able to avoid all of the potential performance-killing changes, but knowing about this potential pitfall is very helpful.

Wow, that is really cool. Thanks for sharing!

@Scott Simpson Thanks for sharing!

Done