nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Anyone else see "Discussion NAME" turn into "Discussion ID" in export?

Genevieve P

Hiya,

I went to Export a custom chart I had created that uses the Discussion Name and the creator ID to track enhancement requests (Ideas). Normally the CSV file has the name as static text in the exported CSV file.

However today I noticed the export changes the Name to the Discussion ID:

This behaviour has changed, but I don't know when it started happening. I do know there have been a number of updates to Analytics so just checking if I missed an update.

Note: this is what my previous export had looked like, I believe about 2 months ago:

Anyone else seeing the same thing, or am I missing a setting in the chart to ensure the Name is pulled through in the export?

Thanks!
Genevieve

Find more posts tagged with

Analytics

Analytics & Reporting

Accepted answers

All comments

MSE_James

Yes there has been a bug for several weeks in Analytics which means discussion IDs are showing up in place of titles. You can see this in the default traffic dashboard for instance.

I have an open support ticket regarding this issue.

Genevieve P

Thanks!

Genevieve P

@MSE_James Do you have any update from your open ticket?

I don't see it on the Known Issues tracker.

https://success.vanillaforums.com/discussion/1834/known-issues-initiative-launched

Branwyn T

@Genevieve P A ticket has to have a certain critical mass to make it into the Known Issues. I'll see what I can do to get it added.

John

I will be adding this to the Known Issues tracker since we're getting some additional reports. Thanks for mentioning this, @Genevieve P!

MSE_James

The last update I received was nearly 4 weeks ago:

"We appreciate your patience as this works through our escalation process. This is currently in our developers queue. We ensure that fixes are ran through QA once complete. I have notified our developer and product team lead regarding this issue to get more eyes."

I am surprised that this issue has been allowed to persist for so long, especially as it is visible in the default analytics dashboard.

The issue was reported two months ago.

Val

I can provide some context here. We made some changes to our UI a while back that resulted in the changes you've noticed in the CSV exports. We had gotten reports that counts were off, and this was due to the fact that when you query on Discussion Name and you have discussions where the name has changed, the counts will be split between the two different names. To remedy this, we updated our charts grouping data by Discussion Name, to run the query using the Discussion ID in the background so that you have one unique entry per post. This unfortunately does result in the Discussion ID being pulled in the CSV export. That being said, we are gearing to start a new Analytics project to add more details into the CSV exports so you can clearly see each event that is logged in your chart and all the details associated with them including both discussion name, discussion ID and much more. That way we can address the concerns reported here as well as the rest of the feedback we've received about these exports. Thank you for your patience. I assure you it will be worth the wait.