Forum Discussion
Hi SuzieH ,
Thanks for the answer. There are few missing information and typos in the document that makes me question the integrity of the data I'm pulling via API.
For an example, I think "Viewing Accepted Solutions Metrics" have the (Node) and (User) notation switched. This is based on the metric values I was getting back, as well as metric names under the description.
Another issue I ran into was with net_comments_per_idea. The description says that the value is calculated by dividing Net Ideas Comments (net_idea_comments) by Net Ideas (net_idea_threads), but the value seems way off. Here is an example:
My api call for Net Ideas Comments is .../restapi/vc/metrics/name/net_idea_comments/history/daily?date_start=2014-06-12T00:00:00&date_end=2014-06-12T23:59:59&xslt=json.xsl&restapi.session_key=...
This returns a two digit value.
My api call for Net Ideas is .../restapi/vc/metrics/name/net_idea_threads/history/daily?date_start=2014-06-12T00:00:00&date_end=2014-06-12T23:59:59&xslt=json.xsl&restapi.session_key=...
This also returns a two digit value.
When I finally call for Net Comments per Idea using
.../restapi/vc/metrics/name/net_comments_per_idea/history/daily?date_start=2014-06-12T00:00:00&date_end=2014-06-12T23:59:59&xslt=json.xsl&restapi.session_key=...
I get a three digit (sometimes four digit) number.
I'm just having trouble trusting some of these data due to problems like these. Could you provide an insight?
Thanks so much in advance!
Are you still experiencing the net comments per idea bug? If so can you file a support ticket with output files so we can try to reproduce what you experienced? Thanks