If you are just using the form builder, then no but if you switch the form to code mode or convert the project to the CLI you can do it either of these ways:

If your api supports retrieving an object by its id then once a user selects an option and you have the object id, you can make another request before your main one that retrieves the full details of that object. 

Alternatively,  you could JSON.stringify each of the objects and set the string as a new value in the object before returning the results.

  return z.request(options).then((response) => {
    response.throwForStatus();
    const results = response.json;

//results is an object, results.data is the array of objects I want to use in my dynamic dropdown

    results.data.forEach(object => {
      var temp = JSON.stringify(object);
      object.stringObject = temp;
    });

    return results.data;
  });

Then you can use the new key ‘stringObject’ as the value you want from the dynamic dropdown

then you can JSON.parse the value selected to get it back into its proper form and from there pick off what you need.

Thanks for the quick reply!

So if I understand it correctly, I should first fetch say UUID using the Dynamic Dropdown and then use the UUID to make another call to our API that retrieves the rest of the information?
Should I use the Dynamic Field for this second call? 

Hi @Chooboo 

If you go the second call route, you would not use an additional field. The second request would happen behind the scenes prior to your main request. 

I have also edited my initial response as I thought of a second solution that didn’t use a second api call. 

I’ll definitely check it out, thanks again!