Something's wrong with one or more fields

Hi Gilbert.  Correct.  Users are updating the PBIX files.  The nice Report Server actually, will not let you save a desktop version and yes, we make sure the users have the correct version installed on their machines through our IS department as well.  In the past, we have had to migrate some templates into the newer versions.  However, all of the versions we are using currently are matching also.  I just created a brand new dashboard to test this theory using Power BI Optimized for Report Server (January 2020).  Same exact problem.  I saved it to a new file then went back today, added another dataset in there and a new visual, and ran into the same problem.

I did these two scenarios to fix the problem and encounterd these findings.

1. Saved the PBIX over the old existing PBIX (Same exact name) and everything visualized fine (No Service Error).  When I ran the scheduled refresh, I then encountered the same error I've been having the issue with:  "Something is wrong with one or more fields, please try again later or contact support".  These were the fields on the new dataset, but strange.  It worked fine when I uploaded it, but the schedule broke it.
2. I deleted the whole PBIX from the Power BI Server and the schedule this time.  Uploaded the changed PBIX as the same name of the old PBIX and created a new schedule.  I kicked off the refresh schedule and problem solved.  A lot of steps that seem unnecessary and also very dangerous for the users if that goes wrong.

I've also had luck with restarting the service by resetting the service account credentials which stops and restarts the service.  The problem suddenly went away on some of the reports that I hadn't tried to go fix yet and discovered this unintentionally (or this just happened to be a coincidence).  I don't think it was coincedence because these issues had been happening on a new dashboard a user was trying to get up and we were struggling to find out why this issue was happening.  Trying to isolate what is actually happening though has been really challenging.  I've been looking through the logs on the actual server and I don't see anything that sticks out to the RequestId reference that it gives to the user with this message, so it's tough to troubleshoot.