Share this page

# Supported field type mappings

The following table lists the PPM-OpenText Software Delivery Management field type mappings. These field type mappings are also applicable to fields that are not visible on UI pages.

PPM Field Type | Sync Direction | OpenText Software Delivery Management Field Type | Notes
--- | --- | --- | ---
Portfolio | Bi-directional | Memo String List | The Portfolio field is available for PPM request type that uses a request header type that includes either of the following field groups: PFM - Proposal, PFM - Project, or PFM - Asset. Value mapping is supported when matching with a List field in OpenText Software Delivery Management.
Text Field Text Area | From OpenText Software Delivery Management to PPM | Float | Sync Actual Value and Perceived Value of an OpenText Software Delivery Management epic or shared epic to a PPM text field or text area field. For syncs from OpenText Software Delivery Management to PPM, they succeed only when the text field or text area field in PPM supports the float data mask. For syncs from PPM to OpenText Software Delivery Management, the telephone text field is not supported. For the currency and percentage text fields, the syncs only succeed when PPM passes numbers to OpenText Software Delivery Management. If the currency and percentage signs are included in the text fields, the syncs fail.
Text Field Text Area | From OpenText Software Delivery Management to PPM | Progress | Sync the progress of an OpenText Software Delivery Management epic, shared epic, feature, and user story to PPM field. If the progress value in OpenText Software Delivery Management has decimals, when passed to PPM, the value is round to the nearest integer. If the progress value in OpenText Software Delivery Management is bigger than 0 and smaller than 0.4, the value "1" is stored in PPM field. If the progress value in OpenText Software Delivery Management is bigger than 99.5 and smaller than 100, the value "99" is stored in PPM field.
Text Field Text Area | From PPM to OpenText Software Delivery Management | User | Sync successfully if PPM passes email address that exists in OpenText Software Delivery Management. If PPM passes email address not existing in OpenText Software Delivery Management, the ALM Octane field is cleared. Only support sync of a single user per time.
Text Field Text Area | From OpenText Software Delivery Management to PPM | User | Use email address to find the matching user in PPM. If a matching user exists in PPM, the user's full name in PPM is displayed in the PPM field. If no matching user exists in PPM, the user's full name in OpenText Software Delivery Management is displayed in the PPM field. Multiple users are separated by ";".
User User List | From PPM to OpenText Software Delivery Management | String Memo | Multiple users are separated by ";".
User User List | From OpenText Software Delivery Management to PPM | String | Sync successfully when OpenText Software Delivery Management passes full names that exist in PPM. If OpenText Software Delivery Management passes full names not existing in PPM, the PPM filed keeps the old value. If OpenText Software Delivery Management passes an empty value to PPM, the PPM field is cleared. Support sync of multiple users per time.
Integer | Bi-directional | Integer |
Text Field Text Area | From OpenText Software Delivery Management to PPM | List |
Text Field Text Area | Bi-directional | String Memo |
Text Field Text Area | Bi-directional | Phase | When the OpenText Software Delivery Management entity is created, PPM can pass any existing phase value to OpenText Software Delivery Management. If PPM passes an empty value, the OpenText Software Delivery Management Phase field is filled with the default value "New". After OpenText Software Delivery Management entity is created, PPM can only pass phase values that follow the phase change logic. Phase values are case-insensitive.
Text Field Text Area | Bi-directional | Release | For syncs from PPM to OpenText Software Delivery Management, they only succeed when PPM passes release values existing in OpenText Software Delivery Management. Release values are case-insensitive.
Text Area | From PPM to OpenText Software Delivery Management | Comments | Treat every non-blank text from PPM as new comments that would be added in OpenText Software Delivery Management. If PPM passes the same content, it is not added as new comment in OpenText Software Delivery Management.
Text Area | From OpenText Software Delivery Management to PPM | Comments | If OpenText Software Delivery Management passes comments with html tags to PPM, the comments will be synced to PPM as an attachment.
User User List | From PPM to OpenText Software Delivery Management | User | Use user email address to find matching user in OpenText Software Delivery Management. If a matching user exists in OpenText Software Delivery Management, sync successfully. If no matching user exists in OpenText Software Delivery Management, the OpenText Software Delivery Management field is cleared.
User User List | From OpenText Software Delivery Management to PPM | User | Use user email address to find matching user in PPM. If a matching user exists in PPM, sync successfully. If no matching user exists in PPM, the PPM field is cleared.
ACL DDL | From PPM to OpenText Software Delivery Management | String Memo |
ACL (SQL-Custom) DDL (SQL) | Bi-directional | List | Value mapping is not supported. Sync successfully when passing existing values. Case-sensitive for the sync between PPM list values and OpenText Software Delivery Management system list values; Case-insensitive for the sync between PPM list values and OpenText Software Delivery Management custom list values "Phase" and "Release" fields are not covered in the OpenText Software Delivery Management "List" field type.

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: