hey @Deepta , sorry for the delay. I have a feeling that the model.Meta object may be handled correctly somewhere. When I used the example script just now, I noticed the meta reference was looking at fields[0][0] but that was empty for me. By changing it to fields[1][0], it seemed to pull the list.
I recently built a tool with 2 inputs and created a handler for the metadata:
// create field name list from metadata
const generateData = (data, connectionId) => {
// If the data isn't filled in, then use these default properties.
console.log("Index - generateData",{data});
if (JSON.stringify(data)=="{}" || !data) {
return ([]); //create a simple lookup table for "missing data" value
} else {
return data?.fields[connectionId][0].fields.map((item) => {
item.primary = item.name;
item.value = item.name;
console.log("generateData",{item})
return item.name
});
};
};
Then when calling the generateData function in the autocomplete, it looked like this:
<Autocomplete
id="Autocomplete"
options={generateData(model.Meta,1)} // was model.Meta?.fields[0][0].fields
renderInput={params => (
<TextField
{...params}
fullWidth
id="ac-meta"
label="Meta Data"
margin="normal"
placeholder="Select Column..."
/>
)}
onChange={handleResourceEvent("fieldSelect")} // was handleFieldSelect
value={model.Configuration.fieldSelect}
/>
the handleResourceEvent was a new function I created to dynamically handle events like field select (because i was using it multiple times):
// to handle class objects you have to break down the data into a newValue which equals the json object.
const handleResourceEvent = (key) => (_, newValue) =>{
const newModel = { ...model };
newModel.Configuration = {...newModel.Configuration, [key]:newValue};
handleUpdateModel(newModel);
};
Hopefully, that helps you get your autocomplete element working. Let me know if you have any questions though.
- Jarrod
