Timeframe for EXCEL exporting?

Posted by: cynthia-dd on 3 August 2017, 3:53 pm EST

  • Posted 3 August 2017, 3:53 pm EST

    I need to know if there is an estimated timeframe for this.

  • Replied 3 August 2017, 3:53 pm EST


    Right now there is no fixed timeframe available as to when the issue will be fixed. I have attached your email address to this case as the affected user and you will be notified when the issue gets fixed.



  • Replied 3 August 2017, 3:53 pm EST

    I would rather not explain myself as I will only get more frustrated because no one knows if Excel integration will even occur.

    Im looking at requests for this back to 2007. Im frothing at the month because DDA is so close but so far away. What are you all thinking by taking this product to this point and then droppoing the ball with Excel.

    You have some bright guys out there but if you can't figure out how to interactively integrate and leverage with Excel and make it a priority then Im just going to shelve this thing until i receive an email on the case # update.

    If you want a product requirements session send me an email I would be happy to visit you in Seattle and give you an earful.

    Also GauravC instead of answering the majority of the requests with "no we currently dont have it and here is a case number", maybe you should have a product suggestion forum. There you can keep a list of requested enancements, along with the case #, so people dont keep manking the same request. I suppose asking for a timeline and priortization is just a bit too much at this point.
  • Replied 3 August 2017, 3:53 pm EST


    First, let me explain our internal thought process on what we've been doing with regard to Excel exporting.

    Back in January we identified Silverlight/WPF, Excel export, PDF export, and some other items as the features for us to accomplish over the coming year.

    We began planning what features the Excel and PDF exports would have in them and looked into how we could implement them.  Something that was readily obvious is that we already have a document format that can export to Excel and PDF (amongst other formats) built into ActiveReports.  With this, we began implementing a different export, an RDF export that could be used in conjunction with ActiveReports to export the document to any of the formats it supports.

    While we were working on this export it became obvious that there were some major graphical features that we relied on in DDA that were not present in RDF.  With the ActiveReports team working on version 6.0 of that product we hoped that we would be able to sneak these new canvas items into the format so that we could continue with the RDF export at a later time.

    In the mean time we did two things, 1) implement a CSV export which would give you all of the data you needed in Excel minus the formatting, 2) began working on a Silverlight control (a massive undertaking as it requires rewriting the entire UI and graphing code).

    Our assumption was that the CSV export would provide the basic functionality of the Excel export without the added complexity while we worked on the Silverlight control.

    So where do we go from here?  The team is finishing up the Silverlight control now, and the good news is that we just laid out our plans for the next 6 months.  At this point we am abandoning the idea of going through RDF for the Excel export and we'll just offer Excel as its own export (same with PDF).  We'll likely bring up RDF again so that pivot views can be embedded within an ActiveReports report but it is not currently in our 6 month plan.


    James Johnson
    DDA Product Manager
  • Replied 3 August 2017, 3:53 pm EST

    OLAP type analytics has a far different usage than relational type reporting performed by your other products. DDA should fit into a stream of thought not just be an end point. Im not sure your product strategy team understands the usages scenarios that offer the widest deployment and acceptance. The web is just one of many distribution channels for data. Dont forget about the millions that use Excel on the desktop every day that could benefit from a better pivot table and add dashboard capabilities.

    Thank you for the above response. However the bottom line remains, Excel integration (still not sure what you have in mind) is not to be delivered in a window that encourages me to invest more time. DDA is on my shelf and my team will reevaluate whether it is worth working on once we have a definitive product timeline and integration feature plan.
  • Replied 3 August 2017, 3:53 pm EST

    I suppose even bring up integration with FarPoint, now that GC owns it, would be just too much.........
  • Replied 3 August 2017, 3:53 pm EST

    I second the motion on requesting an export to excel.  Im a BI industry analyst and this seems to be univerally requested from the user base we poll.  Just exporting to Excel is a start.  Once it is in Excel it will likely be reformated preventing any dynamic updates.  Everytime a user wants to refresh the data then they wlll have to go through the same format exercise again.  To go one step further, it would be a quantum leap forward to be able to pass the shelf information (page, column, row) to another application.  Forgive my lack of technical skills but this would be tanamount to the select, from where sql statement.  The objective would be to have a rich integration to the purpose build Excel reporting tools commonly used for budgeting, forecasting, and statistical analysis. 


  • Replied 3 August 2017, 3:53 pm EST


    Thanks for your suggestion. I have attached your email address to the Case 62147 as the affected user . However I am not able to completely understand your second requirement. Are you looking for some end user designer capability through which an end user can modify report layout before exporting to excel or is there anything else you are looking for.

    Can you please explain me in detail your requirements so that I may assist you further.



  • Replied 3 August 2017, 3:53 pm EST

    We cannot add a dependency on Spread into Analysis as they will be offered as separate products.  However, we do plan on offering some form of integration in the future.  We will begin by offering Excel export support in Analysis which Spread can read in.

    This may be augmented with additional forms of exports in the future, however because of the issues with the way assemblies are loaded any compiled code we ship would be tied to the specific version of Spread we compile against.  For this reason we may need to offer such exports as sample code that can be integrated into your own application where it would be independent of the version of Analysis and Spread being used in your own application.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels