This content has been marked as final. Show 3 replies
Solution: change the identifying attribute of your entity to a text attribute.1 person found this helpful
The identifying attribute is used in substituting the entity text within decision reports, screen labels etc. In OPA v10.4, the identifying attribute is also used to identify inferred entity instances, which is why the validation is more strict - although the requirement for the identifying attribute to be a text attribute has always existed. Therefore ensure that the correct attribute is being assigned as the identifying attribute for your entities, and if necessary create an inferred text attribute that is equivalent to the number attribute you are currently using and make that the identifying attribute.
See the topic "Define an entity" in the Oracle Policy Modeling User's Guide for further details on identifying attributes.
I can understand the complexity. I have solved it differently, but my colleague says it would be better if I could have the same rule table in working condition.
PS: In the same document, there were other rule tables for inferring number attributes . They were working properly.
You will have to have a separate number attribute that is not the identifying attribute, and use that in your Excel table.
Then change the identifying attribute to be of type Text, and use a rule to assign it the value of the number attribute set in the Excel rule table.