Page Comparison

Metadata

Select the Metadata value from the dropdown list for the operation you want.

• Office365Team - Used to rename an existing team.

• Office365Group - Used to create a workspace.

• Office365TeamIdCollection - Used to request/remove access.

Default Value

Enter the default value to be assigned to the metadata value.

Is Hidden

Select the Hidden status value.

Is Read Only

Select the read only value.

Display Label

Enter a display name for the metadata. Make this as specific as needed to differentiate between similar metadata names that may exist.

Help Text

Enter help text to be displayed as a tool-tip on the custom field.

Type

Select the type of metadata from the drop-down. Options include:

• Date: Represents date value (e.g. 2018-10-10)

• String: Alphanumeric characters (e.g. cam123)

• Boolean: Represent logical values (e.g. True or False)

• Number: Numeric data values (e.g. 1,2,3)

• Currency: Represents integer format (e.g. 123.456)

Look Up

By default Look up value is No for selected metadata value.

Order

Set the order of the metadata to be displayed on the panel.

Panel

Select the panel for the metadata to be displayed. Based on the selection here the fields will be displayed in the panel.

Editable

Select Yes to allow the metadata value to be edited in the workspace dialog.

Lock Existing Values

This option doesn't allow users to create a new workspace using previously added values of specific metadata, locking the existing metadata.

When a new Unique Metadata field in Configure Wizard is added, the option to Lock Existing Values displays. If Lock Existing Values is selected as Yes, Create a new value option should be automatically selected as Yes. The option No should be disabled. Also, the Default Value option is disabled.

If the Metadata with Lock Existing Values option is 'No', then users can only add values to Metadata by clicking the '+' button. After the user enters values for that Metadata, there is a validation to check if that value already exists. If the value already exists, the user should not be able to save that value.

E.g. Lock existing set to yes and is parent set to yes, means the unique metadata field matter will not allow inputting duplicate matters if any parent matters exist. If no for parent, and yes for lock, then if the metadata exists in entire system, then the value can't be added.