Skip to content

Commit 185bac3

Browse files
author
Siddharth
authored
Apply suggestions from code review
1 parent 06bdc05 commit 185bac3

File tree

1 file changed

+2
-2
lines changed
  • articles/logic-apps/connectors

1 file changed

+2
-2
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The SAP built-in connector significantly differs from the SAP managed connector
104104

105105
* Handling empty XML elements
106106

107-
- SAP built-in connector: An empty XML element is treated as an SAP parameter with an explicit empty value or default value.
107+
- SAP built-in connector: An empty XML element is treated as an SAP parameter with an explicit empty value or default value. To omit the parameter to be sent to SAP, you can simply remove the empty element from the input payload.
108108

109109
- SAP managed connector: An empty XML element is interpreted as a missing parameter and isn't sent to the SAP function.
110110

@@ -134,7 +134,7 @@ The SAP built-in connector significantly differs from the SAP managed connector
134134
</RfcName>
135135
```
136136

137-
In the SAP RFC function call, the whitespace in the **Parameter** value is treated as an empty string ('') and is trimmed. To make sure that the call keeps whitespace exactly as provided in the payload, include the **`xml:space="preserve"`** attribute with the element, for example:
137+
In the SAP RFC function call, the whitespace in the **Parameter** value is treated as an empty string ('') and is trimmed. To make sure that the call keeps whitespace exactly as provided in the payload, include the **`xml:space="preserve"`** attribute with the element. This is to conform with W3C specification [2.10 White Space Handling](https://www.w3.org/TR/xml/#sec-white-space). For example:
138138

139139
```xml
140140
<RfcName>

0 commit comments

Comments
 (0)