Maps Extended error - can't find ID field from API even when using Lat / Long

I’m getting this error when trying to use Lat / long info to load markers into Maps Extended. It worked ok using a merged Lat/long as a geographic address, but then it processed them as “nearest known addresses” and the markers were not at the correct points. Switching back to Lat/Long I get this ID error even though I am not telling it use the ID field.

Going mad here! How can I fix this? Or how else can I get a map to show a list of markers at their exact Lat / Long locations rather than the nearest known address

Thanks!

“The plugin Google Maps Extended / action Add Markers List a Maps Extended threw the following error: Error: This fieldName does not exist: _id
at Object.get (https://samueldavies101.bubbleapps.io/package/run_debug_js/455c413856a65492f27ee84f4bb39cd790330095f6365d3cd895a664db494f94/xfalse/x31/run_debug.js:721:2478)
at eval (PLUGIN_1479901297703x967536405834891300/Google-Maps-Extended-element_action–Maps-Extended-Add-Markers-List-.js:3:3482) (please report this to the plugin author)”

The error is happening because Maps Extended expects the ID field to contain a unique identifier for each marker, but it seems like the field path is not matching what the plugin expects.

Since you are pulling data from Airtable, the issue is likely that the ID field path needs to be the actual Airtable record ID, not just the Name field. Airtable records have a unique ID that usually looks like “rec…” format.

Here are a few things to try:

  1. Check if your Airtable API response includes a record ID field (usually called “id” at the root level of each record). Use that instead of “fields Name”.

  2. If your Airtable connector returns the ID as part of the response, try setting the ID Field to just “id” without the “fields” prefix.

  3. As a workaround, you can also try creating a unique identifier by combining Latitude and Longitude values formatted as text (like Latitude:formatted as text + “-” + Longitude:formatted as text).

  4. Make sure that whatever field you use for ID Field actually exists in your data and has a unique value for each record.

The error specifically says “_id” which suggests the plugin is looking for a field with that exact name. Check the raw API response in your Bubble debugger to see the actual field names being returned from Airtable.