Hey @PaulK ,
While this is valuable, we have some significantly more pressing bugs to deal with right now. I’m keeping this in my awareness, but can’t bring up the priority in the immediate.
Hi, @PaulK and @ACWadmin1 !
Ok, I think that I’ve deployed a fix to this that allows for successful download of the occurrence search results.
When I initially inspected the spreadsheet, I thought that it didn’t contain anything, but I scrolled waaaay down and found the correct number of rows full of content.
Are you experiencing the same (spreadsheet download success, followed by weird but technically workable entries in the spreadsheet)?
Is this an ok workaround for now, if I make a (low-priority) ticket to fix the spreadsheet wonkiness?
Many thanks to both of for your patience with this one!
-Mark
Hi, Paul!
I apologize for the later-than-usual follow up here.
So, in the file that you sent me, there IS one result at the very, very bottom of that spreadsheet.
I was able to confirm that searching for “GB300” in the occurrenceID field for sightings search should only yield one result.
I also set this up on my test environment, and the single exported result was at the TOP of my spreadsheet. So. Weird.
But hopefully at least useable in your case.
I was also able to fix the bug for the GTM export download not working in my test environment. I’ll deploy that fix onto ACW as soon as it passes code review.
@ORP-StephanieK , I will deploy those bug fixes onto IoT as soon as possible as well in the optimistic case that IoT has the same bug as ACW.
