Anybody has any idea how to do custom reporting in Team Services without help of Power BI. I can get the test cases and defect data from Excel Add-In but this is not useful as we have to write the Team Services Query all the time.
There are also some lightweight charts and dashboards you can use for the report, refer to this link for details: Dashboards and reports overview.
And beside the Power BI, Analytics service is added to VSTS but it is in preview for now. If you are interested in it, you can contact the Analytics service team: vsts-analytics-supp#microsoft.com.
Related
I am using Power BI Desktop and try to create a live connection (no standard import) to an Analysis Services tabular model in Visual Studio 2017.
In Power BI Desktop, I press Get Data -> Analysis Services.
I use Power BI Desktop with the same credentials as in the Analysis Services model in Visual Studio.
I use Microsoft SQL Server 2017 (RTM).
What am I missing?
Try this check list:
Try to access your cube with SQL Server Management Studio
if not ok -> there is a problem with credential or server. If your computer and the server are not in the same domain it could be an issue
from power bi desktop try import data rather than live connection
can you connect to your model with data tools for visual studio?
The point here is to exclude some configuration to focus on the real problem.
let me know.
I faced this problem today in my work and I make the following and it's working for me
process the whole analysis service project from visual studio, not just the cube or one dimensional
type the name of the database in the Database(optional) and click ok.
tell me if this not working with you
good luck
I am working on Visual Studio 2010 , developing a windows app.
I want to create some simple reports. I am confused about which reports should I use in the application.
The reports which are available in the Visual Studio or the crystal reports.
what are the advantage of report over each other ?
I am working on reports after long time so, can I get some simple links, so I can understand workflow of it.
Crystal Reports seems well documented, more ressources available than Microsoft Reporting
Huge API in CR (just try to print a Microsoft Reporting-report without preview, that's ridiculous!)
Crystal Reports somehow slower than Microsoft Reporting with huge amount of data
Designing reports against custom BusinessObjects is really worse (Wizard isn't even able to "see" objects in another project!) in Crystal Reports
Crystal Reports's preview integration into our apps is much better than in Microsoft Reporting (just try to make your own toolbar!)
Microsoft Reporting's integration in the dev environment is superior to CR (which's habit to implement it's own DB-connection is bad taste)
Both seem to lack designers, our users can use at runtime from within our apps (not external!) to manipulate reports which we prefer to store in the DB (seems to be quite easy with Microsoft Reporting as it's only XML to be stored!) for better managability and deployment.
What is the difference between Query Studio and Report Studio in Cognos?
Could anyone explain me in detail?
Thanks in advance.
Query studio is lightweight add hoc web report writer that allows semi-power users to build ad-hoc reports via the Cognos web portal using prepared data content published to the web portal. Users can sort/filter change font size, do some grouping and aggregation... and save their reports. How ever this report writer is lightweight in that you don't have strong capabilities over presentation format and layout.... in comes report studio which is the enterprise report development tool which can develop pixel perfect reports that have a high degree of interactivity complex condition/conditional layout processing etc... Report studio can edit query studio reports as well. So sometimes users save their Query studio reports but ask for developers to tweak them to get desired appearance/functionality. Both application generate XML files that are stored in the Cognos Repository.
We're looking into migrating to TFS 2010 in the next few weeks. However, we're unclear on what kind of tools are required for the team. We know developers need Visual Studio but what tooling is required for Project Managers and Testers that will ONLY need to manage work items? Do they also need Visual Studio to just view and edit work items?
Project Managers and Testers can use the following methods to access TFS 2010
The web access portal - this allows the ability to create/run queries of work items, and even view source/builds if they want
Excel/Project - Both have integrate with TFS. You are able to load work items directly into Excel/Project, edit them, and publish them back to TFS.
Visual Studio with Team Explorer only - This is a barebones installation of VS, with the Team Explorer only. It doesn't take all that long to install, but it will say "Visual Studio" when launched. Not sure if that is scary to testers/project managers.
Web access provides a good complete set of functionality, but having VS/Team Explorer will provide a rich client experience (read: faster, more responsive).
Additionally, in order to get the Excel/Project integration, you'll need at least the VS/Team Explorer installed on the client box, even if they never use VS. And you need a CAL (Client Access License) to use the web access portal.
So to summarize, TFS provides a lot of ways for the non-developer to interact with the system, but all of them require a CAL, and most of them require installing VS/Team Explorer on the client machine.
In short, they don't need Visual Studio. They can use Team System Web Access (formerly known as TFS Web Access) to do pretty much everything a developer can do, except associate a check-in with a work item. After you install TFS 2010, you simply browse to http://yourserver:8080/Tfs/web and you're in!
Project Managers (and all other team members) can also work with work items from Outlook using 3rd party TFS client embedded in Outlook: TeamCompanion www.teamcompanion.com. This way, assuming they otherwise use Outlook, they wouldn't need to change tools or use any additional tools at all.
As is the case with Excel or Project integration they would still need a TFS CAL and additionally a TeamCompanion license.
TeamCompanion supports much more than just work item management: Email/TFS integration, SQL Server Reports, SharePoint document integration and much more...
Full Disclosure: I am the Product Owner of TeamCompanon, so I may be biased :-).
There is a web front end which you can use to manage the work items. There is also integration to Excel and MS Project.
See http://msdn.microsoft.com/en-us/library/ms181304.aspx for more information on Team Foundation Clients
Already have MSDN with Team System Test Edition, how do I go about getting Developer Edition? Can't find it on MSDN.
Do I need to buy a whole other MSDN license for this?
Can you add just another SKU into the Team System family, in other words, can you have 2 Team System Versions, or does it have to be the Team $uite MegaVersion or single versions?
Also, can you use FxCop with the nice VS shell integration inside of VS Test Edition?
Any URLs/hints would be greatly appreciated. Seems to me that there's very little documentation on how to mix and match VS versions. Would be great if MSFT had a "Visual Studio store" MENU ITEM in VS where you could go and just buy/download the different SKUs automatically. I mean it takes me just a few clicks to download extra states into TurboTax, but MSFT makes that very hard to do.
P.S. Same set of questions for Visual Studio Database Edition.....yes I'm a dev that wears many hats.
There are 3 common levels of licensing that you see:
Visual Studio Pro - Doesn't include any of the team system features
Visual Studio Team System xxxxx Edition - Where xxxx is either Developer, Tester, Architect or DBPro. Includes all the functionality of VS Pro + the functionality associated with the role you chose.
Visual Studio Team Suite - Includes the functionality of all the different role editions.
If you have the VSTS Developer Edition and you want some of the functionality from the other roles, you either have to buy a 2nd VSTS license for the other role, or upgrade to VSTS Team Suite. If I remember correctly VSTS Team Suite is about twice the cost of a specific role version of VSTS, so rather than purchasing multiple role editions most people just opt to upgrade to Team Suite since the cost is approx. the same.
You can compare the list prices here: http://www.microsoft.com/visualstudio/en-us/howtobuy/compare-price.mspx
First, once you logon to the MSDN site, make sure you've clicked the "Downloads" tab at the top of the page, and then near the lower-right click on "MSDN Subscriber Downloads". Software that you have access to at your level of subscription will appear in the list.
Second, you may consider reviewing the details of your level of MSDN subscription if you still don't see what you're looking for.
I hope this helps!
If you will really be using all the different products, then it is best to have the full System license. I think 2 of the products make the price of the full, if you are using 3 ...