Skip to content

Commit 894102e

Browse files
author
Siddharth
authored
Update sap.md
1 parent 1546b43 commit 894102e

File tree

1 file changed

+12
-0
lines changed
  • articles/logic-apps/connectors

1 file changed

+12
-0
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,11 @@ The SAP built-in connector significantly differs from the SAP managed connector
9898

9999
This change prevents you from uploading multiple PSE files, which isn't supported and results in SAP connection failures. In Consumption logic app workflows, the SAP managed connector lets you specify these values through connection parameters, which allowed you to upload multiple PSE files and isn't supported, causing SAP connection failures.
100100

101+
* Changes to `guid` and `tId` Handling
102+
103+
The XML parameters for `guid` and `tId` are no longer available within the input or output XML payloads.
104+
Instead, they are now exposed as explicit parameters in the Logic App Designer's input pane and as dynamic output expressions.
105+
101106
* Difference in how empty XML elements are handled
102107

103108
- **BuiltIn SAP Connector**: An empty XML element is treated as a SAP parameter with an explicit empty value or default value.
@@ -135,6 +140,13 @@ The SAP built-in connector significantly differs from the SAP managed connector
135140
```
136141
Using `xml:space="preserve"` ensures that the connector retains the whitespace characters exactly as provided in the payload.
137142

143+
* IDoc Format Validation
144+
145+
The **Built-in SAP Connector** strictly validates the input payload against the `IDoc Format` specified in the action inputs.
146+
If there is a mismatch between the provided `IDoc Format` and the structure of the input XML IDoc, the built-in connector will throw an error.
147+
148+
In contrast, the **Managed SAP Connector** infers the IDoc format directly from the input payload, allowing more flexibility without requiring an exact format match.
149+
138150
* Difference in handling BizTalk XML group segments.
139151

140152
- **Built-in SAP Connector**: Strictly follows the schema defined by the Schema Generator. A group segment (a segment ending with `GRP`) must define its child segments only once per instance. To represent multiple items, multiple instances of the group segment should be created, each containing its own set of child segments.

0 commit comments

Comments
 (0)