There is an application which can be described as reporting as well as content management system. Most of the views of the application are tabular reports which can be extracted in excel.
Can anybody suggest a tool which would be useful to handle generation of tabular reports. Sometimes there might be 10-15 columns. Also the tool should have feature to handle documents as well; meaning possibility to upload documents and share the same to the application users.
Please note that the tool may not be open sourced. If there is any licensing cost, that will also holds good.
Thanks!
Use SQL Server reporting service by Microsoft and ASP.Net MVC or JAVA application for all your need.
Link : https://learn.microsoft.com/en-us/sql/reporting-services/create-a-basic-table-report-ssrs-tutorial?view=sql-server-2017
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017
SSRS is an independent reporting tool. Will work for both .Net or Java.
Shortly before Open Text acquired Actuate I stood up an iHub F-Type server on Amazon so that people in my little company could have access to reports and information. Now that the acquision is completed Open Text has discontinued support and availability for F-Type and is directing users like me to full blown iHub which they make available free for 45 days (which they will, so they say, extend to 90 days) and afterwards it is a paid service and not affordable for me.
My question is...how are others providing for cloud based reporting for users in a way that is affordable? I am aware of this project that appears to offer something like what F-Type used to. Has anyone tried this ReportServer? Any thoughts or experiences you could share?
I am also open to other reporting platforms (Jasper, etc.) if they offer what I am after. This would be my least preferable option but my users wouldn't really know or care so I could do it if I needed to?
Download the latest BIRT Runtime Release Build (4.5.0), put the engine in a server, add scripts to run the reports you want.
http://download.eclipse.org/birt/downloads/build.php?build=R-R1-4_5_0-201506092134
Ever since I started to work with TFS 2010 (through VS 2008 if it matters) and was tasked with producing administrative reports, I have had a lot of challenges. I know that there is an API and the Sidekick but neither give the details, scheduling capabilities, zero client involvement, or ease of use that my group requires.
After looking at one of the collection schemas, I only became more frustrated... We aren't using the testing/lab piece of the tool, so the only database relationships available are of little use to us.
My department is heavily involved with reporting branch activity/maintenance/administration, where the primary focus of the canned TFS reports is more towards work items and burn rates (not useful to my department).
Ideally, I would like to know what SQL is involved to achieve this without having to run a profiler against a branching process, decipher the logs, and decrypt all involved SPs/functions/views to identify the programmatic connections between each table involved so that a SSRS report (2008r2) can be developed to provide this scheduled information more dynamically...
I can't be the only person in a Release Management department that wants this info... Can anyone help?
I have requirement of preparing an in-house Project Management and accounting app using Microsoft Dynamics. My requirements are similar to what explained in the below page:
http://community.dynamics.com/product/crm/f/117/p/54453/98182.aspx
Can someone suggest that should we use ERP or CRM? And which one to use i.e. SL, GP, NAV, AX? And why?
CRM is probably the first choice to eliminate. Project management is usually an internally facing application, while CRM is by definition, externally facing. Secondly, if you need to maintain budgets, Dynamics CRM doesn't have anything built in for this (a general ledger for example).
As for the others, each will have its own costs and the extent of support you can get for any of them will vary depending on where your business is located. In some areas you may be able to get good SL support but no NAV or AX for example.
As for one you may not have considered, have you considered Project Server / SharePoint? If you need really heavy weight PM capability, Project may be your best bet. SharePoint can do some PM stuff. There's at least one book around by Dux Raymond Sy, published by O'Reilly. He's also done at least one webcast. Both are based on SharePoint 2007.
HTH
Of the Dynamics ERP products, SL is the one most focused on the project management (i.e. Project Accounting) space. CRM doesn't have a lot of project management capabilities built in, but is probably the most customisable and extendable of the dynamics range.
If you're after something that needs to cover the financial aspect of PM (e.g. billing, tracking costs etc) then you should look at the ERP options. If you're not worried about the financial side, then building a custom solution within CRM might be an option.
Came across this thread in a search I was doing. Hope Sukhminder Singh is still listening...
Sounds like you shouldn't abandon Dynamics CRM, a tool which your organization has tried and tested for nurturing customer satisfaction and turning it into ongoing revenue. On the other hand, you need to maintain a smooth accounting and billing relationship with the same customers - and for that, you'll need an ERP solution. As ccellar suggested NAV can do that, or even SharePoint, as suggested by Mike. I'll hazard a guess your organization already has SharePoint, too.
Now, what about the integration? You know, devising an effective, scalable, and future-proof way for getting MS folk to "talk" is quite a challenge! Also, you need a solution that places stress on human, as well as system workflows. The human factor can be decisive in time-critical projects.
Sukhminder, are you going to be coding solutions on either end? That's one way to go, though often, that option comes with high overheads: dragged-out coding projects, functionality that can be difficult to maintain, and even harder to modify, and serious concerns when one of the systems is upgraded or replaced.
From another angle--are you considering BPM? I'd urge you to.
BPM (Business Process Management) software suites are becoming an increasingly practical and mainstream option as an organization's central integration hub. BPM lets you rapidly map out and control mission critical processes involving multiple systems (as in your scenario). BPM lets you visualize the players, processes and apps over time, and when it comes to adjusting, remapping, and remodeling your workflows, you may have to do some coding, but a large part of the work can be done by experienced, non-programmer BPM users.
There are a bunch of vendors out there, each with its own pros and cons. For the job of connecting MS CRM and MS ERP/Sharepoint, here are 3 candidates I have come across.
Kofax's TotalAgility BMP integrates between Dynamics CRM and SharePoint, by leveraging SharePoint capabilities. The solution obviates elaborate coding by supporting workflows, rules, and user screens. It "orchestrates" processes between itself and other MS and products, most notably SharePoint, CRM, Lync, Visio, Outlook. They enable "in-flight" process change and dynamic BPM, so that down-time on your production is minimal. See the data sheet.
Sequence Business Process Management from PNMsoft. Provides integration with systems from many vendors. The forte is on human-centric processes, with a strong bent for Microsoft products. Sequence lets you integrate with existing systems using wizard-based connectors. When your organization changes, Sequence lets you "hot-swap" your business processes fast, without down time in your production.
MuleSoft's CRM-ERP integration. Their strong point is application integration, for connecting (legacy) systems from a range of vendors, including SAP, Oracle, Salesforce.com, and MS. The Mule ESB is a lightweight integration platform. It comes with a library of connectors to quickly create connectivity with all systems and services, whether on-premise or in the cloud. When adding or modifying an endpoint, you can easily update your integrations to reflect the change.
HTH some....
I'd start off at the Microsoft Dynamics site and explore what each product has on offer. They even have an ERP selector tool for you to try out with just a few questions. Why not contact Microsoft yourself and they could provide a list of potential partners that work in your area - it will be an important decision and they would better guide you through the selection process.
After a few projects which also had an accounting part, I would not recommend to use Dynamics CRM (at least for the accounting part). That's not what it's meant for and you have to spend much effort to get to a level of Dynamics NAV for example.
On the other side: why not combine both systems and use their strenghts.
My organisation is in the final stages of acquiring CRM 4.0 for use as a general purpose software development platform. The company who is selling it to us has convinced upper management that CRM will solve all our productivity problems and make software development as easy as point and click. (They don't read Brooks.)
Having resigned to the fact that I can't stop CRM from being foisted upon us developers, I have been doing research on how to manage the complexities of large scale CRM development.
I have so far identified the following complexities that need to be addressed:
CRM seems wholly incompatible with basic configuration management practices.
Keeping the black box CRM database in bidirectional synchronisation with external LOB systems is both very hard and critical to project success.
What other complexities must I take into account when building a large scale CRM application?
What limitations does CRM have as a development platform?
Edit: This topic provided additional insight.
I've worked with MS CRM 3.0 and now 4.0 here's my take:
Whenever possible focus on standard best practices. Don't get overly confused by what CRM is doing or wants you to do.
Don't be afraid to break what's "supported" by MS. With some caveats on 2 major factors - will your company let you think outside the box to solve problems and do customizations/integrations that are not officially supported? - and are you comfortable enough with .Net, SQL, javascript etc to weave through their code and implement what you need?
I have sometimes banged me head 100 times trying to do something in a "supported" fashion when one small tweak to a js file here or a small db modification there gave me what I needed.
If constant data integration with other LOB apps is critical you should consider a 3rd party tool like Scribe (http://www.scribesoft.com/). It's not cheap but can basically get you 90% of the way when it comes to integrating with your other LOB apps.
As a general rule, MS CRM is great at contact management - doing things like tracking appointments, doing mail merges, etc. Could you use it as your core HR system - probably. Finance system - maybe a bit more difficult. The further you go from it's core competency of performing contact management the more custom work you'll have to do. The more custom work you have to do the more you should consider if MS CRM is the right solution to that problem.
I know you're likely well underway into your deployment of Dynamics CRM, but just a few quick tips:
I'd avoid making unsupported changes purely because it becomes too hard to track the changes eventually. Since Dynamics CRM allows developers to make C# Plugins and access to web services, it's usually unnecessary to make unsupported changes for anything non-trivial. Plus you run the roulette of having to hide changes from MS if you have to call their support. I know many people will include external javascript files (jquery, etc) and other somewhat benign changes, but try to mentally stop yourself when an unsupported edit involves anything non-visual.
Look into the phrase Microsoft Dynamics Xrm, there are several books on the subject that are excellent, http://www.thecrmbook.com/ is particularly good because it comes with some nice custom code to use with your CRM.
Source Control your customizations xml's and don't let people touch the database, also, Google Halan CRM tool, and use it for scripting out CRM customizations and javascript files. Easier than writing custom powershell scripts to do the same job.
Transaction Support
If your application require transaction support from the underlying platform, Dynamics CRM is not the correct choice. The reason is because currently Dynamics CRM SDK web service doesn't support transaction.
The reference thread is here : Does MSCRM web-service support database transactions?
Since you would like to utilize Dynamics CRM as a platform, that means all the business logic should utilize Dynamics CRM SDK Web Services as data access layer. But imagine without the transaction support and you're invoking a series of web service calls as a unit of work, and one of the web service calls fails. That means you potentially will encounter data integrity issue.
Configuration
Usually i create a custom entity called Configuration, which will store all the necessary related configuration for the current CRM application. After it has been created, you can use Dynamics CRM SDK Web Service to read all the necessary configurations from the Configuration custom entity