<request type="EXPORT_DIMENSION" desc="Store Dimension Output">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
<parameter name="DIMENSION" value="TENPO"/> (2)
</parameters>
<contents> (3)
</contents>
</request>Exporting Dimension Members
This manual is in pilot operation.
|
Overview
This function is the same as "Exporting Members" performed via fusion_place [Manager]. In other words, you specify a dimension and export member configuration information.
How to Write a Request
Below is an example request for "Exporting Dimension Members":
| 1 | "Application" parameter |
| 2 | "Dimension" parameter |
| 3 | No request content needed |
Parameters
Specify the target application and dimension.
| Parameter | Required | Key | Description |
|---|---|---|---|
APPLICATION |
Yes |
None |
Specify the label of the target application. |
DIMENSION |
Yes |
None |
Specify the label of the dimension to export members from. |
FORMAT_VERSION |
No |
None |
Specifies the member export format for the exported members. |
Response Content
Below is an example response for "Exporting Dimension Members":
<response type="EXPORT_DIMENSION" desc="Store Dimension Output">
<returned-contents> (1)
ADD_OR_UPDATE_MEMBER, HDR, LABEL, NAME:ja, ...
ADD_OR_UPDATE_MEMBER, DTL, "S01", "Roppongi Store", ...
ADD_OR_UPDATE_MEMBER, DTL, "S02", "Daikanyama Store", ...
...
</returned-contents>
<result>
<code>SUCCESSFUL</code> (2)
<started-at time-zone="Asia/Tokyo">2016/04/28 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2016/04/28 09:50:07.827</ended-at>
<messages>
</messages>
</result>
</response>| 1 | (Returned Content) |
| 2 | (Processing Result Code) |
Returned Content
The returned content is the exported dimension member data. The format is the same as when exporting dimension members via fusion_place [Manager] (however, replacing special characters <, >, & is required). For details, refer to:
