Flex attributes or OOTB attributes
Hello
Need advice on any performance hit that may happen as a result of using the flex attributes.
I have set up 70 sub-classes each subclass has an average of 30~40 on Page and anywhere between 10-20 on Page 3, all attributes are setup as Flex attributes.
The choice was made due to axml export not retaining the name of the attribute if using the OOTB and integrating with non oracle system double mapping of the attribute would be required.
Example
On page 3 using the OOTB Text01 and new Flex image001.png for java client view, you can see that axml Image002.png is only exported with the right name for the flex,
Let me know if you have experience with any performance hit.
I am aware of the limitation of using the flex attributes as i have read the documentation in regards to using Data Load and or Notification.
Thanks in advance
Stefano
The biggest limitation that I have found (which isn’t mentioned in the limitations from the manual) is that Page 2 user defined flex fields cannot be used as “read through’ fields on other object tables (BOM, Affected Items, etc.)
I find the read-through capability to be very useful so I try to avoid using the user defined flex fields whenever possible.
You are correct about the axml mapping, but this is relatively painless to sort out using the Class Configuration reports.
