pub struct MixtureUpdate {
pub aliases: Option<Vec<String>>,
pub units: Option<String>,
pub entity_registry_id: Option<String>,
pub author_ids: Option<Vec<String>>,
pub folder_id: Option<String>,
pub fields: Option<Fields>,
pub ingredients: Option<Vec<IngredientWriteParams>>,
pub name: Option<String>,
pub amount: Option<String>,
pub schema_id: Option<String>,
pub custom_fields: Option<CustomFields>,
}Fields§
§aliases: Option<Vec<String>>Aliases to add to the mixture
units: Option<String>§entity_registry_id: Option<String>IDs of users to set as the mixture’s authors.
folder_id: Option<String>ID of the folder that the entity is moved into
fields: Option<Fields>Schema fields to set on the mixture. Must correspond with the schema’s field definitions. Every field should have its name as a key, mapping to an object with information about the value of the field.
If you are setting the parent mixture field here, you must also specify ingredients
ingredients: Option<Vec<IngredientWriteParams>>Desired final state for the ingredients on this mixture.
Each ingredient you specify will be matched with the existing ingredients on the mixture based on the component entity, and Benchling will create, update, or delete this mixture’s ingredients so that the final state of this mixture’s ingredients matches your request.
Benchling will recognize that any ingredients you specify that match ingredients on the parent mixture (based on component entity) are inherited. This can be seen on the returned ingredients[i].hasParent attribute.
name: Option<String>§amount: Option<String>The positive numerical amount value of this mixture in string format (to preserve full precision). Pair with units. Supports scientific notation (1.23e4).
schema_id: Option<String>§custom_fields: Option<CustomFields>Custom fields to add to the mixture. Every field should have its name as a key, mapping to an object with information about the value of the field.