Create custom input field component

Hi Team,

I’ve created a custom React component to render an input field within the UESIO platform. The component is working as expected in terms of rendering and setting values via setWireValue.

However, I’m facing an issue in the component’s property panel:

The “Field ID” dropdown is not populating based on the selected wire (just like it does for built-in UESIO components such as uesio/io.field).

Could you please guide me on:

How to define the component property schema so that the Field ID dropdown appears dynamically, showing only fields from the selected wire.

If there’s a specific config or metadata I need to attach to the fieldId property to make it wire-aware (e.g. type: FIELD_ID with wire binding).

My goal is to allow users to:

Select a wire from a dropdown.

Dynamically populate the “Field ID” dropdown based on the selected wire.

Have the input field bind to the correct wire and field at runtime.
I’ve attached a screenshot of my current custom component schema for reference

Hello @rbdwt09 -

You are close, a couple of adjustments from what you currently have:

  - name: wire
    type: WIRE
    label: Wire
  - name: fieldId
    type: FIELD
    label: Field Id
    wireField: wire

Hope this helps!

Regards,

-bds

Hi barry,

I’ve reviewed both the custom YAML structure (screenshot attached) and the default UESIO field component for input handling (also in the screenshots below).

Planned Adjustments:- The core functionality — binding to a wire and updating a fieldId — will remain unchanged to ensure consistent data integration.

  • I’ll make a minor refinement to the Read Only checkbox, so its behavior matches UESIO’s native handling more precisely.

  • In addition, I’ll align the YAML definition more closely with the default UESIO field properties, by incorporating:

    • required

    • minValue / maxValue (for length validation)

    • and any other relevant UI flags visible in the default configuration

These enhancements will make the custom input behave more consistently with standard UESIO inputs while keeping it flexible and wire-driven.

(attachments)


Hi @rbdwt09 -

Seems like you are making great progress! Let us know if you have any questions as you work through the remaining items.

Regards,

-bds

Hi @barry,

Thanks for your response!

Just a quick follow-up—could you please confirm how we should define the Read Only behavior in the YAML configuration? Specifically, I’d like to know the correct property or flag to use in the YAML so that it aligns with UESIO’s standard Read Only handling.
UESIO field component for input handling (also in the screenshots below).but its not working for read only property.

Hello @rbdwt09 -

Below is the yaml configuration for the “Read Only” property that UESIO uses for it’s “FIeld” component:

  - name: readonly
    type: CHECKBOX
    label: Read Only

Regards,

-bds

yes that worked we can close this issue.