Data Extraction

2 Posts tagged with the updates tag

As you all know, we continue to refine the features and functionality of our web services during this beta rollout based on your suggestions and comments.  We also learn a great deal at our Developer Day events.  They have proven to be a fantastic event for attendees, and a great win for us as well as we learn very quickly what additional functionality will help our larger community develop more powerful apps.

 

Last week we rolled out a few updates that we wanted to make sure you were aware of:

  1. Calculated measures will no longer display in report definitions. Currently, these are only available through the Analytics user interface.
  2. The report "category" has been added to the "list reports for profile" method. 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.  This feature request came from one of our fantastic partners who was looking for an easy way to find the reports that were relevant to their implementation.  Good idea!
  3. 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.
  4. The ability to filter based of a discrete set of measure identifiers was not working. This was a bug and has been resolved.
  5. The "profile summary" report, when returned in Excel format, contained invalid XML what was preventing it from rendering properly. This has been resolved.
Again, many thanks for your feedback.  Keep it coming!
0 Comments Permalink

Our development team has been busy over the past few weeks updating the beta versions of our web services and Generator application.  We have received some excellent feedback from everyone (thank you!), and wanted to let you about updates we made this past Wednesday evening, May 6.

 

Please note these changes as they modify some of the core request and response formats.

 

Changes include:

  1. XML and JSON response format changes. We received feedback that it would be easier to consume some response data if it were formatted differently, so we made some adjustments to those responses.
  2. URL naming conventions.  We wanted to standardize on plurals in the URLs when requesting data.  For example, we've changed "/profile/" to "/profiles/" and "/report/" to "/reports/".
  3. New response codes have been added to make error conditions more obvious.
  4. Report "Category" has been added to the meta data for reports.  This is useful for selecting specific reports inside a profile that have been categorized for specific uses.
  5. Various bug fixes.

 

We also updated our documentation as well so you'll have the information you need.

 

Please keep the feedback coming in.  As you can see, we're listening...and iterating quickly to make this an outstanding service offering for everyone.  Thanks for your help.

0 Comments Permalink