OBIEE 11g training for Oracle BI Partners


OBIEE 11g Training

Last week, the ClearPeaks Academy provided another OBIEE 11g Bootcamp training for Oracle BI Partners, this time in Oslo (Norway). The attendees of the course had in general very low or null experience with OBIEE 11g. With this scenario, the biggest challenge of the bootcamp was to bring them up to speed in record time (5 days). The trainer was Alex Caminals, our ClearPeaks Academy Manager, who has been providing training courses for more than 7 years in the BI space and also accumulates more than 12 years bringing hands-on knowledge and experience in BI projects. The feedback from the attendees was excellent and that is encouraging Oracle to keep relying on the ClearPeaks Academy to train their BI Partners in EMEA.

If you want to get some information about the ClearPeaks Academy training courses or OBIEE 11g training, please visit our Academy page or contact us via our web page form or by sending an email.

Pop up effect in OBIEE Answers & Dashboards using jQuery


In this article of our OBIEE Customization Series I will show you how to implement a tooltip (a pop up window displayed when hovering over an element) in OBIEE Answers and Dashboards. The tooltip can provide additional details (like an explanation of a KPI) or load content such as target report.


For our example let’s imagine we have a summary level report with purchase orders listed. We can navigate to order details level, but that would require leaving the current page or opening the content of detail report in a new window. What if we could have a summary level report and peek into details on the same page? Implementing the dynamic navigation to a report inside the tooltip will allow us to achieve that.

Because OBIEE Answers and Dashboards allow using web technologies such as HTML5, JavaScript, CSS3, and AJAX we are able to customize the look and user interface of any report just like we can do with websites. To achieve that, we will use the most popular JavaScript library called jQuery. It’s an optimized .js file containing Document Object Model (DOM), events, effects and Ajax functions that can be called from the report. JQuery is widely used in website development and allows implementing complex components using pre-defined methods defined in library. For the tooltip we will need also a plugin, an additional library that defines the effect. There are many available plugins for tooltip functionality both free and requiring paid license. Many UI libraries such as jQuery UI or Kendo UI offer, among others, a tooltip functionality. For the example in this article we will use the Tipped tooltip library, which offers a lot of customization options but requires a licence for commercial use.
As an example in this article we will invoke a tooltip that loads the contents of target report when hovered on a column’s value. To create this effect we will need to use AJAX technology. Such method is already included in the jQuery library. We will need to specify the target page or report from which the external content will be loaded.

Implementing the tooltip

Let’s start by creating a simple report showing Order Number, Number of Order Lines and Order Cost.


Our objective here is to provide additional information of the orders displayed in the first report but without navigating. Therefore let’s create another simple report that will contain more details on a given Order and its Order Lines. We need to add a filter - Order Number is prompted to enable navigation.


Let’s go to the results tab and edit the views. The contents of this report will be displayed in a tooltip. We can add a pie chart with breakdown of the line cost and save the report as Order Lines Report.


Let’s get back to the main report. We will need to add a static text view with code to load libraries. Those files could be referred pointing to the file on the internet (we can do it by loading jQuery library from google developers and for example jQuery UI library which contains tooltip functionality). However we should have those files on our OBIEE server. Often internal network security settings disallow loading content (especially script files with .js extension) from external sources. A one-domain policy is used to prevent security breaches. Because of that we will need to save those library files on OBIEE server. To be able to link a file on a OBIEE server we will need to create a virtual directory on OBIEE server in weblogic settings.
When we have the virtual directory created we can refer to the libraries using such link: http://localhost:9704/userfiles/jquery.1.9.0.min.js



First, we need to load the jQuery library:

<script type="text/javascript" src="http://localhost1:9704/user_files/jquery-1.9.0.min.js"></script>

Tipped libraries:  

<script type="text/javascript" src="http://localhost:9704/user_files/Tipped/tipped-3.1.8/js/tipped/tipped.js"></script>
<script type="text/javascript" src="http://localhost:9704/user_files/Tipped/tipped-3.1.8/js/excanvas/excanvas.js"></script>

Tipped CSS stylesheet, which contains the styles used for tooltip customization:

<link rel="stylesheet" type="text/css" href="http://localhost:9704/user_files/Tipped/tipped-3.1.8/css/tipped/tipped.css"/>

Then let’s edit the column formula to dynamically generate a tooltip with navigation to Order Line Details.



