Changes to export

Product Feedback
, ,
1

Hi Folks,

This week I exported the xlsx from our weekly event and noticed that the columns had changed. Specifically, the “entry_number” column, which our weekly league had come to depend on, is missing.

If this is a bug, could you please let us know when it may be addressed? I’ve added bug report info at the end.

If not, would you please, (pretty please) notify folks of changes like this ahead of time?

If it was announced and I missed it, please point me to that communication channel and I will be more diligent in the future.

Context: In the absence of a public API, many of us have designed systems for ingesting the export data from xlsx files for scoring and other purposes. Our league had come to depend on the entry_number values as a workaround for the last time things changed suddenly.

I hate to be a pain in the ass and don’t want to take away from all the amazing things that uDisc does, but this kind of stuff is super frustrating and easy to avoid/mitigate. Please consider a more robust release process.

Thanks for your consideration. Hope to hear from you soon.

Steps to repro:

  • visit the event page in a web browser. Example.
  • click the “Export” button to download an xlsx

Expected results:

  • The columns exported are the same as previous weeks (i.e. include a col for “entry_number”):
    division position position_raw name event_relative_score event_total_score entry_number pdga_number username round_relative_score round_total_score hole_1

Observed:

  • The columns in the export are:
    division position position_raw name event_relative_score event_total_score pdga_number username round_relative_score round_total_score hole_1…
2

This isn’t a bug or a new change/release.

The export only includes the entry_number field when there are multiple entries. In the case of the event you linked, no one has entered multiple times (so everyone’s entry_number is 1). We only conditionally include this field because not all events use multiple entries, so this field would be irrelevant/confusing for any event that uses single entry.

Instead of looking at whether any player has entered multiple times, we could perhaps look instead at the configuration of the event which would solve for both of these concerns. In any case for now, you may safely assume that when entry_number is missing, it is the first/only entry.

1 Like
3

Excellent. Thank you sir!