Refine•4d ago

Antd useTable warning

When using Antd useTable(), I got an error "installHook.js:1 Warning: Instance created by

useForm

useForm

is not connected to any Form element. Forget to pass

form

form

prop?". This seems coming from line 130 of useTable file "const registeredFields = formSF.form.getFieldsValue() as Record<
string,
any
>;"

How to fix this error ?

kapa.ai•12/10/25, 11:30 AM

Hi @quick691. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base.

kapa.ai•12/10/25, 11:31 AM

----------------------
This warning appears when an Ant Design instance created by

useForm

useForm

is not actually attached to any

<Form>

<Form>

element. Ant Design then logs:

Warning: Instance created by
useForm
useForm
is not connected to any Form element. Forget to pass
form
form
prop?

In refine’s Ant Design integration, exposes a object that is meant to be spread onto an
<Form>
<Form>
component. [useTable search; tables search]

To avoid the warning, make sure you are doing something like this:

Key points:

Do not call yourself; let refine manage that internally.
Always attach to an actual
```
<Form>
```
```
<Form>
```
(), not to arbitrary elements or only partially.
If you don’t render a search form at all, you should avoid using so no unattached form instance is created.

kapa.ai•12/10/25, 11:31 AM

If you are already spreading into an Ant Design

<Form>

<Form>

exactly as in the docs and still see this warning, the knowledge sources do not provide additional debugging steps for this specific case.
----------------------
Note: you can ask me a follow up question by @ mentioning me again

----------------------

kapa.ai•12/10/25, 11:31 AM

@347285614531444756 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

moderate-tomatoOP•12/10/25, 11:34 AM

@kapa.ai I'm not calling manually "formSF.form.getFieldsValue()", I was talking of the internal code of refine in file useTable line 130

GitHub

refine/packages/antd/src/hooks/table/useTable/useTable.ts at main ...

A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility. - refinedev/refine

kapa.ai•12/10/25, 11:34 AM

Let me check the knowledge base for you again. One moment!

kapa.ai•12/10/25, 11:34 AM

----------------------
You’re right, that call is inside refine’s Ant Design implementation, not in your own code. The warning still indicates that the Ant Design instance created for the search form is not attached to any

<Form>

<Form>

element.

From the docs and related issues, we can infer two important points:

