Mapping from Schema 1 to Schema 2
Updated:
Use-Case Name
Attribute Mapping with Schema 1 (OLEDB Technology APP) and Schema 2 (REST Application - Magento 2)
Brief Description
Two different Application has been created one being an OLEDB Technology app
and the other one is the REST based
application
MAGENTO 2. Here Schema 1
is created for the OLEDB app and its attributes created are mapped with
the attributes of the Schema 2
(Magento 2).
ACTORS
Implementers, Developers, Partners
Preconditions
Organisation Creation & Connection Creation.
Basic Flow
- Login to the APPSeCONNECT Portal and create a connection with the application for which the mapping is to be done.
- Create an OLEDB Technology App
- Create the schema and its action for the OLEDB App
- Create the connection between the two apps.
- OLEDB is a technology application so Touchpoint is required to be created.
- Now the touchpoint is created. Navigate to the Transformation section for implementing the attribute Mapping.
- The above scenario defines, that the attribute default_billing of Magento 2 is here mapped with the source attribute BPAddresses of the app OLEDB for the easy transformation of the Schema that contains the address of the Business Partner.
Post-Conditions
The user can view the successful sync of the touchpoint Customer Add for the connection OLEDB Technology App and Magento 2.
Exception Courses
The user can view the error logs in the RESYNC Bucket of the agent (Cloud and OP), if the touchpoint fails to sync for any cases.
Frequency of Use
The user can sync the touchpoint whenever required.
Assumptions
Not Applicable