ReadonlyapiContains base API URL to use when calling backend methods for this particular item.
ReadonlyavailableList of layers, that can be added to this change, together with the permission that the current user has for each of them.
ReadonlyblobBlob id of file (checksum of file contents).
ReadonlycontainerId of BimContainer to which this change belongs.
Optional ReadonlydisciplineDiscipline. Example A, K, V etc
Readonlyetagetag for change. Used for optimistic concurrency checks and in operations where we want to check if data has changed or not since last etag we have.
ReadonlyformatFormat of change.
ReadonlyidId of change.
ReadonlymetadataMetadata for the file.
ReadonlyserverRelativeUrl: stringserver relative path of file
ReadonlynameName of change.
ReadonlyownerId of system that the change originated from. If a change in Twinfinity was created because an external system pushed it into Twinfinity then the id will refer to that system. If change originates from Twinfinity (for example because a file was uploaded by a user) then the id will always be 'twinfinity'.
ReadonlypathUnique path for the change. Each change has one. If the change or one of its parents are renamed then the path will change.
Readonlypermissions64 bit permission bitmask. Used to verify that a user has required permissions on a change. Since there is no native JSON support for bitmasks, the value is derived from permissionsString.
ReadonlypermissionsString used to represent the permissions bitmask.
ReadonlytypeReadonlyurlURL of change content. Points to the endpoint where the content of the change can be retrieved by a simple GET request.
ReadonlyversionVersion of change
Represents a generic file that is not defined by other change types such as BimChangeIfc or BimChangeDwg.