We need a couple of elements here. Instead of just "Order"."Order Number" column value we need to embed some more elements in the formula code. The code inside will contain HTML tags so let’s mark Constains HTML Markup option.


For our example we will need to use the following column formula: '

'<div id="popup' ||"Order"."Order Number"|| '">
' ||"Order"."Order Number"|| '
||'<script type="text/javascript"> Tipped.create("#popup' ||"Order"."Order Number"||'",||"Order"."Order Number"||'",||"Order"."Order Number"||'", "saw.dll?Go&path=%2Fshared%2FUnder%20Developments%2Ftest-tooltip-nav&Action=extract&p0=1&p1=eq&p2=%22Order%22.%22Order%20Number%22&p3='||"Order"."Order Number"||'",
{ajax: true,
 hook: "bottomright",
 border: { size:1},
 afterUpdate: function()
} );

To separate HTML formatting from the OBIEE column value ("Order"."Order Number") we will need to use single quote (') and to merge HTML formatting with the column value we need to use concatenate (||).

<divmarkup is a placeholder for our tooltip. Its id is generated dynamically by concatenation with value of the "Order"."Order Number" column.
Here we initialize Tipped script and call plugin’s method to create a tooltip. The syntax of the script to create a Tipped tooltip is as follows:
<script type="text/javascript">
Tipped.create("#target", "url", { ajax: true });

# is a jQuery selector that points to a single element with the given id attribute, in our case #popup div concatenated with Order Number. Then there is a url with the external content to be loaded inside ("url"). The important part here is the ajax: true option, which allows loading of external content.

<script type="text/javascript"> Tipped.create("#popup' ||"Order"."Order Number"||'

So basically, the popup will display whatever contents are displayed in the url, therefore we can pass a GOURL link to the detail report passing the order as a parameter. Note the Extract parameter which displays just the results of target report in a format without the paging control, hot links and other elements.

"saw.dll?Go&path=%2Fshared%Reports%2FOrder%20Lines%20Report &Action=extract&p0=1&p1=eq&p2=%22Order%22.%22Order%20Number%22&p3='||"Order"."Order Number"||'"

Here we specify the formatting options of the tooltip. For Tipped tooltip to load external content we will need to use  ajax: true option. Tipped offers richness of customization options for skins, positioning and effects.

{ajax: true, 
 hook: "bottomright", 
 border: { size:1}, 
 afterUpdate: function() 

Because the column formula does not include the whole script (it references to the scripts loaded in the Narrative View) we will get a “Formula syntax is invalid” error:


We can ignore it, as it will work correctly with the whole script at the report execution. We also need to change the Data Format Column Properties:


We need to override Default Data Format in order to treat text as HTML:


Let’s make sure that report has the Static Text view added to the Compound Layout.


Now we can try out our development. The table with Orders should display the tooltip with navigation to target report with the Order details.


On hover, the order details from the target report are displayed in a tooltip:


The contents of the tooltip are displayed dynamically based on the navigation condition (in our case Order Number)

Maintenance and other considerations

We need to take into consideration that by embedding scripts to the OBIEE reports we are adding another layer of complexity.  This is especially true for the maintenance reasons as it requires more time and skills for the end users and developers to edit and create reports that contain scripts. Another concern should be that adding too many scripts to the report may negatively affect the performance of the report. We also need to take into consideration the web browsers used by users in the company. Some of the plugins and the latest versions of jQuery library are fully compatible only with the latest versions of browsers.


Thanks to the possibility of using many web technologies such as JavaScript we are able to customize OBIEE reports and dashboards. Tooltip can be a valuable tool to enhance the functionality of OBIEE reports, allowing users to get detailed information when hovering over a link.

Do you have another method to achieve the pop-up effect? Please leave us a comment below, we would be happy to answer it! If you would like to know more about visual enhancements in OBIEE, read our blog posts series about enhanced visualization:

Rich Visualizations in OBIEE with Javascript


Tableau – Salesforce Integration


In this blog post we will see how we can connect a Tableau workbook to our Salesforce environment in order to retrieve real time data from our hosted database. Note that this connector is going to work both for standard or custom cloud-based solutions using the platform.

The process steps to follow are:

  1. Select the Salesforce connector
  2. Enter the connection details
  3. Choose and define the connection type to extract data
    1. Standard
    2. Single Table
    3. Multiple Tables
  4. Name the connection

Let’s see the above steps in more detail.

1. Select the Salesforce connector

The connection to Salesforce is done using a data connector available in Tableau. So there is no need to install any third party tool or driver.

To select the Salesforce connector, from the initial Tableau screen, click on “Connect to data”.

01 - Initial screen - Connect to Data

Then, on the left pane, under “Connect” “On a server”, click on “Salesforce”.

02 - Connect - Salesforce

This will pop up the “Salesforce Connection” dialog.

2. Enter the connection details

In the “Salesforce Connection” dialog we need to fill in the connection details to our environment as follows:

  1. Username: Our username.
  2. Password: Our password concatenated to our security token*. For example, if your password is “1234567890” and your security token is “5XEBsSpC8LcnrDaTTqUnOcikc”, you should type in “12345678905XEBsSpC8LCnrDaTTqUnOcikc”.

*: In order to obtain your security token, from Salesforce you need to:

  1. Click on the “Setup” option in the drop down next to your username.
  2. Click on “Reset My Security Token” in the “Personal Setup” page, “My Personal Information” section.
  3. Click on the “Reset Security Token” button.


11 - Salesforce - Reset Token (Confirm)

When you have filled in the details, click on the “Connect” button.

03 - Salesforce connection - Connection Details_b

3. Choose and define the connection type to extract data

Once connected, you will need to choose how you want to extract the data from the database. The three available options are:

  1. Standard
  2. Single Table
  3. Multiple Tables

3.1. Standard

The standard connection type is used to simplify the connection to the data. It includes multiple predefined business areas with preconfigured joins. The main benefit of this connection type is that the user doesn’t need to know the data model supporting the data.

Tableau comes with the following standard connections:

  • Accounts
  • Campaigns
  • Cases
  • Contacts
  • Service Contracts
  • Opportunities
  • Opportunities and Contacts
  • Opportunity Items
  • Tasks
  • Leads

In order to select a standard connection, just select the Standard option in the Connection Type radio button and select a connection. For instance, “Contacts”.

04 - Standard Connections - Contacts

3.2. Single Table

The single table connection type is used to retrieve data from one single table from the database. This connection type does not allow to join tables so it brings simplicity and good performance on one side but also some limitations in terms of the data extracted.

In the example below, we are extracting data from the “Contact” table.

12 - Connection Type - Single Table

3.3. Multiple Tables

The multiple table connection type is used to retrieve data from multiple tables from the database. This connection type needs the joins between the selected tables to be defined. This prevents non-technical users from using this connection type. However, it provides flexibility to technical users to connect to the data.

In the example below, we are extracting data from the “Contact” and “User” tables, with the latter acting as the Contact Owner.

The first step is to select the initial table. In our example “Contact”. In order to do that, click on “Single Table”, select the table and then click on “Multiple Tables”. You will then see the following screen:


13 - Connection Type - Multiple Tables 1

Click on “Add Table”.

In the pop up dialog showing up, you will find the tables that can be joined to the selected table as per the joins defined in Salesforce.

Select “User”. Then click on the tab “Join”.

14 - Connection Type - Multiple Tables 2

You will then find the possible joins based on the different roles that the “User” table can have when joining to the “Contact” table.

15 - Connection Type - Multiple Tables 3

In our example, we will select the “CreatedById” and “LastModifiedById” join clauses and will click on the “Delete” button. This needs to be done individually for each join. The remaining join is defining the join between “Contact” and “User” acting as the contact owner.

16 - Connection Type - Multiple Tables 4

Click on the “OK” button.

Then you will see the “Contact” and “User” tables selected with the join condition used to join them based on the “Owned By” relationship.


17 - Connection Type - Multiple Tables 5

4.Name the connection

Finally, you just need to optionally modify the connection name to be shown in the Tableau workbook. Note that this name is filled in by default depending on the connection type and its content.

Then click on the “OK” button.

05 - Salesforce Standard Connection Contacts - Click on OK

After connecting to the cloud-based database, you will see the workbook workspace showing the content associated to the connection you defined.


Below you can find the results based on the three connections previously defined.

1. Standard

Dimension tables included in the “Contacts” standard connection:

  • Account
  • Account Created By
  • Account Owned By
  • Contacts
  • Created By
  • Owned By

06 - Workbook - Contacts Standard Objects



2. Single Table

Dimension tables included in the “Contacts” single table connection:

  • Contact

08 - Workbook - Single Table - Contact



3. Multiple Tables

Dimension tables included in the “Contacts +” multiple table connection:

  • Contact
  • User (Owned By)

09 - Workbook - Multiple Tables - Contacts + Users


Connecting to our environment is now a very simple task. Even non-technical users can define the connection to the data and start exploring it. On the other side, technical users will be able to define their own complex queries by joining non-standard tables in a customised environment. After you’ve done that, you will get the benefits of having real time data in Tableau, giving you the ability to do data discovery in this cloud-based environment.

Have you connected Salesforce to Tableau or any other BI tool? Leave us a comment and tell us about your experience with Salesforce and the benefits you had from connecting it to a BI system.

Tableau 8.2: New Features


Good news for all Tableau fans! The new release, version 8.2, is now available!

We have been selected to participate in the testing program of Tableau 8.2 Beta. Lucky you to be reading this article, as you will have the privilege to read about some of the new features being included in the new release.

In this article I’m introducing you some of the hottest functionalities in Tableau 8.2:

  1. Visual Connection to Databases
  2. Story Telling Object
  3. Updated Maps
  4. Tableau Server Improvements
  5. Tableau Desktop for Mac OS

Keep reading and get as excited as I was when going through them for the first time. It’s worth spending 5’ reading this article. You will not regret that.

1. Visual Connection to Databases

This new feature will greatly simplify how we are currently building data extract queries. It’s a completely redesigned data connectivity view that allows the designer to build different types of joins (inner, left, right, full outer) between tables in a visual and very intuitive way.

The steps to follow are:

  1. Select the data source: Nothing has changed here. You must select the data source type and then fill in the appropriate details to connect to the selected data source.
  2. Select the tables: Drag and drop the selected table into the canvas on the right.
  3. Set the joins: Click on the joins and set the join type as well as the matching columns.
  4. Verify if the joins are correct in the Preview: Check the query results to validate the joins.
  5. Click on “Go to Worksheet” to start working on the new analysis: Once you have done all the above, click on this button to start designing your analysis.

Note that you will be able to choose the connection type. The options are:

  • Live: Queries will be done to the data source to retrieve the data.
  • Extract: Queries will be done to an extract of the data instead of the real data source.


Below you can find two screenshots so that you can compare this functionality between Tableau 8.1 and 8.2:



Data connection version 8.1                                            Data connection version 8.2

Having said this, news in data connection do not finish here. There are improvements in the following connections sources too:

  • Microsoft Excel and Text files: Improved detection of field types, larger amount of columns, Time type seconds recognition, percentages as number recognition…
  • SAP HANA: Variables and input parameters.
  • OAuth: Support for, Google Analytics and Google BigQuery
  • Google BigQuery: Native support provided
  • Splunk: Improved connection.


2.Story Telling object

Story Telling provides the user a brand new experience in data analysis as it guides the user through different analysis following a predefined path.

The predefined path is defined by the Story Points, a sequence of steps that the user can walk through as he or she explores the data. However the user is not forced to go through every single step to get to the analysis he or she is most interested in. The user can jump into that step without the need of visualising the previous ones.

Each Story Point or step in the Story Telling is showing the user an analysis or even an entire dashboard.

Proceed to the following steps in order to create a Story with Story Telling:

  • Create a new Story

Add a new Story by clicking on “Story” > “New Story” in the Menu bar.


You can also create a new Story by right clicking on the Analysis/Dashboards/Stories tabs and selecting “New Story”.


  • Embed sheets and dashboards into Story boards

The sheets and dashboards are displayed as on the left pane of the board as in the previous versions of Tableau. To insert them into the Story, just drag & drop them into the right pane.


  • Add annotations

The analysis won’t lose neither the annotations, highlights nor filter capabilities once embedded in the Story board. On top of that, we have additional description capabilities to add to the Story board to emphasize important findings.


  • Print the stories in PDF

Click on “File” > “Print as PDF” and you will save the Story Telling object as PDF showing each step in a separate page of the PDF document.

  • Show in full screen

Click on “Window” > “Presentation Mode” or press F7 to show the Story Telling object in full screen as it can be done with dashboards.


3. Updated Maps

Tableau is improving the visualization in maps, one of the most powerful capabilities of the product.

The data content used to create the maps is including the latest set of data from OpenStreetMap. This engine allows you to zoom down into 16-steps of zoom, WORLWIDE!

You can check the visual impact of such changes by comparing the screenshots below:



Maps version 8.1                                                                          Maps version 8.2

tableau10 tableau11

Maps version 8.1 with 3 levels of zoom                                      Maps version 8.2 with 3 levels of zoom

4.Tableau Server improvements

There are many improvements on the server side, mainly focused in simplifying the server administration. Some of these improvements are:

  • Easier Log Access
  • New Log Format
  • Change Content Ownership
  • Provision Sites with Site Export/Import
  • Server APIs for Administrators
  • Responsive Marks
  • Cross-version compatibility
  • Disable Web Authoring per Site
  • Support for Multiple IP Addresses

5. Tableau Desktop for Mac OS

The user base of Tableau is made of a heterogeneous group of people. And guess what? Some of them are using Mac OS based computers!!

From version 8.2 they will be able to analyse and discover data using Tableau directly from their preferred platform: Mac OS. The old days of having another computer or even a virtual machine running Windows to be able to work with Tableau Desktop are gone.

Here are the highlights of this improvement:

  • All the Tableau products (Reader, Public and Desktop) will all be available for Mac OS.
  • The Mac OS version will support high resolution Retina displays and will use the same files (TWB, TWBX, TDE, and TDS) that are supported on the Windows version of Tableau Desktop.
  • The Tableau users could use the same license for the Tableau Desktop on Windows and Mac. According to Tableau, the installation on Mac OS will be plug and play: Install Tableau Desktop on your Mac and activate it with your existing license.

From the Mac OS lovers I can only expect to hear a word… “FINALLY!“



As you can see, most of the new features improve visualization, something that identifies Tableau as a data discovery tool. Remember that this post is based on Tableau 8.2 Beta version 4, so it’s sensible to changes until the final version is released.

I hope this blog has helped you to get a better idea of how the new version looks like and how useful it will be in your future data discovery and analysis. What are your favorite features of Tableau? Do you think the new options bring value to your Tableau visualizations? Tell us your opinion in a comment below this blog post!

For more information, feel free to contact us at:

Oracle Discoverer De-Support: how do you visualise your future BI and reporting?


If you are still using Oracle Discoverer for some or all of your reporting and BI requirements, you are probably struggling to deliver on user demands for better mobile/tablet access and richer information visualisation to improve interpretation, understanding and informed decision-making.

Also, it’s not new news that Oracle Discoverer is on its way out.  It ceased to be Oracle’s strategic BI toolset as long ago as 2006, when OBIEE came to the fore as Oracle’s new flagship BI platform.  Premier Support ceases in June 2014, and Oracle recommends all customers to migrate away from Discoverer by June 2015.

Many customers invested considerably in Discoverer prior to the release of OBIEE, and through challenging economic times have sweated the asset rather than undertake the transition to a more state-of-the-art platform.

Now that Discoverer is moving into its final stages of life, it is time to revisit the strategy for current Discoverer customers.

Why should I be migrating away from Discoverer?

From a business viewpoint, you are already well behind the curve in terms of the BI capability offered to you by Discoverer – and that could easily mean that you are falling behind your competitors who have gained the edge of working with newer, more able technology.

The releases of Discoverer around 2006, including Discoverer for OLAP, were actually pretty good at the time and brought it to a comparable level with other products of the day.  But just look around at what else has changed since then in the IT world – mobile devices, social media, advanced visualisation, big data – so that today, even if Discoverer is doing what it says on the tin, it is not equipped to move forward in any way.  Many end-user capabilities that are considered “must have” today are just not possible with Discoverer; indeed, even in its heyday, whilst Discoverer was a good workhorse, it never did score particularly good ratings for usability.

The last “features” release of Discoverer was 11gR1 in June 2009, and the terminal release of bug fixes and minor features was  According to Oracle’s latest Statement of Direction (March 2014), there will be no further releases.  Premier Support ceases in June 2014, and Oracle recommends all customers to migrate away from Discoverer by June 2015.

A common objection from some customers is that they have a large estate of Discoverer reports and it would be far too major, complex and costly a task to replace them all.  Some customers have many hundreds of Discoverer reports, so at first glance it may indeed look like a huge task and not worth the cost.

However, a closer look may reveal that:

  • Actually, a large percentage of the “hundreds of reports” is redundant now – many of them are old versions or multiple temporary re-hashes of the same report.  So it may be that only tens of reports are still fit for active purpose.
  • Many of the reports are being used solely as a staging post to extract data to Excel for wrestling into shape for the final output – this is clearly an inefficient, error-prone and costly (in human time) process
  • There is a now cottage-industry of Excel (or other tools) producing newer report requirements that were not built into the Discoverer suite because it was not meeting the business need.  Again this could be costly, slow and error-prone.  Maybe the IT department thinks that Discoverer is still delivering what is required, but the business has moved on and may even have purchased other BI tools
  • Every time the underlying systems are upgraded, the whole Discoverer suite has to be re-tested and modified – Discoverer does not have the same metadata capabilities as OBIEE.  Many customers implemented Discoverer direct against transactional systems or eBusiness Suite without a data warehouse, meaning that every change to an underlying database could mean major rewrites of the Discoverer reporting suite.  The cost of a few iterations of this could outweigh the cost of replacement.

What do the changes to available Support mean?

When Premier Support ends (June 2014), the main change is that Certification with most new third party products/versions and new Oracle products ceases.  You can choose to keep the rest of the available Support features by paying an additional fee for Extended Support (free to June 2015).

If you choose not to opt for Extended Support, or in any case from June 2017, then you are on Sustaining Support.  This provides updates, fixes, security alerts, critical patch updates and upgrade tools/scripts for pre-existing issues only – not for anything new that occurs.  Also, there is no further certification against other Oracle or third-party products.  Basically you could maintain the software as-is, but if you were to change any of your source systems, database versions, etc, then you would be running the risk that if it broke, you would have no Support redress.

You are maybe planning on moving forward in other areas – e.g. an R12 Upgrade to eBusiness Suite, or migrating your database to 12c.  If you have any such major changes planned, it makes even more sense to reconsider whether Discoverer remains fit for purpose or whether it is now time to look at its replacement.  If you plan to move to the Fusion edition of eBusiness Suite, BI Foundation Suite becomes a pre-requisite.

Oracle specifically recommends that you should migrate by June 2015.

What should I replace it with?

Conventional wisdom, and Oracle recommendation, says:

  • Migrate the licenses to Oracle BI Foundation Suite or OBIEE.  There may be a partial rebate on the costs if you have a current Support contract, but this depends on versions and needs to be checked with your Oracle Account Manager (ClearPeaks can facilitate and advise on this)
  • For each Discoverer report, consider whether it is more appropriate to replace with Answers (the OBIEE analytic tool) or BI Publisher (the OBIEE tool for more structured reporting)
  • If you are an eBusiness Suite customer with packaged Discoverer content, replace with Oracle BI Applications

However, there are further considerations in making your decisions:

  • If you run direct against source databases – e.g. eBusiness Suite – would you benefit from changing to a datamart/warehouse approach to both future-proof your reporting and open up your data for analysis by making it available in a more digestible form for business users?
  • If your Discoverer “reports” are in reality being used for data extraction to another BI toolset, should you replace this manually intensive process with a proper ETL tool such as Oracle Data Integrator?
  • If your user base is small, could you migrate to the less costly BI Standard Edition One? (there are restrictions on this product so you would need advice)
  • If the business users have already moved on and adopted – in part – an alternative BI tool, does it make sense to enhance it to an Enterprise approach and incorporate the Discoverer content into the chosen BI toolset?
  • Would the use of a discovery-based BI tool fit your requirements better, or complement your more structured reporting?

ClearPeaks specialises not only in OBIEE/Foundation Suite, Oracle BI Applications and Endeca, but also in leading third-party BI products, so we are well-placed to provide advice on your best approach.

How should I go about it?

It makes sense to consult the expertise of a specialist BI implementer since, having waited this long before migrating, you will want to get it right!

ClearPeaks can help you to review your current estate of Discoverer reports with a thorough Health-Check and analysis of usage, together with capturing some of today’s aspirational requirements of the business rather than necessarily just doing a like-for-like replacement.  We can assist with licensing considerations, reviewing alternative replacement strategies, and making sure that you get the best fit at the most acceptable cost, with a solution that will hopefully live for as long as your Discoverer solution did!

We can help you to plan the migration, train appropriate IT staff / power users in the new technologies, run and test the migration scripts if appropriate (although in many cases it is more effective to use the old report as a design template and rebuild from scratch), and generally assist you through the implementation.  Or if you prefer –and are all busy with the day-job – we can take the problem away and build your new solution on one of our servers then commission it when ready to switch over.

Just give us a call and we will be delighted to help assess what is right for you!

privacy policy - Copyright © 2000-2010 ClearPeaks