Forum Discussion
The metadata field is used internally to store information about assets, including asset recycling (after delete) and asset search related info. It is persisted within the org, it will not be persisted across project export and migration.
The metadata field is not exposed currently for external use. We could open an enhancement request to expose and document the metadata. The metadata does have limits in terms of data size. Limiting the external metadata to under 16 entries with values lower than 1KB in size each would be recommended.
- dcyr4 years agoNew Contributor
Thanks for the response - much appreciated. I expected this might be the case and have decided to try to accomplish my goal without using the metadata property. I do think it would be helpful though to be able to decorate the resource (pipeline etc) with custom data that could be persisted across project export and migration. Something along the lines of the below snippet maybe…
“customProperty”: {
“property1”: “shared”,
“property2”: “operations”
}