-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typeahead from ExtensibleForm not Filling With Patched Value #22375
Comments
Hi, are there any recent developments or updates regarding this issue? |
Hello, If you are using a Typeahead-typed field in your form, you also need to add another field with the same name but with the suffix _Text to store the selected key from the Typeahead field. This field is automatically populated when the Typeahead selection changes. Here’s an example usage: {
type: ePropType.Typeahead,
name: 'state',
displayName: '::State',
id: 'state',
options: data => {
return of([
{
key: 'Active',
value: 'active',
},
{
key: 'Passive',
value: 'passive',
},
]);
},
},
{
type: ePropType.String,
name: 'state_Text',
displayName: '::State',
id: 'state_Text',
visible: data => false, // Hidden field to store the selected key
} |
Thanks for the tip. Is this a work-around or a definitive solution? Can it be used right away or will it only be available in a future patch? I tested it on my project and it still didn't work |
Hello, |
Hello, Again, thanks for the help provided
Request payload:
Response:
|
Hello The issue is that your response does not include the Could you please add the |
While the solution functions, it appears to introduce unnecessary complexity compared to the streamlined behavior of the abp-lookup-typeahead component. Optimizing this implementation to achieve similar efficiency and simplicity is desirable |
Description
Typeahead input in abp-extensible-form is not updating properly when a patched value is applied through patchValue() or form initialization.
Reproduction Steps
Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: