Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland
------------------------------

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland
------------------------------

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland
------------------------------

Hello,

Thanks for your advice and help. I was able to follow the script. 

Any clue how to map the value person id to "maxuser.personid"? 

Thanks again.

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hi Pankaj,

I'm not sure what do you mean... Could you please elaborate a bit more what is it that is not working?
Basically when the script finds a PERSON record by e-mail, then it injects it into the integration pipeline and MAXUSER record gets created for given PERSON, therefore MAXUSER.PERSONID gets set to PERSON.PERSONID.

Hello,

Thanks for your advice and help. I was able to follow the script. 

Any clue how to map the value person id to "maxuser.personid"? 

Thanks again.

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hello,

Thank you for your patience. The concept of " it injects it into the integration pipeline and MAXUSER record gets created for given PERSON (the code line 

ctx.setMbo(mbo)

  is relatively new to me).  I was therefore confused. I will try the same and get back to you.

Regards

Pankaj Bhide

Hi Pankaj,

I'm not sure what do you mean... Could you please elaborate a bit more what is it that is not working?
Basically when the script finds a PERSON record by e-mail, then it injects it into the integration pipeline and MAXUSER record gets created for given PERSON, therefore MAXUSER.PERSONID gets set to PERSON.PERSONID.

Hello,

Thanks for your advice and help. I was able to follow the script. 

Any clue how to map the value person id to "maxuser.personid"? 

Thanks again.

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hi Pankaj,

I'm not sure what do you mean... Could you please elaborate a bit more what is it that is not working?
Basically when the script finds a PERSON record by e-mail, then it injects it into the integration pipeline and MAXUSER record gets created for given PERSON, therefore MAXUSER.PERSONID gets set to PERSON.PERSONID.

Hello,

Thanks for your advice and help. I was able to follow the script. 

Any clue how to map the value person id to "maxuser.personid"? 

Thanks again.

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hi Pankaj,

I'm not sure what do you mean... Could you please elaborate a bit more what is it that is not working?
Basically when the script finds a PERSON record by e-mail, then it injects it into the integration pipeline and MAXUSER record gets created for given PERSON, therefore MAXUSER.PERSONID gets set to PERSON.PERSONID.

Hello,

Thanks for your advice and help. I was able to follow the script. 

Any clue how to map the value person id to "maxuser.personid"? 

Thanks again.

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland
------------------------------

Hi Andrzej,

thank you for this hint.
We tried it, but the problem seems to be, that we only can add it to manage and not to core. So it has no effect, becuase the table only exists in Core.

How do we add it to core? Do you have a manual?

Thanks in advance

Kind regards

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland

Hi Gunter,

I get the feeling that we're mixing up here different use cases. What I helped Pankaj with was the scenario where he creates user record in MAS Core which needs to be further quite specifically handled when synching MAS Core to MAS Manage.

Could you please describe your use case? Are you still somehow trying to add user to MAS Manage and hoping that it gets synched to MAS Core?

Hi Andrzej,

thank you for this hint.
We tried it, but the problem seems to be, that we only can add it to manage and not to core. So it has no effect, becuase the table only exists in Core.

How do we add it to core? Do you have a manual?

Thanks in advance

Kind regards

Hi Pankaj,

this sounds just like the process at one of my customers :-) 

There are probably other ways to do it but I would recommend creating Object Structure integration processing automation script for MASPERUSER object structure which may look as follows.

Script Name: OSIN.MASPERUSER

Script Source:

from psdi.mbo import SqlFormatdef mboRules(ctx):    table = ctx.getProcessTable()    if table == "PERSON":           data = ctx.getData()        # Mark the character casing - for parent/child navigation you need to use upper-case names        emails = data.getChildrenData("EMAIL")        # Find primary e-mail - example code below looks for a first found primary e-mail        # Mark the character casing - you need to use lower-case to access JSON attributes        primaryEmail = next((e.getCurrentData("emailaddress") for e in emails if e.getCurrentDataAsBoolean("isprimary")), None)        # Find PERSON record with given e-mail        mboSet = ctx.getMboSet()        sqf = SqlFormat(ctx.getUserInfo(), "exists(select 1 from email where email.personid = person.personid and email.emailaddress = :1)")        sqf.setObject(1, "EMAIL", "EMAILADDRESS", primaryEmail)        mboSet.setWhere(sqf.format())        mbo = mboSet.moveFirst()        if mbo:            # Inject identified person MBO into the integration processing pipeline.             # The rule is that if mboRules function returns MBO (through the ctx) then             # the integration logic does not look for one on its own using standard rules.            # The other way to do this would be to simply override "personid" column value            # in the inbound JSON structure data but passing back MBO you save one            # SQL query as the object to be processed has already been identified.            ctx.setMbo(mbo)        else:            # Raise exception            ctx.error("<msggrp>", "<msgkey>", [ "param1" ])    elif table in ["EMAIL", "PHONE"]:        # Skip updates to the EMAIL and PHONE tables        ctx.skipMbo()#end def

MASPERUSER object structure, used by MAS Core to Manage synchronization, uses PERSON record at the top level and you cannot really skip this one as you would not let the integration logic create corresponding child level MAXUSER record (PERSON/MAXUSER). If you do not want MAS Core to update person's details (display name, title, etc.) then you can do that by enabling Inbound Setting Restrictions for the attributes you're interested in. 

------------------------------
Andrzej Więcław
Maximo Technical Consultant
AFRY
Wrocław, Poland