Hi colleagues,
I have a challenge with OOB Autocomplete control. The one you can assign view and provide field for filtering.
The task:
To migrate legacy form design (9.1, before deprecation "addOnClick" event) in Dynamics CE 9.1 to UCI I need to maintain a hierarchy of autocomplete fields.
Client sets "low code" as a requirement and writing of PCF controls of my own is not an option for now.
The issue:
To keep it going with OOB I tried to insert with regular "setValue" which did work. No errors though.
Javascript (getValue) shows the value is actually there. But never displayed.
My own investigation failed.
The issue seems not documented or I could not find it.
Is there some one who've been through such scenario?
Thanks in advance
HI @mkalinov ,
So you would like to use this OOB Control, right?
I made some tests, and it seems to work only sometimes. Pretty hard to find when it does work: the combination that I've found out: when the autocomplete was opened once, and the focus is changed outside the control. In that case you can set the "setValue" and it is reflected in the UI, Otherwise it happens exactly as you say: when you use getValue() you see what you just set by using setValue(), but the value is not shown in the UI, and the form is not dirty.
Even worse, after an (auto)save, the control is like "new", doesn't know the options anymore and the game starts again.
Unfortunately I can only confirm that it doesn't work for me; I cannot come up with a better solution than writing an own PCF.
I hope somebody else have a better solution for you...
An own PCF wouldn't have the same customizing experience: the OOB seems to be a combination of both field and dataset PCF. I would like when the custom PCFs would be able to do that too.
Kind regards,
Diana
WarrenBelz
109
Most Valuable Professional
Michael E. Gernaey
82
Super User 2025 Season 1
mmbr1606
71
Super User 2025 Season 1