AML throws Aras.Server.Core.AmbiguousCriteriaException

I'm trying to update the datasource of a property to the correct datasource in our test and production environments, but without the use of ID's because that's what caused the problem I'm trying to correct in the first place, the id's for (for instance) properties in test and production don't always match the id's in our development environment. So, I wrote this AML:
<Item action="edit" type="Property" where="[Property].keyed_name = 'era_locked_by'">
  <data_source keyed_name="locked_by_id">
    <Item type="Property" action="get" select="id" where="[property].keyed_name = 'locked_by_id' and [property].source_id in (select it.ID from innovator.ITEMTYPE it where it.name = 'DOCUMENT')" />
  </data_source>
</Item>
but when I run in Innovator Admin for instance, it returns <af:exception message="Aras.Server.Core.AmbiguousCriteriaException" type="Aras.Server.Core.AmbiguousCriteriaException" /> This is probably because of the nested Properties where statement, but is there any to make this work, without using actual id's?
Parents
  • So, to answer my own question, because I ran into this issue again (and yeah I forgot this). It works fine for properties on itemtypes that have actual relations in the database, i.e. source_id on a item_type that has a relation to another table. Data_source on the other hand, does not have a relation to other tables, because data_source can be of type List as well, therefor a SQL WHERE statement wouldn't work that well on the data_source column/property
Reply
  • So, to answer my own question, because I ran into this issue again (and yeah I forgot this). It works fine for properties on itemtypes that have actual relations in the database, i.e. source_id on a item_type that has a relation to another table. Data_source on the other hand, does not have a relation to other tables, because data_source can be of type List as well, therefor a SQL WHERE statement wouldn't work that well on the data_source column/property
Children
No Data