Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Hi Ahmed,

I noticed that you also started a thread in the appropriate API Connect group, so I'll add my response here as well to continue the conversation in this topic group.

From your description, it sounds like you're expecting the output to include a value inside the <accountId> element (123456789), but it's showing up as empty with only the attributes. If that's the case, it's likely because the text content of the element is not being explicitly set in your map policy. Can you try this?

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Wed July 02, 2025 04:39 AM
From: Ahmed Elaimy
Subject: map policy

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

------------------------------
Ahmed Elaimy
------------------------------

Hi Ahmed,

I noticed that you also started a thread in the appropriate API Connect group, so I'll add my response here as well to continue the conversation in this topic group.

From your description, it sounds like you're expecting the output to include a value inside the <accountId> element (123456789), but it's showing up as empty with only the attributes. If that's the case, it's likely because the text content of the element is not being explicitly set in your map policy. Can you try this?

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Hi Ahmed and Francis,

Actually for an xml definition, attributes are children of the element property, so although the value is a scalar type, you must specify it as an object so the map policy will traverse the definition into the children properties to pick up the attributes.

Best Regards,

Steve Linn

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Sun July 06, 2025 09:39 AM
From: Francis Cocx
Subject: map policy

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Fri July 04, 2025 08:44 AM
From: Steve Linn
Subject: map policy

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Wed July 02, 2025 04:39 AM
From: Ahmed Elaimy
Subject: map policy

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

------------------------------
Ahmed Elaimy
------------------------------

Hi Steve,

So far I was unable to set a value to the accountId element when defining it as type object in my definition. Not sure if I am doing something wrong?

If I just set it as string I am still able to add and set the attributes and value.

    accountId:      type: object      xml:        name: accountId        prefix: ns3        namespace: http://www.banqueaudi.com/ebo/psa.cmn.Identifiers      properties:        format:          type: string          enum:            - Local            - GL            - IBAN            - Other            - Unknown            - Display            - OldAccount            - OldIBAN            - FCUBSAccount          xml:            attribute: true        domiciliation:          type: string          enum:            - Local            - Domestic            - International          xml:            attribute: true        value:          type: string

<accountId format="Local" domiciliation="Local">	<value>123456789</value></accountId>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Sun July 06, 2025 12:51 PM
From: Steve Linn
Subject: map policy

Hi Ahmed and Francis,

Actually for an xml definition, attributes are children of the element property, so although the value is a scalar type, you must specify it as an object so the map policy will traverse the definition into the children properties to pick up the attributes.

Best Regards,

Steve Linn

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Sun July 06, 2025 09:39 AM
From: Francis Cocx
Subject: map policy

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Fri July 04, 2025 08:44 AM
From: Steve Linn
Subject: map policy

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Wed July 02, 2025 04:39 AM
From: Ahmed Elaimy
Subject: map policy

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

------------------------------
Ahmed Elaimy
------------------------------

Hi Francis,
  Your definition is incorrect.  XML element (definition property) accountId does not have a child property named "value".  The mapping must go directly to the accountId property.  In the case of an array, you have a child action for the create action, and you must specify $item as the set property.  You must have done that in your first attempt.  Hard to believe it has been 9 years since I wrote the map policy and I can't remember now if I put special code to traverse the definition if you had a properties property for a scalar such as a string, or if I traversed only for type object or array.  You'll need to test and verify as I don't have access to the code anymore.

Best Regards,

Steve Linn

Hi Steve,

So far I was unable to set a value to the accountId element when defining it as type object in my definition. Not sure if I am doing something wrong?

If I just set it as string I am still able to add and set the attributes and value.

    accountId:      type: object      xml:        name: accountId        prefix: ns3        namespace: http://www.banqueaudi.com/ebo/psa.cmn.Identifiers      properties:        format:          type: string          enum:            - Local            - GL            - IBAN            - Other            - Unknown            - Display            - OldAccount            - OldIBAN            - FCUBSAccount          xml:            attribute: true        domiciliation:          type: string          enum:            - Local            - Domestic            - International          xml:            attribute: true        value:          type: string

<accountId format="Local" domiciliation="Local">	<value>123456789</value></accountId>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Sun July 06, 2025 12:51 PM
From: Steve Linn
Subject: map policy

Hi Ahmed and Francis,

Actually for an xml definition, attributes are children of the element property, so although the value is a scalar type, you must specify it as an object so the map policy will traverse the definition into the children properties to pick up the attributes.

Best Regards,

