In the meantime, has anyone come up with any tricks on how to figure out what the error is without the detailed log? I can’t wait for Cloud Support to supply it to me as they are few and the errors are many.
Not pretty, but you can go into the query of the report and strip it down to just one column, one table, if that works, then slowly add things back in until you find what breaks the query. If you were on-prem, you can copy the query to SSMS and debug it there. Cloud, not so easy.
Ok, since I was dead in the water, I was just trying stuff on the dataset query and put a space in front of every line and it worked. Let me explain my process on how I customize SSRS reports.
I take the dataset query and copy it to Notepad++
I then add a CRLF after each field so there is one field per line
I add fields as needed and edit the FROM block as needed
I then copy and paste it back into the rdl
I do this for readability and to scratch my OCPD itch. I get errors a good amount of the time, but could address them with the log. I was literally trying ANYTHING to try and get it to work and adding a space at the beginning of each line worked.
open your original rdl (locally) and delete the Tablix so there is only a Body there and save it.
Upload the report using Report Style
Run the report Generate for Design.
Open System Monitor
Actions → Design SSRS Report
Download the report
Copy the Original back over your “no tablix” version
run the preview - most times you will get some kind of error message the helps you figure it out.
if it still will not run - Divide and Conquer. Start deleting Fields at first and then remove from the RDL Main Select Query (you can ignore subreports initially).
However, everyone here is right - SSMS is SOOOOOOO missed on Cloud - there is no easy way to debug that i know of.
Sympathies - if it is any consolation - you will probably find a period instead of a comma