Why does adapter schema show spaces with "_spc" or "_sp_"?
Article ID: KB0087783
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel | - |
| Not Applicable | - |
Description
Resolution:
When using IntegrationObject schema and if a field has a space in its name:
This space is represented as "_sp_" in the Designer schema(as seen in the project)
This space is represented as "_spc" in the xml string used as SiebelMessage to trigger the adapter.
The xsd at the Siebel end is created only by using this xml tag and not by the Name. But the adapter uses the field name under the column Name and that space is getting replaced by the _spc and the same is reflected in advisorydoc and in the propertysetxml.
Replacing the spaces in field names with "_spc" In the HTTP Request will make sure adapter process such fields as well.
When using IntegrationObject schema and if a field has a space in its name:
This space is represented as "_sp_" in the Designer schema(as seen in the project)
This space is represented as "_spc" in the xml string used as SiebelMessage to trigger the adapter.
The xsd at the Siebel end is created only by using this xml tag and not by the Name. But the adapter uses the field name under the column Name and that space is getting replaced by the _spc and the same is reflected in advisorydoc and in the propertysetxml.
Replacing the spaces in field names with "_spc" In the HTTP Request will make sure adapter process such fields as well.
Issue/Introduction
Why does adapter schema show spaces with "_spc" or "_sp_"?
Feedback
Yes
No
Powered by