Steve Linn

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Sun July 06, 2025 09:39 AM
From: Francis Cocx
Subject: map policy

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Fri July 04, 2025 08:44 AM
From: Steve Linn
Subject: map policy

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Wed July 02, 2025 04:39 AM
From: Ahmed Elaimy
Subject: map policy

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

------------------------------
Ahmed Elaimy
------------------------------

Hi Steve,

I have actually tried the following 3 ways of mapping the accountId:

• Create child named "value" underneed accountId. -> this created the element value with the accountId from the array as per example.

  • accountId format="Local" domiciliation="Local">	<value>123456789</value></accountId>

• map dirrectly to accountId using $item -> no result 
  • <accountId format="Local" domiciliation="Local"></accountId>
• make AccountId string instead of Object
  • <accountId format="Local" domiciliation="Local">123456789</accountId>

The solution you proposed just doesn't seem to map anything, which also seems to be the problem Ahmed is having.

Regards.

Hi Francis,
  Your definition is incorrect.  XML element (definition property) accountId does not have a child property named "value".  The mapping must go directly to the accountId property.  In the case of an array, you have a child action for the create action, and you must specify $item as the set property.  You must have done that in your first attempt.  Hard to believe it has been 9 years since I wrote the map policy and I can't remember now if I put special code to traverse the definition if you had a properties property for a scalar such as a string, or if I traversed only for type object or array.  You'll need to test and verify as I don't have access to the code anymore.

Best Regards,

Steve Linn

Hi Steve,

So far I was unable to set a value to the accountId element when defining it as type object in my definition. Not sure if I am doing something wrong?

If I just set it as string I am still able to add and set the attributes and value.

    accountId:      type: object      xml:        name: accountId        prefix: ns3        namespace: http://www.banqueaudi.com/ebo/psa.cmn.Identifiers      properties:        format:          type: string          enum:            - Local            - GL            - IBAN            - Other            - Unknown            - Display            - OldAccount            - OldIBAN            - FCUBSAccount          xml:            attribute: true        domiciliation:          type: string          enum:            - Local            - Domestic            - International          xml:            attribute: true        value:          type: string

<accountId format="Local" domiciliation="Local">	<value>123456789</value></accountId>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Sun July 06, 2025 12:51 PM
From: Steve Linn
Subject: map policy

Hi Ahmed and Francis,

Actually for an xml definition, attributes are children of the element property, so although the value is a scalar type, you must specify it as an object so the map policy will traverse the definition into the children properties to pick up the attributes.

Best Regards,

Steve Linn

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Sun July 06, 2025 09:39 AM
From: Francis Cocx
Subject: map policy

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

------------------------------
Francis Cocx
Integration Engineer
Rijkevorsel

Original Message:
Sent: Fri July 04, 2025 08:44 AM
From: Steve Linn
Subject: map policy

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM Retired

Original Message:
Sent: Wed July 02, 2025 04:39 AM
From: Ahmed Elaimy
Subject: map policy

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

------------------------------
Ahmed Elaimy
------------------------------

Hi Ahmed, 

Thankyou for providing the full assembly. I did a test and can confirm that the reply @Steve Linn posted is the correct way of doing this. Important to note is that for this to work the element 'accountId' needs to be defined as the correct type in the definition. I would assume as String in this case and not as an Object.

Testing this gave me the following result:

Actions:

 actions:	- set: '@format'	  from: accountId.format	- set: '@domiciliation'	  from: accountId.domiciliation	- set: $item	  from: accountId.value

TestRequest:

{    "accountId": [        {            "format": "Local",            "domiciliation": "Local",            "value": "123456789"        },        {            "format": "IBAN",            "domiciliation": "International",            "value": "LB123456789012345678901234"        },        {            "format": "GL",            "domiciliation": "Domestic",            "value": "987654321"        }    ]}

TestResponse:

<?xml version="1.0" encoding="UTF-8"?><accountIdSet>    <accountId format="Local" domiciliation="Local">123456789</accountId>    <accountId format="IBAN" domiciliation="International">LB123456789012345678901234</accountId>    <accountId format="GL" domiciliation="Domestic">987654321</accountId></accountIdSet>

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below : 

Hi Ahmed,

I keep prefacing my posts by saying I'm retired and don't have any mechanism to try this anymore, but your array child actions only map your attributes, not the value of the element itself.  I'm not sure if the UI will do this for you, but try adding to your create action in the source view

Dears , 

     appreciate your support i have this field in xml need to get the output of map policy same as below :