I don’t see any issues in this HTML.
But I don’t understand where the inclusion and name bindings are coming from? Is this inside a repeat?
Also, what do you mean by binding is not working? Lastly, just for debugging purposes, did you try to create a simple autocomplete without any of tye custom bindings?
Yes, this is inside of a repeat and dmx-bind:id is working for others fields (input, radio, check, dropdown) but not for autocomplete.
I created a new page, a variable with a random value (abc) and an autocomplete field, with dmx-bind:id="{{variable.value}}". When inspecting the element, the autocomplete id is id={{variable.value}} not id=abc.
If you remove “is=autocomplete”, the dmx-bind:id works!
Finally got around to testing this on my machine too. It does look like the dmx-bind bindings are not getting resolved for autocomplete input field. Something for the team to check.
In this app, all the fields are dynamic, the user creates rules and the app show the fields accordingly to the user rules, I need the identify each field with different IDs in order to show or hide fields via javascript. Autocomplete field is one of these fields.
@Teodor! I answered you! Check the above messages!
Well if you need to use it inside the same repeat scope, then you can use the static ID there like autocomplete1.value
It did not work for my use case. There are many controls based on the user's rules, for the autocomplete, for example, I'm using it as a "tag and search"...user search a value and the result selected I stored inside of an array and then show the selected values as tags/buttons. When the user press "save", I need to validate the presence of values for required fields and I'm doing it via javascript (fields are required only if the admin user select the field as required), I would like to have the dmx-bind ID for the autocomplete only to display a red border in case of not having a value in a required field. I tried to use Wappler validation, but having the "required" dynamic, didn't found a "Wappler way" to accomplish it.
I found a workaround but would be nice to have this or even a "required" validation with conditions.
I don’t really understand what exactly are you trying to achieve. As I explained if you need to use its value in the same repeat scope dynamic id is not needed.
Currently it’s not possible to have dynamic attributes for the autocomplete. And I don’t have a timeframe for when will this be possible.