![]() That never happens! It turns out that vertical text was deprecated in SQL Server 2016. Imagine our surprise, then, when we found an “SSRS” bug. Given this experience, we don’t usually test our reports within SSRS until after they are added to Enhansoft Reporting or Warranty Information Reporting. Our team knows that 99% of the time if there is an issue it will appear in Visual Studio and not the SSRS interface. ![]() After the reports are created, we test all of them on each version of SQL Server. Once these details are all inventoried and returned to SCCM, our customers need to see them in easy-to-read reports. Our products collect extra inventory details about computer warranties, computer monitors, local administrator group names, etc. I documented the process on how I did this in case you need to do the same thing too!Įnhansoft, where I’m the Chief Architect, specializes in SCCM reporting. I say, “normally,” because recently I ran into an issue which meant enabling the publishing option within Visual Studio. Normally, I work on SQL Server Reporting Services (SSRS) reports in Visual Studio until they are done, so I don’t need to deploy SSRS reports directly to the SSRS server.
0 Comments
Leave a Reply. |