This operation is a Technical Preview and is available for testing purposes only. Do not use in production.
POST https://qa-api.bentley.com/transformations/configurations/groupandmap
This endpoint is used to create the Group And Map configuration.
The Group And Map transformation enables the creation of new custom EC schemas and is capable of remapping already existing elements to the new EC classes with new EC properties. The custom schema is constructed using grouping and mapping data. It is your responsibility to create a valid mapping for the source iModel through the Reporting API before starting the transformation. To learn more about EC schemas and classes, please see Base Infrastructure Schemas.
Mapping -> EC schema
Group -> EC class
GroupProperty -> EC property
After the transformation all elements that were selected with the group query will be remapped to the corresponding EC class. These elements will also have all the new EC properties inserted. The newly inserted EC properties' values will be populated with the help of 'ecProperties' field taken from the respective GroupProperty which you configured beforehand.
POST configuration specific properties explained:
mappingId - source iModel mapping id.
groupOverrides - list of overrides for each group.
- groupId - id of mapping group.
- baseClass - base EC class that will be applied for elements selected by group.
- ecSchemaName - EC schema name.
- ecClassName - EC class name.
additionalEcSchemas - list of additional EC schemas that will be added to target iModel.
- ecSchemaName - EC schema name.
- ecSchemaVersion - EC schema version.
In addition to exported data, the transformer will also push some additional metadata. This metadata contains:
BisCore:RepositoryLink and BisCore:ExternalSource elements that mark the source where the data was imported from.
A "Scope" BisCore:ExternalSourceAspect that contains Synchronization changeset metadata that is needed by the transformation service to process any later changes correctly.
Element provenance information (BisCore:ExternalSourceAspects) for elements that do not have federation guids.
Note: Creating a configuration does not run the transformation. To run the transformation, please see transformations reference.
You must have imodels_write assigned at the target project level and imodels_read assigned at the source project level within related configuration. If permissions at the project level are not configured, then you must have same assigned at the iModel level.
Alternatively, you must be an Organization Administrator for the Organization that owns a given project the iModel belongs to.
An Organization Administrator must have at least one of the following roles assigned in User Management: Account Administrator, Co-Administrator, or CONNECT Services Administrator. For more information about User Management see Bentley Communities Licensing, Cloud, and Web Services wiki page.
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
json
HeaderNotFound
{"error":{"code":"HeaderNotFound","message":"Header Authorization was not found in the request. Access denied."}}
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.