Printing a Web Intelligence document isn’t a necessary evil- it’s simply necessary. And SAP should graciously support users who work in industries where a printer is required equipment.
Back in 2011 when I wrote All the Desktop Intelligence That’s Fit to Print, I was working on what I hoped would be my last project migrating Desktop Intelligence documents to Web Intelligence. Fast forward six years to 2017 and I’m still helping several customers retire Desktop Intelligence. And in 2017, the Web Intelligence Job Server still doesn’t have the schedule-to-printer functionality that existed for Desktop Intelligence and is still available for Crystal Reports users.
This year, the SAP Idea Place moved to a new home- the SAP Customer Influence portal. The idea to Schedule Webi documents to a Printer– submitted by Brian Thomas on January 10, 2011- was reviewed by SAP and set to “not planned”, despite the idea currently having 64 votes- many more than the ten votes SAP required for consideration. The idea has comments from Web Intelligence users across multiple industries making their case for schedule-to-print.
Instead, Samuel Polichouk, an SAP product expert in Paris where Web Intelligence is developed, wrote:
In our world which become more and more “mobile”, printing is not something we would like to invest in scheduling webi documents. Therefore I prefer to set expectation saying that we will not include this in our backlog for coming releases.
Please continue to vote for this necessary idea and hope that SAP will review its position on the matter, bringing much-needed printing capabilities enjoyed by Desktop Intelligence and Crystal Reports users to the legions of Web Intelligence fans.
UPDATE: Voting is closed for this particular idea; however, I’d be grateful if you’d leave a comment on this article describing a use case for Webi printing or why you support adding this feature to the platform.
I know it was not webi but my problem is with the comment made by the person who says printing not required
SAP has put yet another nail in the coffin of Desktop Intelligence.
SAP has put yet another nail in the coffin of Desktop Intelligence with Free-Hand SQL in the recent release of Support Pack 6 for SAP BusinessObjects Business Intelligence 4.1. Steve Yemm has put together an excellent tutorial on the SAP Community Network (see related SCN article, Web Intelligence Free Hand SQL (FHSQL)/Stored Procedures in BI4.1 SP06). I’d like to show just a couple of extra formatting nuances not in Steve’s article.
Free-Hand SQL isn’t a silver bullet (see related article, Free-Hand SQL Isn’t Free), but it is a bullet. It can help query data that no existing universe can access. Web Intelligence now uses a workflow that will seem very familiar to Desktop Intelligence users.
I’m going to use the Web Intelligence Java applet and choose the new Free-Hand SQL option for creating a new document.
Next, I’ll choose a universe connection.
For my query, I’ll paste SQL from an eFashion query for Year, State, and Sales Revenue into the Query Script editor, essentially a large text box.
The Query Script “editor” provides the same editing features as its Desktop Intelligence predecessor- none. However, it is possible to validate that the SQL you pasted from elsewhere is valid.
Notice that Web Intelligence inferred that the aggregate function SUM should be interpreted as a measure object. However, the object naming isn’t terribly creative.
That is why you’ll want to add aliases to your SQL statement.
You can manually rename objects, which is helpful for setting column headings. Here I changed Sales_Revenue into Sales Revenue.
And voila! The results are exactly what we expect. Except unlike data from the eFashion universe, measures aren’t well-formatted.
Simply right-click on any value in the Sales Revenue column and choose Format Number. It’s near the bottom of what seems to be the world’s longest right-click menu. Does anyone else hope that Web Intelligence 4.2 will have shorter right-click menus?
Choose the desired numeric format.
And there you have it, a Web Intelligence document that uses Free-Hand SQL.
Some additional observations. The new Free-Hand SQL is also available in the Web Intelligence Rich Client…
However, it is missing from the HTML panel.
UPDATE: The Free-hand SQL option now appears in the BI 4.2 SP4 HTML panel, where only the Analysis View query option is missing.
In addition to creating new Web Intelligence reports from Free-Hand SQL, this feature provides new capabilities to the Report Conversion Tool, which were actually introduced earlier in Support Pack 5. Prior to SP5, Desktop Intelligence documents with free-hand SQL were converted by placing the SQL into a derived table of a new universe (see related article, Retiring Desktop Intelligence Free-Hand SQL). This approach could become problematic when hundreds of Desktop Intelligence documents were spawning hundreds of new single-use universes. The Report Conversion Tool no longer needs to create a universe to successfully convert free-hand SQL documents.
In its continuing effort to gain traction in the crowded data discovery market, SAP is enlisting the help of a trusted brand name: Desktop Intelligence™. The change is expected to be announced next month at its annual SAPPHIRE NOW user conference in Orlando, Florida. SAP analytics users have been down the rebranding road before. “Project Hilo” was launched at SAPPHIRE NOW 2012 as SAP Visual Intelligence (see related SCN article) then rebranded as SAP Lumira just one year later at SAPPHIRE NOW 2013 (see related SCN article).
According to SAP spokesperson April Erste, yet another re-brand was warranted because “highly-respected industry analysts made fun of Lumira’s seemingly pharmaceutical-inspired name.”
In addition, SAP’s corporate clientele mistakenly believed that increasing the number of “Lumira users” in their organizations would lead to skyrocketing prescription drug costs, often resulting in a buying decision for rival data discovery tools such as Tableau or Qlik.
The new branding will be applied to what was previously known internally as SAP Lumira version 1.26 and will introduce bold new features like a redesigned “slice-and-dice” panel, the ability to import queries from “classic” Desktop Intelligence (see related article, True Desktop Intelligence with SAP Lumira) and a new splash screen that incorporates nostalgic cues from the original BusinessObjects product SAP acquired in 2007. Continuing to integrate technology from SAP’s KXEN acquisition, the new release includes an automated (and animated) assistant to help casual users who are not trained statisticians add predictive capabilities to their visualizations. The animated Deski the Dachshund™ provides a light-hearted interface to business users who fondly remember Clippy, the animated assistant from Microsoft Office. “It’s like Apple Siri for analytics,” says Ms. Erste, clearly beaming with pride.
This isn’t the first time SAP has tried to resurrect the Desktop Intelligence brand name, but SAP is hopeful their second attempt will have better success. “We introduced a brand-new Desktop Intelligence product in 2012,” continues Ms. Erste, “but initial reaction from ramp-up customers was chilly and we ended up scrapping the effort” (see related article, Hell Freezes Over). The upcoming Desktop Intelligence rebrand will be supported with a global multimedia campaign featuring Jennifer Lopez, who co-wrote the campaign song, “Don’t Diss Deski,” with long-time collaborator Cory Rooney and Alan Wilkis (Big Data). Ms. Lopez will first perform “Don’t Diss Deski” publicly during her concert appearance at the SAP SAPPHIRE event. Its accompanying music video, directed by James Frost (OK GO, Radiohead), will be promoted on SAP’s social media channels with a special #DontDissDeski hashtag.
Unfortunately, I won’t be attending SAPPHIRE this year but it’s shaping up to be a great event. What are your thoughts on SAP’s plans for Lumira?
Free-Hand SQL is a good short-term solution but a poor long-term solution.
Editor’s note: I’m a bit embarrassed that this article has languished in draft mode for almost two years as I try to clean out my backlog of unfinished blog articles. But it’s still a relevant topic to discuss.
With custom dimension grouping finally added to SAP BusinessObjects Business Intelligence BI 4.1 SP2, the functionality gap between legacy Desktop Intelligence and its successor Web Intelligence is largely closed. One large gap remains, although it’s a controversial gap in my view.
Three words- Free-Hand SQL.
Free-Hand SQL is a feature of legacy Desktop Intelligence that allows a report to be created from a hand-crafted SQL statement. It’s typically used when there’s not enough time to create a universe. A highly normalized data model is sometimes too complex to model generically in a universe and nobody wants to bother transforming it into a star schema. Web Intelligence presently doesn’t support Free-Hand SQL, but the Report Conversion Tool does an adequate job of converting existing Desktop Intelligence documents that use it to Web Intelligence (see related article, Retiring Desktop Intelligence Free-Hand SQL).
Looking forward to real-world customer story: Zurich Insurance, retiring DeskI. I want to know what to do about no Free Hand SQL #SBOUC
The user interface for Free-Hand SQL is spartan, so the query is usually crafted elsewhere in a tool with better SQL editing features such as Microsoft Access, TOAD, or the SQL editor provided by the database vendor then simply pasted into a humble box in Desktop Intelligence.
It’s a pretty basic box, without any tools to help the Desktop Intelligence user fashion a well-written query. You can validate the final result, though.
My friend and SAP Mentor Greg Myers had this exchange a few years ago when Free-Hand SQL was first mentioned on the Web Intelligence product roadmap.
Matthew elaborates on several valid technical considerations, but this one stands out.
There is no central control over the SQL with free hand SQL. Should the database change, corrections needs to be made, or improvements made, then each and every document containing that free hand SQL needs to be inspected and manually updated. Compare this to the semantic layer where one change is made and that change is automatically propagated to all related documents.
In other words, maintenance nightmare! Free-Hand SQL is difficult to manage. If the data model or reporting requirements change, the task of tracking down and updating the offending SQL is tedious and time consuming. Of course, the manager that told you to “just get it done” with Free-Hand SQL won’t be around when the maintenance requests come in- she put “agile BI project management” on her resume and now has a much better paying job than yours.
SAP no longer supports SAP BusinessObjects Enterprise XI R2. But unfortunately, it still supports the decade-old philosophy that “all features of Desktop Intelligence must be crammed (eventually) into Web Intelligence”. In my view, a better approach would be to ask “where is the best place in the platform to support users that need to write free-hand SQL” and “what features can we add to the platform to support the lifecycle of free-hand SQL”. There’s an opportunity here to share SQL query design-time features across multiple tools in the BI suite, possibly leveraging some of the existing query builder functionality in Crystal Reports.
Although it first appeared on the official roadmap nearly two years ago, Free-Hand SQL in Web Intelligence does not have a public timetable. It is not mentioned in the “What’s New” document for SAP BusinessObjects BI 4.1 Support Pack 3 expected to ship at the end of this month. Unless SAP changes its mind, Free-Hand SQL is coming to a future version of Web Intelligence (UPDATE: Free-Hand SQL was delivered in BusinessObjects BI 4.1 Support Pack 6 – see related article Web Intelligence and Free-Hand SQL). But if we must have Free-Hand SQL in Web Intelligence, can we at least have something more elegant than a big box?
How do you feel about the SAP product roadmap for Free-Hand SQL?
Modernizing Desktop Intelligence without leaving the desktop.
Last October, I performed a system health check for a customer using SAP BusinessObjects Enterprise XI 3.1. SAP BusinessObjects is an OEM package that comes with the financial system that runs their large yet highly specialized business. Like their industry peers that use the same solution, the company has upgraded from classic BusinessObjects 5 and 6 to XI R2 and currently XI 3.1, meaning that Desktop Intelligence is the overwhelming source of reports that help them run their business. Aside from the sample documents and universes provided by their ERP vendor, nearly all of the Desktop Intelligence documents live out in the wild, on desktops throughout the organization. Of course, the BI 4.1 platform offers limited support for Desktop Intelligence (see related article, Desktop Intelligence, Back for a Limited Time). But everyone, including this XI 3.1 customer, recognizes that the Desktop Intelligence Compatibility Pack is only a short-term solution.
I’ve seen this Desktop Intelligence scenario a lot since XI R2 was first introduced nearly 10 years ago. As part of my health check, I first made sure that the current hardware was sufficient to support the proposed number of simultaneous Web Intelligence users. Then I made sure that enough Web Intelligence Processing Servers and connections would be available. I explained to the customer the need to work with key stakeholders to identify critical Desktop Intelligence documents, export them to the BI platform into a well-designed folder structure, then convert them to Web Intelligence using the Report Conversion Tool.
This strategy made sense in 2004. But does it continue to make sense in 2014?
As business intelligence professionals, we’ve spent the last 10 years mocking desktop software and worshiping at the altar of web-based software. We’ve rolled our eyes at Desktop Intelligence diehards and showed no sympathy to users that have waited 10 years for SAP to deliver grouping functionality (it finally arrived in BI 4.1 SP2). We laughed in the face of WebiJavaGeddon (see related article, Never Let a Serious Crisis Go to Waste). But today a new business intelligence revolution is occurring and its back on the desktop where it all started (see related article, Nobody Ever Got Fired for Buying Tableau). Delicious irony.
What if old Desktop Intelligence documents could be modernized without leaving the desktop? What if SAP Lumira could open a Desktop Intelligence document? And even if it couldn’t replicate the tables and charts accurately enough (or at all), what if it at least imported the document’s data providers properly? Ideally, a desktop BI user could convert the documents themselves rather than bundling them up for the IT department’s Web Intelligence conversion project. Self-service BI upgrades, not just self-service BI.
Sadly, the idea was rejected— “not planned by SAP”— because “Web Intelligence is the natural upgrade path for Deski documents.” As much as I love Web Intelligence, I would argue that it’s the historical upgrade path for Desktop Intelligence documents. It’s no longer the logical upgrade path and should no longer be the only upgrade path.
As items gain popularity through the votes of members in the community, moderators engage in dialogue about those ideas. Cecile [Hudon] notes, “We encourage the moderators to comment and look for responses to the most popular ideas each week, and also look for diamond in the rough ideas— innovative ideas that have low point scores because they may be too new of a concept for people to recognize as a good idea.” [emphasis mine]
This business intelligence barista thinks a Desktop Intelligence extension for SAP Lumira qualifies as a diamond in the rough idea. I hope SAP will give the idea a second look.
What do you think of my idea for SAP Lumira and Desktop Intelligence? Would you consider voting or adding a comment to my idea on the SAP Idea Place?
Disclosure of Material Connection: I received this book free from the publisher. I was not required to write a positive review. The opinions I have expressed are my own. Some of the links in the post above are “affiliate links.” This means if you click on the link and purchase the item, I will receive an affiliate commission. Regardless, I only recommend products or services I use personally and believe will add value to my readers.I am disclosing this in accordance with the Federal Trade Commission’s 16 CFR, Part 255: “Guides Concerning the Use of Endorsements and Testimonials in Advertising.”
Desktop Intelligence is an integrated query, reporting, and analysis solution for business professionals that allows you to to access the data in your corporate databases directly from your desktop and present and analyze this information in a Desktop Intelligence document.
Desktop Intelligence makes it easy to access this data, because you work in familiar business terms and non technical database terms like SQL. Once you have used Desktop Intelligence to access data, you can present information in reports as tables, or as sophisticated dynamic documents with drillable charts.
Desktop Intelligence lets you access data from a wide range of sources. You can access data from a number of sources:
Personal data files
Freehand SQL server
XML data provider
VBA data provider
Now remember kids, Desktop Intelligence is not coming back.
Seriously, there is no Desktop Intelligence 4.1. What the Report Compatibility Pack provides is the ability to use Desktop Intelligence XI 3.1 in a limited way with BI 4.1 to ease migration to the new platform. Only Desktop Intelligence Service Pack 6 Fix Pack 6.1 or higher will interact with BI 4.1.
While the product description above was undoubtedly lifted from an old Desktop Intelligence manual, seeing it in the “What’s New” guide made me laugh. I hope it made you laugh, too.
Will your organization adopt the Desktop Intelligence Report Compatibility Pack? Finally convert its remaining Desktop Intelligence documents to Web Intelligence using the Report Conversion Tool 4.1? Was Desktop Intelligence retired long ago? Or never adopted in the first place?
Much attention has focused on the Web Intelligence feature gap with Desktop Intelligence. But recent security concerns have focused attention on the other Web Intelligence feature gap.
Ever since the 2004 BusinessObjects roadmap described the eventual retirement of Desktop Intelligence, much attention has been paid to the feature gap between Desktop Intelligence and its successor Web Intelligence. Today, the feature gap is much more narrow than it was in Web Intelligence 6.0 or even Web Intelligence XI R1 or XI R2 (remember when lack of support for synchronized data providers was a big deal?). And Web Intelligence has evolved to contain exclusive features like input controls, advanced charting and mobility support. When Desktop Intelligence disappeared with the release of SAP BusinessObjects Business Intelligence 4.0 two years ago, concerns from long-term customers become more pronounced. The forthcoming Desktop Intelligence Compatibility Pack will debut later this year in BI 4.1 to address those concerns. And the current product roadmap will continue closing the Deski-to-Webi feature gap in BI 4.1 and BI 4.2.
But there is a second Web Intelligence feature gap that demands increasing attention, and that is the gap between the HTML (web) and Java-based (Rich Internet Application) versions of Web Intelligence. The best Web Intelligence experience has always required Java in the web browser and BI 4.0 is no exception. The web version continues to evolve but is always behind its more powerful Java-based relative.
Here are the preferences in the SAP BusinessObjects Enterprise XI 3.1 InfoView portal:
And here are similar preferences in the SAP BusinessObjects Business Intelligence 4.0 BI Launch Pad:
Despite the name changes from version to version, there’s always a Java and a non-Java version of Web Intelligence.
In BI 4.0, the following features are currently exclusive to the Java-based Rich Internet Application:
Query support for BEx and Analysis Views
Custom Cascading Style Sheets
Custom number formats
Many usability features in the Java-based UI, including Data View
There’s also a third feature gap- Web Intelligence features like bullet graphs and scorecards that are only supported on the Mobile BI app- but I’ll discuss those in a future article.
Ten years ago, it was impossible to create rich, engaging web applications without relying on plugins like Java or Adobe Flash. However, today’s modern browsers provide a different canvas for application developers to paint on. Tomorrow, on Wednesday, March 6, 2013, ASUG and SAP will present a webcast entitled What’s New in Web Intelligence 4.1. I hope that we’ll see that the roadmap for Web Intelligence leads to a Java-free future.
How is your organization coping with Java security woes?
What were the top 10 SAP Analytics news stories of 2012?
Join Diversified Semantic Layer hosts Greg Myers, Jamie Oswald, and Eric Vallo along with contributors Josh Fletcher, Clint Vosloo and myself in an end-of-year podcast to count down the top 10 SAP Analytics news stories of 2012.
Since the release of SAP BusinessObjects Business Intelligence 4.0, the SAP support center has been flooded with angry callers demanding the return of “f-ing Desktop Intelligence”. SAP has responded directly to this customer feedback and started a new development initiative. It’s known internally as the FUll Client Compatibility Kit, or simply its acronym. The official name of the add-on is the Desktop Intelligence Compatibility Pack (DCP)- although the name sometimes appears incorrectly as the Desktop Intelligence Compatibility Patch. It will be released in 2013 as part of SAP BusinessObjects Enterprise XI 3.1 Service Pack 6.1. Thomas Kuruvilla announced the DCP earlier this year at the ASUG SAP BusinessObjects User Conference and gave an updated presentation and demo yesterday in an ASUG webcast.
What is the Desktop Intelligence Compatibility Pack?
The Desktop Intelligence Compatibility Pack will permit Desktop Intelligence XI 3.1 Service Pack 6.1 to connect to the SAP BusinessObjects Business Intelligence 4.1 platform (BI 4.1). Both products are tentatively slated for release in May 2013. The Report Conversion Tool 4.1 and Upgrade Management Tool 4.1 will also have enhancements to support the Desktop Intelligence XI 3.1 SP 6.1 client.
What is missing from SAP BusinessObjects Business Intelligence 4.0 and will still be missing in 4.1 are the server-side components of Desktop Intelligence. In other words, the Desktop Intelligence Cache Server, Processing Server and Job Server will not be ported to the BI 4.1 platform. The absence of these servers defines the capabilities of the Desktop Intelligence Compatibility Pack and how it works.
The Desktop Intelligence client must be upgraded to XI 3.1 Service Pack 6, Fix Pack 1
The BI 4 platform must be upgraded to SAP BusinessObjects Business Intelligence 4.1
Desktop Intelligence documents can be imported and stored on the BI 4.1 platform via the Upgrade Management Tool
Desktop Intelligence documents cannot be viewed via the BI Launchpad (formerly InfoView), but only via the Desktop Intelligence XI 3.1 application
Desktop Intelligence documents cannot be scheduled on the BI 4.1 platform. They can only be scheduled from the Windows desktop using “lightweight scheduling”
Although Desktop Intelligence documents cannot be viewed on the BI 4.1 platform, scheduled instances in agnostic formats like Adobe PDF or Microsoft Excel can be viewed via the BI Launchpad
It is unclear at this time what features will be added to Web Intelligence 4.1 to help continue to close the feature gap between Desktop Intelligence and Web Intelligence
If your organization has already retired Desktop Intelligence, pat yourselves on the back.
If your organization is still working on Desktop Intelligence retirement, the availability of the DCP should not slow or alter your retirement plans. The dates for retiring Desktop Intelligence are unchanged. Maintenance will end in 2015 and Priority One support will end in 2017. Keep moving ahead.
If your organization has not yet begun Desktop Intelligence retirement, the availability of the DCP is encouraging. But the Desktop Intelligence Compatibility Pack is not going to solve your problems. You ultimately have to retire all of your Desktop Intelligence documents (see related article by Eric Vallo and Thierry Audas on the SAP Analytics Blog, Better Content Migration to SAP BusinessObjects BI 4.0).
What are some drawbacks of the Desktop Intelligence Compatibility Pack?
There are several.
First, your Desktop Intelligence users will have to upgrade their systems to Desktop Intelligence XI 3.1 Service Pack 6 Fix Pack 1. Depending on the size of your Desktop Intelligence user base, just getting the new software in place will be a challenge.
Second, because it is a fix pack, there will be two components to the installation. First, your users will have to install a full build of Desktop Intelligence XI 3.1 Service Pack 6. Then, they will need to separately apply Fix Pack 6.1. (NOTE: SAP has since shipped XI 3.1 SP7 and an SP8 is planned, theoretically eliminating the need for a separate patch).
Third, because there is no server-side scheduling, at least some of your desktop systems will have to remain powered on around the clock to support off-hours schedules.
Fourth, until we see the final product, there’s no guarantee that your existing Desktop Intelligence solution will map into the DCP solution as-is. For example, existing Desktop Intelligence-based publications or Desktop Intelligence documents that create HTML output may require workarounds to keep working on the BI 4.1 platform.
An Interesting Alternative
In January of this year, I referred to Xcelsius as “the new Desktop Intelligence” (see related article Thoughts on Xcelsius). I made the comparison because Xcelsius is based on dying Adobe Flash technology and Desktop Intelligence is based on dying 32-bit Windows technology. What I did not foresee at the time was renewed interest in desktop analytic applications like Tableau, Tibco Spotfire, and QlikView. Nor could I foresee that SAP would respond by announcing their own desktop data discovery tool, SAP Lumira (originally introduced SAP Visual Intelligence), in May 2012 at its annual SAPPPHIRE event in Orlando, Florida. While very different and very modern, SAP Lumira is the spiritual successor to Desktop Intelligence.
In just a few short months, there have been eight iterations of SAP Lumira. The product shipped with only SAP HANA support but today provides support for free-hand SQL, classic UNV universes, and new 4.0 UNX universes.
So here is my suggestion.
Allow SAP Lumira to open a Desktop Intelligence document. And not just a version XI 3.1 document, but XI 3.0 and XI R2 as well.
Still with me? SAP Lumira does not need to fully recreate the document format as the Report Conversion Tool does. It only needs to import the Desktop Intelligence queries. From there, users can create visualizations that could never be realized with Desktop Intelligence.
Adding Desktop Intelligence support to SAP Lumira isn’t a silver bullet. But neither is the Desktop Intelligence Compatibility Pack. Or for that matter the Report Conversion Tool. But it gives users that prefer the desktop experience of Desktop Intelligence another robust desktop experience. It provides options.
The SAP Lumira development team has demonstrated that they can move quickly. With agility. There’s plenty of time to add this capability in time for the May 2013 release of the other products.
Above all, remember that your users don’t just have Desktop Intelligence documents on their desktops. Those documents address business challenges. And in 2012 the SAP BusinessObjects BI platform has a lot more crayons in its analytics box than when those Desktop Intelligence documents were originally authored.
So don’t just help users get rid of an unsupported document format. Help them run their business. Help them run better. For many of these users, getting the documents converted to Web Intelligence will be sufficient. But for others, use your imagination.
Desktop Intelligence is fading away. But there’s never a dull moment in business intelligence.
Hell Freezes Over was the name given to a tour and accompanying 1994 live album by the Eagles after a fourteen-year-long break up. The name came from a statement Don Henley once made when asked when the band would get back together. Hell Freezes Over could also be the code name SAP is using for its next version of the SAP BusinessObjects Business Intelligence platform. Responding to customer demand, Desktop Intelligence (aka Deski) is returning to the SAP BusinessObjects Business Intelligence platform as part of next year’s 4.5 release.
“Customers have spoken and SAP has listened.” according to April Erste, SAP spokesperson for business analytics. “Primarily because of its integrated Visual Basic scripting, key customers have deployed Desktop Intelligence in various office automation scenarios- some quite sophisticated- and we want to continue to support those customers.”
Long time Desktop Intelligence customers are thrilled with the news. Greg Myers, SAP Mentor and Desktop Intelligence fan had this to say about the renaissance of Desktop Intelligence.
Desktop Intelligence 4.5 is totally the sh*t.
“Many of the developers from the original Desktop Intelligence are no longer with SAP and the code is difficult to maintain,” revealed Erste, “so we are using this as an opportunity to rewrite major portions of the product and make it 64-bit, even though the other client applications will remain 32-bit until a future major release.” The SAP BusinessObjects Desktop Intelligence 4.5 UI has been freshened up with a Microsoft Office 2010-style ribbon replacing the traditional menu and toolbars from the previous version. Other features include a redesigned and more powerful Visual Basic scripting engine, a new shared charting engine first introduced with Web Intelligence 4.0 (Webi) and support for UNX universes created with the new Information Design Tool. There will be updated database support, including Microsoft SQL Server 2012 and Teradata 13 in addition to SAP’s own HANA and Sybase IQ. On the server side, new 64-bit services will power larger and more complex reports compared to the 32-bit servers they replace.
Ms. Erste stated thatSAP has prototypes in the lab but currently has no plans to add Desktop Intelligence support to the BI Mobile app. “Our primary focus for this iteration was the desktop experience and Microsoft Office automation, but we will continue to listen to feedback from the user community,” she added. Ms. Erste had no comment on rumors that partners were working on add-on solutions for Desktop Intelligence mobility.
Jody Bankston, currently leading CBL Properties through a painful conversion from Desktop Intelligence to Web Intelligence, is ecstatic. “We were looking at empowering our users with SAP BusinessObjects Explorer and interactive Web Intelligence reports, but that was going to take a lot of work and difficult change management. AND you still don’t get Fit to Page printing with Web Intelligence XI 3.1! We’d rather just keep running the same old reports and print them. Yeah, the return is small, but the investment is practically zero…so our ROI is HUGE!”
Mark Bradbourne, a BI architect at Forest City Enterprises and member of the ASUG Desktop Intelligence to Web Intelligence Influence Council agrees. “There’s still a lot of passion in the BusinessObjects community about Desktop Intelligence. We had members of the council literally breaking down in tears during our deliberations. But everyone is excited about the future”.
But not everyone agrees that SAP’s moves are in the right direction. For some customers, hell is not only freezing over but SAP is driving at top speed on the highway to hell. Jamie Oswald, SAP Mentor and long-time Desktop Intelligence opponent, had this to say:
Desktop Intelligence is an old dinosaur. SAP is having trouble supporting the tools that they already have. I can’t see how resurrecting an old tool improves anything, especially for customers looking for innovation in newer products like Explorer, the mobile BI apps, and the rumored Zen project.
Desktop Intelligence 4.5 will go into ramp-up next year along with the rest of the SAP BusinessObjects BI 4.5 suite. No official date for the ramp-up has been announced.