**`searchFormProps` must be spread onto an Ant Design `<Form>`** `useTable` returns `searchFormProps` specifically to be passed to `<Form>` so that the internal `formSF` instance is connected and those internal calls like `formSF.form.getFieldsValue()` are safe. [[useTable return](<https://refine.dev/docs/ui-integrations/ant-design/hooks/use-table/#return-values>); [tables search](<https://refine.dev/docs/guides-concepts/tables/#search>)]Correct usage (what refine expects) looks like:

[useTable search]

If is not used this way (e.g., not rendered at all, spread onto a non- component, or overridden), the internal

form

form

instance becomes “unconnected” and triggers that Ant Design warning.

kapa.ai•12/10/25, 11:34 AM

There’s a past bug around form props, but no separate “fix” instructions in the sources
There was an earlier bug where did not conform to Ant Design Form props and a fix was released in . [useTable form bug]
The knowledge sources do not provide additional, newer instructions for this exact warning beyond using correctly.

Given what’s available in the docs and issues, the concrete things you can do to eliminate the warning are:

Ensure you have exactly one Ant Design
```
<Form>
```
```
<Form>
```
that uses like .
Don’t destructure and reassemble pieces of in a way that drops the internal
```
form
```
```
form
```
connection.
If you don’t need a search form, don’t use at all (i.e., don’t access it from ), so refine doesn’t create an unused form instance.

The knowledge sources don’t include more detailed internal changes to or a separate configuration flag to suppress this behavior, so if you are already using and the warning still appears, that specific situation isn’t covered in the provided materials.
----------------------
Note: you can ask me a follow up question by @ mentioning me again

----------------------

kapa.ai•12/10/25, 11:34 AM

@347285614531444756 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

moderate-tomatoOP•12/10/25, 11:37 AM

@kapa.ai my usage is the following : <Form
{...searchFormProps}
initialValues={{
name: getDefaultFilter("name", filters, "contains"),
}}
layout="inline"
>
<Form.Item name="name" noStyle>
<Input
size="large"
allowClear
prefix={<SearchOutlined className="anticon tertiary" />}
suffix={
<Spin size="small" spinning={tableQuery.isFetching} />
}
placeholder={t("list.searchByName")}
onChange={debouncedOnChange}
/>
</Form.Item>
</Form>

kapa.ai•12/10/25, 11:37 AM

Let me check the knowledge base for you again. One moment!

kapa.ai•12/10/25, 11:37 AM

----------------------
Your usage pattern matches the documented pattern for (spreading it directly on an Ant Design

<Form>

<Form>

), which is exactly what refine expects. [Antd table search; useTable search]

Given the knowledge sources, there are two things you can safely do:

**Let refine control `initialValues`** `searchFormProps` already contains form-related props (including `initialValues`) wired for the search form. Overriding `initialValues` at the `<Form>` level might interfere with how refine wires the internal form instance.Instead, set the initial filter via `useTable`’s `filters.initial` and then read it in the input using `getDefaultFilter` (as shown in the docs): [[Initial filter/sorter](<https://refine.dev/docs/ui-integrations/ant-design/hooks/use-table/#initial-filter-and-sorter>)]

kapa.ai•12/10/25, 11:37 AM

Avoid touching the internal
form
form
instance directly
The docs recommend using (or just submitting the form) to trigger , and not accessing other internal form methods yourself. [useTable return values]

---

The warning you see is produced inside Ant Design when a instance is not attached to any

<Form>

<Form>

; the knowledge sources don’t show a concrete refine bug or additional configuration related to this specific warning beyond:

Using
Using / as documented.

If you’re already following these patterns and still see the warning, the provided sources do not contain further guidance or a confirmed bug description for this exact scenario.
----------------------
Note: you can ask me a follow up question by @ mentioning me again

----------------------

kapa.ai•12/10/25, 11:37 AM

@347285614531444756 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

moderate-tomatoOP•12/10/25, 11:41 AM

@kapa.ai I still got the error even if I changed my code as : <Form {...searchFormProps} layout="inline">
<Form.Item
name="name"
noStyle
initialValue={getDefaultFilter("name", filters, "contains")}
>
<Input
size="large"
allowClear
prefix={<SearchOutlined className="anticon tertiary" />}
suffix={
<Spin size="small" spinning={tableQuery.isFetching} />
}
placeholder={t("list.searchByName")}
onChange={debouncedOnChange}
/>
</Form.Item>
</Form>

kapa.ai•12/10/25, 11:41 AM

Let me check the knowledge base for you again. One moment!

kapa.ai•12/10/25, 11:41 AM

----------------------
The code you’ve shared matches the documented usage of with and , so from the perspective of the docs, you are using it “correctly”. [useTable search; initial filter]

However, the warning you’re seeing:

Instance created by
useForm
useForm
is not connected to any Form element. Forget to pass
form
form
prop?

is emitted by Ant Design when a instance isn’t attached to a

<Form>

<Form>

component. That’s happening inside refine’s (), and the knowledge sources you provided do not:

Describe this specific warning as a known bug in the current implementation, nor
Provide an official workaround beyond using and wiring as shown in the docs. [useTable return values; tables search guide]

Because of that, I can’t confidently give you a definitive fix based only on these sources.

What is clearly supported by the docs and examples:

Use with and spread on an Antd
```
<Form>
```
```
<Form>
```
. [useTable search]
Use
- if you want initial filter values. [initial filter]

Your latest snippet follows these patterns, so the remaining warning appears to be a behavior that isn’t covered or explained in the available documentation and issues.

kapa.ai•12/10/25, 11:41 AM

In other words: based on the knowledge sources, you are using the API as intended, and there is no additional documented change you can make to reliably remove that warning.
----------------------
Note: you can ask me a follow up question by @ mentioning me again

----------------------

kapa.ai•12/10/25, 11:41 AM

@347285614531444756 Kapa.ai is still learning and improving, please let me know how I did by reacting below.