InfoPath Dev

I have traditionally been able to interact with list data for an InfoPath form by taking advantage of the owssvr.dll by selecting XML and using this path (similar): https://myServer/sites/SE/_vti_bin/owssvr.dll?Cmd=Display&List={22222222-FFFF-3333-9999-222222222222}&XMLDATA=TRUE&noredirect=true. I use this to filter and sort, or simply choose a specific view since a direct list connection orders by ID. Recently this appeared to have changed. I have existing connections working fine in SharePoint 2016. I am attempting the same thing publishing the form to SharePoint Subscription Edition with no luck. Now, if I convert this to a Connection File and authenticate using Secure Store credentials, it works. My basic question is if anyone has experienced this and if this is now required much the same as the GetUserProfileByName which needs to be converted to work. Thanks as always.

So sorry to not actually answer your question here, because I don't know the answer with SE.... but I am wondering if you've considered moving to the REST API instead of owssvr.dll? It works great for filtering, sorting and ordering.... Also, just as an FYI, you can change the sort in a direct list data connection when you create it. There is a dropdown on the dialog where you pick the columns you want :)

Thank you very much for your reply. I am in fact using REST also, but the same thing occurs. I just chose the OWSSVR example because I have more of those. Example: https://myServer/sites/SE/_api/web/lists/GetByTitle('TitleName')/items?$orderby=Field2%20asc&$top=300. I was hoping to avoid touching hundreds of forms before migration. The REST connection only works when I convert it to a Connection file. I do have a case opened. I will let you know what I find out. Maybe it will help someone else. Note: I also tried this direct call: https://myServer/sites/SE/_vti_bin/ListData.svc/MyListName/?$select=Field1,Field2&orderby=Id but the same thing happens.

Got the answer: "SPSE is a hybrid architecture so therefore for long run InfoPath we need to change the connection and refer UDCX file accordingly rather than using direct connection." The same will be true for REST according to MS. Hope this helps someone else.