Browse by Tags
All Tags »
Report Model (
RSS)
I'm developing a report model in Report Builder 1.0 at the moment. I felt like it was finished and started testing the model with some sample reports I knew my client needed. And then I got the oddest thing… I would get a report saying something like: Gender Marital Status Amount of Sales NA NA 865 Male Single 30 Female Single 36 NA was what I chose to put in case I was using referential integrity. I was looking at the sales table and the employees table and if I found a sale which didn't...
I have recently built a data mart containing all the data of budgeting and accounting in SQL Server 2005 and created a Report Model in Report Builder for it. My users were looking for a flexible way to define different grouping on the data, without having to ask for my assistance. Defining new formulas in Report Builder isn't the most comfortable thing to do (specifically if they get complex and long), so we had to find another way. There was a suggestion of creating a view in the database with...
I've recently created a Report Model with a Lookup Entity in it. I saw to it that I had only one default detail attribute for it, and I gave that attribute a ValueSelection of list. When I used the Report Model, I saw the attribute fine (as if it was inside the main Entity) but when I tried to filter on it I saw the Lookup Entity I was trying to hide and a filtered list. I couldn't understand why that was. I went back to check the attribute. Its ValueSelection was of type list. I went to...
Did you, just like me, define a Lookup Entity in your Report Model? And did you, just like me, define friendly names in your Report Model's DSV? If you have, then you may have come across a problem similar to mine… So how did we get there? First and foremost, when you click the relevant tables and columns in your Report Model's DSV, you defined a FriendlyName property for them. That way, when you generate a Report Model based on the DSV with the friendly names, you get the Model with the...
Almost every post I made about Report Builder, be it the pros and cons of creating a report model on a cube or refining a report model based on a cube, brought the same question - what makes reports based on a report model to break and how can you avoid it? Well I didn't know the answer as I admit it never happened to me, (sigh of relief), but the question did bother me enough for me to try and research it a bit more on the internet. And yes, I'm happy to say there is more than enough information...
Creating a Report Model based on an Analysis Cube – Pros and Cons If you follow my blog, you probably know by now that I developed a report model based on the Analysis Services cube I already had. I even got around to updating the report model . And then, my users started using it. And you know, whatever we do just seems so wonderful to us, until our users find all sorts of flaws with what we did… so yes, my users did open my eyes to quite a few problems that may occur when you build...
I recently finished defining and refining a report model based on a relational database. At first, I just set up my DSV and then added a report model with the “Autogenerate” option. Then came the grueling task of refining the report model that was generated… I was using the MSDN pages which were very helpful on that subject, but it’d be fair to say that I something to add to what they suggest for inheritance . See, I was using the inheritance property for my entity and deployed...
I know I had written of the simplicity and ease of creating a report model based on a cube, but I too would have to admit that even a good thing can be made better. Just in case you hadn't noticed, when you enter the report site you can manage your models. If you can't see the "Models" folder, simply click the "Show details" and you'll see it. Select the folder and click on the name of your model or on the "edit" icon next to it. You now have a chance to...
Well I guess congratulations are in order because I finally got around to using a report builder in my project. Turns out that building a report model based on a cube is as easy as 1-2-3. Still I had a problem, as for some unknown reason the translations were showing for my dimension names and my measures, but not for the dimension's attributes... At first I thought maybe this is a problem solved by Service Pack 2 (as my tests were done on a Server with Service Pack 1). Alas, no. So, a further...
Remember how I taught you to recreate your Analysis Project ? Well, let's say this time you have a model you deployed to the Reporting Services Server, but you have changed it since then and want the old version back. So how would you recreate the model you have on the server? First of all, create a new Data Source View in your Analysis Project. It doesn't have to include all the relevant tables, as you'll only use it as a shell to build upon. After you've finished defining the DSV...