Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Agile (MOSC)

Bug 23518983 : ETL FAILING IF MORE THAN 400 ATTRIBUTE MAPPINGS CONFIGURED IN OPLA CONFIGURATOR

Apr 20, 2017 1:56PM edited May 25, 2017 4:54PM in Agile (MOSC) 2 commentsAnswered

Hello. It's nice to see that this 400 attribute constraint has been resolved in OPLA 3.5.0.0.3.

But what is the solution? Is there no upper limit now? 425 attributes? 500 attributes? 1000 attributes?

Thank you to whomever has this answer and can provide here.

2

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month