Item Number Generation
The Integrator only supports the 'Item Number Generation Method'. The 'Configured Item Number Generation Method' is currently not supported but is planned for a future release.
When the ‘Item Number Generation Method’ is ‘Sequence Generated’:
The ‘Item Number’ must be left blank when creating a new item. The Integrator will error the ‘Item Number’ column if it contains a value. Successful uploads will return the new item number to the worksheet based on your system configuration options.
Only one ‘Sequence Generated’ Item can be uploaded in a single upload. The Oracle web service will generate the following error If more than one ‘Sequence Generated’ item gets uploaded together:
Too many objects match the alternate key oracle leads to duplicate keys for this entity type ItemVersionEO
Diagram1 - For the above scenarios, the first and the last rows are ‘Sequence Generated’ item records. They must be uploaded individually from each other. Select the first ‘Sequence Generated’ Item, as depicted in the yellow shaded row, and upload it. Then select the second ‘Sequence Generated’ Item, as depicted in the other shaded row, and submit it as a separate upload.
Diagram 2 - Select the first ‘Sequence Generated’ Item and any ‘Non-Sequence Generated’ Items if desired, as depicted by the yellow shading above, and upload them. Then select the second ‘Sequence Generated’ Item, as depicted by the single shaded row above, and action it as a separate upload.
Formatted Description
When downloading the item, the read-only ‘Formatted Description’ field will be returned with a format that includes HTML tags.
The HTML Tag contains all the format data (i.e. font, size, bold …) e.g. Description<font size='6'> in Different <font size='4'>sizes</font></font><br/>. This is how the Oracle web service returns information to this column and is not something we can control in the download. We suggest using Excel formulas to trim any tag information should you need to use this data elsewhere.
Performance
• Data entry forms, when first opened in the session, will undertake initialization steps along with caching list of value (LOV) information from the instance. This can take time, depending on the number of columns on the sheet. For improved performance we recommend removing columns that are not used.
o Subsequent form openings will run faster without the need for the first initialization as the caches will be populated.
• Due to performance problems with Oracle’s web service, More4apps recommends limiting uploads to not more than 500 items.
• The Oracle web service used for retrieving Items has a limitation for downloading records. More4apps recommends limiting downloads to 300 or less records.
These limits may improve over time as Oracle enhances these gateways.
Item and DFF Combination
Due to an Oracle limitation Item and DFF combination needs to be uploaded one at a time.
If more than one combination (Item & DFF) is uploaded, Oracle will fail and return the following error:
'API Error: Rows 47 - 48 have been rejected by Oracle. Due to Oracle limitations, the specific row(s) errored within this range cannot be identified and no error message has been provided by Oracle. [2 Batched Items(s)’.
Attachments
The integrator is only able to create attachments as the Oracle web service does not currently allow for the update or downloading of existing attachments.
Item Image Attachments are currently not supported but are planned for a future release.
To overcome this, we are defaulting item class from ‘Copy From Item’. Once oracle fix this this limitation the default will be removed.
Refer to the Attachment documentation for more information on these limitations.
These limits may improve over time as Oracle enhances the web service.
Sections:
