When an RFI portfolio is migrated to iCode, this field appears as Document ID. The Document ID in iCode therefore corresponds to the ID displayed in the legacy RFI tool.
You may also see a separate ID field in iCode if an additional ID field was included in the source data. This field is separate from the system-generated Document ID.
In iCode:
- An additional ID field included in the source data can appear as an optional field during the Manage Content process. This field is separate from Document ID, and its field type can be configured.
- Document ID does not appear as an optional field for migrated legacy portfolios or new projects created from spreadsheets. Its field type cannot be changed, and it is stored as a string.
Note: The distinction between ID and Document ID is primarily relevant to migrated RFI portfolios. New projects created from spreadsheets do not have the same legacy RFI field-mapping issue.
Example: Comparing ID fields
In the example below, the legacy RFI portfolio displays ID = 80. After migration to iCode, that value appears as Document ID = 80. A separate uploaded ID field also appears with a value of 0.
Field settings in iCode
Included fields
Field types
Note: Document ID is not available as a field type that can be changed.
Comments
0 comments
Article is closed for comments.