You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have an element that contains a multi-instance element and we make a copy of the nested element in the Metadata Editor then the generated nested element instance does not contain an @id field.
For example, assume we have an element named My Element that contains a nested multi-instance Address element and put My Element in a template as a single instance element:
If we click on the clone icon the make a new Address and then click Save we get the following JSON-LD:
The second Address instance does not have an @id, which is invalid.
Oddly, we can still save the instance. However, when we attempt to copy this instance in the desktop the copy fails with a validation error because of the missing @id
Also, this does not happen with a single level of nesting, e.g., if the Address element is directly placed as a multi-instance element at the top level of the template.
The text was updated successfully, but these errors were encountered:
If we have an element that contains a multi-instance element and we make a copy of the nested element in the Metadata Editor then the generated nested element instance does not contain an @id field.
For example, assume we have an element named My Element that contains a nested multi-instance Address element and put My Element in a template as a single instance element:
If we click on the clone icon the make a new Address and then click Save we get the following JSON-LD:
The second Address instance does not have an @id, which is invalid.
Oddly, we can still save the instance. However, when we attempt to copy this instance in the desktop the copy fails with a validation error because of the missing @id
Also, this does not happen with a single level of nesting, e.g., if the Address element is directly placed as a multi-instance element at the top level of the template.
The text was updated successfully, but these errors were encountered: