v8.0.1 - Sync Editor virtual properties

Isn't Person.CentralAccount the same as ADSAccount.samAccountName in your environment?

/H

I've just used samAccountName as an example, we need a few other attributes from ADSAccount... and also, yes, its not the same

You could always use script property as a virtual property to get the attributes you need..

Thanks Henrik, yes I was hoping we can do that but don't have any code snippet or example. The script property interface is not familar to me, and I tried using Session but that doesnt work. Do you have any examples which can help?

Sorry, just found the answer by Markus on another thread. For reference

www.oneidentity.com/.../synchronization-editor-problem-mapping-property-with-script-retrieve-object

However, the solution in that thread doesnt work as tit complains that it cant fid the ADSAccount schema type (even though I have loaded that schema and it is excluded from shrinking)

My code is shown below (v 8.0.1 expects C# code so I have translated), there are no compilation errors on the code but strange that it can;t find ADSAccount

using VI.Projector.Connection;

ISystemObject[] sam = SystemObject.Connection.QueryObject(SystemQuery.From("ADSAccount").Select("SamAccountName").Filter(String.Format("UID_Person = '{0}'", $UID_Person$))).Result;

foreach (var s in sam)
{
return s.GetValue("samaccountname").AsString;
}
return "notfound";

Error is:

Property (vrtSam@dbo.Person) could not read the value from system object (BLoggs(E), Joe <Middlename?>)!
Error executing 'Get' script for (vrtSam@dbo.Person)!
Exception has been thrown by the target of an invocation.
The schema type (ADSAccount) does not exist in schema xxxxxx 

As described in the mentioned thread. You need to pin the ADSAccount objects in your schema, as the connector is only able to access objects that are part of your sync project schema. So when you shrink the schema, you need to exclude the ADSAccount table from the shrink, when it isn't a part of your sync project already, which seems to be the case.

As described in the mentioned thread. You need to pin the ADSAccount objects in your schema, as the connector is only able to access objects that are part of your sync project schema. So when you shrink the schema, you need to exclude the ADSAccount table from the shrink, when it isn't a part of your sync project already, which seems to be the case.

HI Markus

I have already excluded the ADSAccount schema from being shrunk, so it is always present

Forgive me my stupid question, but the virtual property is defined on the OneIM side (left) in the mapping?

Actually on the right hand side - we have a sync between 2 instances of OneIM. From the RHS instance we need some additional data which is stored in the ADSAccount table, and are trying to extend the existing Person<->Person mapping to include these extra attributes on the RHS

Mmhh. Are you sure, that the schema type ADSAccount is still part of the target system schema?

And, what type of connector are you using to connect your right-hand side OneIM?

Hi Markus, yes 100% the ADSAccount table is present, it is excluded from being shrunk (along with a few other tables)

We are using a Native Database Connector to connect the two instances.

Does the ADSAccount table itself need some kind of mapping present? We have no mapping on ADSAccount, its just part of the schema

I've asked the developer and he reminded me that schema class is called "dbo.ADSAccount" on the target system side.

Try this name, and it should work.

Perfect, it was indeed dbo.ADSAccount, all works fine now, thanks a lot Markus!