Conflict with Craft forms.autosuggestField

[spib]

Description

If there is another field on an entry which is using the built-in Craft forms.autosuggestField macro, the auto suggest field in the non-simplemaps module works, but does not show the stored value (appears blank by default). I first noticed it in the SEOMatic plugin, but I think it would apply to any field type using the craft autosuggestField. Here's the GH Issue where I first raised this in SEOMatic

https://github.com/nystudio107/craft-seomatic/issues/822

After spending a lot of time with the developer of that plugin, and some further testing of my own I narrowed it down to being caused by SimpleMap.

Steps to reproduce

1. Add A SimpleMap field on an entry that already has another field type using a Craft built-in forms.autosuggestField (such as SEOMatic)
2. The forms.autosuggestField field in the other module functions but does not display the previously stored value.
3. Removing the Simplemap field from the Entry Type field layout fixes the issue

Additional info

• Craft version: 3.5.14
• Maps version:
• PHP version: 7.4.14
• Database driver & version: Mysql
• Other Plugins: SEOMatic 3.3.30

[alexjcollins]

@spib Thanks for flagging and for all the info. We'll try and get a fix in for this next week.

[spib]

@alexjcollins Thanks, just checking in to see if you'd had a chance to look at this or if you need anything from me?