Visual Studio SSDT System.Security.Permissions.SecurityPermission
Hi, I have VS 2019 and SSDT installed local on my computer. I have an expression in the textbox, using "Floor", "Abs". When I try to preview the report on my computer, it gives "#Error" In the Visual Studio, window: error list, it shows as [rsRuntimeErrorInExpression] The Value expression for the textrun 'Textbox133.Paragraphs[0].TextRuns[1]' contains an error: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. Note: When I publish this to PBIRS, report works fine. only shows error on my computer's visual studio / ssdt. Also, works on Report Builder when I open ... Any idea? ThanksJan 2020 Power BI Report Server - paginated report rendering issues?
I think we might be running into some version drift issues between the SSDT rendering engine vs PBIRS's rendering engine, and I'm curious if anyone else is seeing something similar? We develop our paginated reports in Visual Studio 2017 (ver 15.9.20), with Reporting Services Projects extension version 2.6.3. I don't have a good way to show it at the moment without exposing some data, but imagine a document map on the left, basic tablix on the right, with a simple header and text box. In Visual Studio, everything renders as expected. When deployed to PBIRS though, the left pane actually says "Document Map" on top with the document map data below. The tablix renders fine, but we're noticing that when clicking on any element in the tablix space, there is a dashed line "selection box" that pops up. As we started looking at that more between different browsers, we noticed it's far worse in IE11 with dashed boxes showing up on-click for even individual table elements, and in Chrome and Chromium Edge, clicking in the tablix space draws the dashed selection box around the entire window, or sometimes just around the text header depending on where you click. We also noticed that a dashed box shows up around the +/- signs in the document map when interacting with those elements. Anyone else seeing this behavior? We're not sure yet if this is due to some policy issue our company pushed out that's effecting browser rendering, or if this is a sign of what we're developing in Visual Studio with SSDT is just drifting more and more from how the PBIRS renderer is handling these elements.PBI Report Server Source Control
Our team has been on PBI Report Server for several months now, and one of the issues that's holding back the adoption of PBI reports vs paginated SSRS reports is the lack of Visual Studio integration and source control. We're long-time SSRS customers, so the entire cycle of using Visual Studio -> SSDT -> publish to SSRS, all using TFS 2012/2015 for source control, is a cycle that is engrained in our processes and works well. For us, PBI reports are just the next step and another tool in the BI reporting toolbox, complementary to paginated reports and not a replacement. But the toolbox we've been given doesn't seem to have a spot to store these new tools. It feels like we're being asked to keep all of our old tools in one box, and then we're told to throw these new tools into a bag in the corner, even though the same company is manufacturing these new PREMIUM tools. :) Metaphors aside, I'm still very confused about Microsoft's vision for BI Reporting teams who use Power BI Report Server and want to have version control on PBIX files. Even if we were full Power BI Premium subscribers, which is unlikely to ever happen in our environment, I don't think Microsoft has even tried to communicate their vision for any kind of verson control for Power BI Premium users either. Not everyone is using these as "self-service" tools - I suspect there are a lot of teams out there like ours who focus on the data aggregation and report creation so their internal customers, the report consumers, can focus on the direct needs of the business. The reality is Power BI Service and Power BI Report Server customers have very different needs, and the only way I can see PBI reports fully meshing into our existing workflows is to see Visual Studio profiles and SSDT extensions added for PBIX report authoring. I can't parse PBIX files the way I parse RDL files either (as far as I'm aware) so that adds another layer of complexity. Not only that, we're believers of keeping the data in the database and having the reports pull the data in real-time, so for now I've recommended our team only use Direct Query PBI reports. Having PBI reports floating around with data embedded in them is just as bad as having piles of Excel spreadsheets all over the place with various versions of untracked data, at least in my experience. Isn't one of the reasons we all started using SSRS in the first place was to encourage users to use web reports and stop creating "New Folder(4)" with "Report002(2).xls" while everyone scratches their heads about which was the right version to use? Does anyone else have similar issues? Is there a grand plan out there to make PBIX reports more "enterprise friendly" for teams like us?
