One of those annoying things about the US is they use different paper sizes to us Brits. US Letter is 215.9 by 279.4 mm (8.5 by 11.0 inches) The UK equivalent, A4, is 210 by 297 mm (8.26 by 11.69 inches) One of our customers is based in the UK but has remote sales offices in the US, so their SSRS report are set to A4 and when they printed them in the US offices, the footer is cut off....
I’ve had a problem recently when it can to formatting a datetime as just date where FormatDateTime didn’t work The fix was to change it to Format. Oddly, despite the parameter being a datetime, I found I still had to cast it as a date. FormatDateTime was introduced in Vs 2008. I’m not 100% sure why this didn’t work.
Another error I hit Warning 1 [rsRuntimeErrorInExpression] The Value expression for the textrun ‘Textbox28.Paragraphs[0].TextRuns[0]’ contains an error: Overload resolution failed because no Public ‘/’ can be called with these arguments: ‘Public Shared Operator /(d1 As Decimal, d2 As Decimal) As Decimal’: Argument matching parameter ‘d2’ cannot convert from ‘TextBoxImpl’ to ‘Decimal’. C:\Projects\Reports\1. Report.rdl Thankfully Google found Qiuyun answer. I was missing the .Value at the end. So (wrong) =ReportItems!Textbox1 Fixed (working)...
In case you haven’t heard, I’ve started a new job and one of my first tasks was to speed up a SSRS report. One of the first issues I stumbled across was this: An error occurred during local report processing. The definition of the report ‘/1. Report’ is invalid. The Value expression for the textrun ‘Tx412.Paragraphs[0].TextRuns[0]’ contains an error: [BC30456] ‘RdlObjectModel’ is not a member of ‘ReportingServices’ Looking into it the issue it appears its expanded expressions when it got copied – it’s basically making the it fully qualified....
For the past 4 months I’ve been using Visual Studio 2015 rather then Visual Studio 2013 and yesterday, I hit a bug with SSRS (shows how much I love SSRS). The bug appeared when it came to deployment The error was deploying SSRS report Exception calling “CreateCatalogItem” with “7” argument(s): “The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting...
https://twitter.com/matt40k/710468378050339000 It’s nice to see Microsoft fixing old bugs – the I noticed today they updated the MSDN article about Actions in Multidimensional Models. It now supports HTTPS! Woot!! https://connect.microsoft.com/SQLServer/feedback/details/692837/cannot-specify-https-in-an-analysis-services-report-action
Unfortunately this year I’ve not been able to make any of the pre-cons, however the (free) community day looks epic – the hardest part is going to be selecting which session to attend, the final one looking the worst. Aghhh!!! I’m going to have to roll a dice or something! CDC – Change Data Capture in Detail Uwe Ricken What’s new in the SQL Server 2016 for a BI Professional...
I had previously created a SSIS package with a simple Process Full on the SSAS MD database, however, as the project has progressed this hasn’t been ideal. Its basically all or nothing. In order reduce the damage a failure can cause I’ve setup a Process Full for each dimension and cube so each is processed independently of each other. I’ve used the data from the Analysis Services Dynamic Management Views, or DMV for short, which I’ve used for the documentation to feed the foreach loop....
I’ve previously blogged about how I was going to detail how I build and deploy my Microsoft BI projects and to be honest, I’ve been putting it off. The main reason is my work has been looking at Visual Studio Team Services, formally Visual Studio Online and I was looking at using the Build functionality that is included. This should make the whole setup process a lot easier for anyone else trying to replicate my setup....
Today, my pull request for the SSAS deployment script was merged into the Octopus Deploy Community Library. So what is Octopus Deploy and why should I care? Octopus is a friendly deployment automation tool for .NET developers. But don’t be fooled. Octopus Deploy isn’t just limited to .NET developers deploying hip new cloud based applications, it can do much, much more. I currently use Octopus to deploy Jasper reports to our 6 HR environments, I also use it to deploy our HR interfaces which are a series of SSIS packages and SQL objects which uses Microsoft SQL Server 2008....
I’ve spent a while today trying to change the text direction (orientation) of a header on a SSRS report – the option was rather oddly placed in Visual Studio – the option is within the properties (for the text) Localization > Writing Mode > then change from Default to either Rotate270 or Vertical. I was hoping it would be within the Font options. Guess that would be too easy 😉
Todays problem, missing the reporting data toolbox in Visual Studio 2013 – once again, a different menu options. Open the actual report (.rdl) View > Report Data Alternatively press Ctrl + Alt + D