Currently Being Moderated

Known API Issues & Release Notes

Posted by Rob Derstadt on Mar 11, 2009 12:32:57 PM

We will keep this blog post updated with the latest known issues for our DX API. Please check here first, before submitting a bug to Webtrends if you are having problem.

 

 

The beta API was last updated on May 21st, 2009. Enhancements include:

 

  • Calculated measures will no longer display in report definitions. Currently, these are only available through the Analytics user interface.
  • The report "category" has been added to the report listing. This will make it easier to obtain a list of reports matching a specific report "category". If a report has no defined category the attribute will not be displayed.
  • In some cases a report was enabled for trending, but the report meta-data did not accurately reflect this. There was a bug in the logic that determined if trending was enabled. This has been resolved.
  • The ability to filter based of a discrete set of measure identifiers was not working. This was a bug and has been resolved.
  • The profile summary report, when returned in Excel format, contained invalid XML what was preventing it from rendering properly. This has been resolved.

 

Beta API Known Issues

 

  • Totals will not be displayed in report data. Client applications can easily aggregate their own data or compute new measures (i.e. a "calculated measure").
  • Dimension attributes for multi-dimensional reports are not currently supported.These will be added in a future release.
  • Some dimension "names" do not match those shown in the UI. This is a translation problem and will also be addressed in a future release.
  • Smart Measures, if available, will show up in report definitions. However, the actual measures displayed is dependent upon the time period specified when performaing a query. If you are requesting specific measures you need to be sure to include the correct smart measure for the time period desired. For example, if you are specifying a daily time period (e.g. 2008m02d24) then you should only specify the smart measure that applies to a daily time period. If not, an error will result.
  • Trending performance is "slow". In some cases it may be possible to improve trending by performing individual requests and calculating the trend on the client.