I want the text in Text to be copy under Lookup

1

I want the one in the picture I attached.
1.

555
555447×183 3.27 KB

2.
5555
5555441×127 2.14 KB

2

Hi @Master_Over_Sun :slight_smile:
Thanks for the post.

To assist you more effectively, could you share the code you’ve worked on and let us know the issues you’re encountering?

3

Here I did it in HTML to show you what I wanted. Sorry I don't have the code to show you. :pray: :pray: :pray:

4

Hello @Master_Over_Sun
I can't understand your goal based on your description and screenshots.

Are you trying to copy the text from a table's text field to a field outside the table, to the text right below the lookup in the same row, or something else? Also, what is the purpose of doing this?

It would be much easier to assist you if you could elaborate on your goal and provide more specific details on what you're trying to achieve.

Thank you.

5

Hi
In my table, I want the text in the Text field to appear directly under the Lookup field, without creating a new row. When clicking on Lookup, it should display relevant information within the same field, making it easier to identify what we're looking for. I hope to achieve this using JavaScript or CSS.

6

Hello @Master_Over_Sun

To display the value of a "Single-line text" field directly below a "Lookup" field within a table, customization using DOM manipulation is required.

Additionally, by leveraging field change events triggered during record creation or record editing, you can execute a process whenever the "Single-line text" field is modified.

In theory, implementing a process that appends the value of the "Single-line text" field directly below the "Lookup" field when a change event is triggered could achieve behavior close to the desired outcome.

However, while attempting to create a reference implementation, I encountered several challenges that would require additional DOM manipulation, making implementation quite complex:

Challenges:

  • Identifying the correct row being modified
    • While the table ID can be obtained in the record editing screen, it is not available on the record creation screen, requiring an alternative approach.
  • Checking whether an element embedded via DOM manipulation in the "Lookup" field already exists
    • Without this validation, duplicate elements may be generated with each execution.

Additionally, during testing, I found that even on the record detail screen, when a row is added, the table ID becomes null, making it impossible to determine which row is being modified. This further complicates implementing a reliable process for handling added rows.

So in the end, instead of using the above method, it would be much easier to change the key field to one that can be more easily identified. Since the key field is what is displayed in a Lookup field, adjusting it could simplify the process significantly.

Additionally, DOM manipulation should be avoided in Kintone, as system updates may introduce regressions that could break the implementation.

1 Like