Beam Help — independent expert support for Zoho. Below are concise instructions for pre-populating a lookup field in Zoho CRM SlyteUI using the crm-field component, based on the community working sample that shows the exact structure you must copy rather than guessing formats[1].
Note: Beam Help is not official Zoho support[1].
Why this matters
If you build custom SlyteUI records that must show an existing related record, the lookup must be set with the precise structure shown in the community sample — passing a bare record ID string will not work[1].
Using the wrong format causes the field to stay empty or reject the value, so copying the sample structure avoids trial-and-error and saves development time[1].
Step-by-step
- Step 1. Start from the crm-field component for the lookup field that you want to pre-populate and prepare to pass a value object rather than a plain string[1].
- Step 2. Do not pass the record ID as a plain string; the community thread shows that plain string values do not work for SlyteUI lookup fields[1].
- Step 3. Refer to the working sample posted in the community thread and copy the exact object structure it shows for the lookup value; the sample is the reliable source for the correct shape to send to crm-field[1].
- Step 4. Replace the sample’s placeholder IDs and display names with your actual related record’s ID and label while keeping the object structure identical to the sample[1].
- Step 5. Bind that object to the crm-field component so the component receives the lookup object at render time rather than a primitive string[1].
- Step 6. Test by opening the SlyteUI form and confirming the lookup displays the related record as shown in the sample; if it does not, re-check you copied the object keys and nesting exactly as the sample shows[1].
Common pitfalls
- Passing a plain record ID string will not pre-populate the lookup field in SlyteUI; the community post explicitly reports that approach fails[1].
- Trying a guessed object format can fail; the post recommends copying the provided working sample structure exactly rather than inventing key names[1].
What to check
- The crm-field receives an object that matches the community working sample’s structure, not a plain string[1].
- The IDs and display values inside that object are the actual record identifiers and labels from your CRM environment[1].
- The lookup renders on the SlyteUI form the same way the working sample shows after you bind the object to crm-field[1].