Performance Issue With Search Using Custom Part Search Fields After Upgrade to 23B
(Doc ID 2959565.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle BigMachines CPQ Cloud Service - Version 23 B Patch 3 and laterInformation in this document applies to any platform.
Symptoms
After the upgrade to 23B, the customer encountered a performance issue with their advanced part search that used custom fields. The time for the process to finish varied between 35 seconds to even 4 minutes, but most of the time was spent on getting to the landing page.
We could observe that the same query with a OOTB part search field took the normal amount of time (about 2-5 seconds).
Changes
This could be seen after the upgrade to 23B.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |