This is a quick blog post for a Friday, but one that might help some of you who’ve run into this issue.
After doing some investigation, we were able to determine the issue comes up only when the data set had been published using SQL Server Data Tools. The issue does NOT appear when you are using a shared dataset you created and published in Report Builder. We’ve already fixed the issue for future releases, but for now, there are two ways to workaround this –
1. Use Report Builder to create the shared dataset vs. SSDT
2. Edit the shared dataset .rsd file using an XML/text editor. For the entry for the dataset in the file, change it from this –
To something that doesn’t leave it blank. It could be this, for example –
Then re-save the file to the server, and it will work without issue. Entering a value there won’t affect anything else around the dataset, including the name you assigned it when you save it. It just prevents the error from being thrown by the Mobile Reports Publisher around having a blank entry for the dataset name.
Hope this is helpful to anyone having this issue, and thanks for reading!