1. Using the Oracle Visual Builder Add-in for Excel in Oracle Integration
  2. Known Issues and Limitations

16 Known Issues and Limitations

This chapter describes the issues (defects) and limitations that have already been identified for the Oracle Visual Builder Add-in for Excel

Known Limitations

  • Never edit the Key column of the table.

  • Avoid using the following Excel features with the add-in. The following is a sample list of Excel features that do not work well with the add-in. Other Excel features not listed may also not work well with the add-in.

    • Do not use the Protect Sheet or Workbook features of Excel.

    • Do not attempt to re-arrange the layout of the integrated worksheet. For example, do no insert rows above the table or columns to the left of the table.

    • Do not use the Mark as Final command to make the Excel workbook read-only.

    • Do not delete anything from the integrated worksheet using Excel's delete features, including the Delete key.

  • If a REST service owner makes significant changes to the service after the workbook is configured to integrate with the service, the integration may not function as expected. In such cases, delete and recreate the layout in the workbook or update the workbook's service description to match the changes in the service.

  • Review REST Service Support to understand limitations around data type support.
  • Review Use Lists of Values in an Excel Workbook to understand limitations around using lists of values.

Known Issues

  • Excel workbooks that you create or modify with version 2.1 of the add-in are not compatible with prior add-in versions.
  • Due to an issue with the Oracle RAMP REST service, all required fields have the Required property deselected. To work around this issue, use the add-in's Business Objects Field Editor to select the Required property where appropriate.
  • When using Oracle REST Data Services earlier than version 19.2, some date-time fields are not recognized as a date-time data type due to faulty service metadata. Use the add-in’s Business Object Field Editor to correct the data type.
  • For an Oracle RAMP REST service that exposes entity- or view-object attributes that set the Updateable property to While New, the add-in is currently unable to detect the While New designation and fields that correspond to such attributes will be marked as Editable on update = true. As a workaround, use the add-in’s Business Object Editor to mark such fields as Editable on update = false.
  • Certain OpenAPI 3 document properties, such as Description, can contain Markdown text-based formatting markup. The add-in displays the Descriptions verbatim and does not interpret Markdown syntax.