Next suggested new ID: missing

In which Wildbook did the issue occur? SeadragonSearch

What operating system were you using? (eg. MacOS 10.15.3) El Capitan 10.11.6

What web browser were you using? (eg. Chrome 79) Version 87.0.4280.88

What is your role on the site? (admin, researcher, etc) admin

What happened? The neat little ‘suggested next ID’ is not working for location Sandtracks

What did you expect to happen? A number to be suggested.

What are some steps we could take to reproduce the issue?

If this is a bulk import report, send the spreadsheet to with the email subject line matching your bug report

Also not working for WA-Point Peron as well as WA-Sandtracks

Also not working for WA-Augusta

Hey @NeridaWilson,
We need to update a properties file to include those locationIDs. We’ll get that done shortly, tracking under WB-1284.

1 Like

Also not working for the NSW locations recently added to the dropdown menu @tanyastere!

@NeridaWilson @ChrissyTustison

These should be implemented.


1 Like

Thanks jason, I can confirm that it is working for Sandtracks, but not for Augusta. I cant test Point Peron yet, cheers, nerida

Hi Nerida,

I forgot to account for the spaces in the names in the mapping file. This should be fixed now.


Thnaks Jason, all good on this end, thanks!

Hi Jason, these WA sites also not working. Canal Rocks, North Mole, North Beach, thanks! Nerida

Tracking this under WB-1436

Hi Tanya, a related but probably different ticket number job…we recently ticked over 1000 for WA. Hooray. So now our next suggested gives a code of WA-0xxxx, when it should just stay at 4 digits like WA-1xxx. Are we able to fix that? thank you!