What are the possible error codes for Logic Apps Data Mapper?

Question

This post lists possible errors coming from Data Mapper back end.

Answer 1

01. CopyOfMessageTypeError

Message

Function 'copy-of' cannot be used when input message type is different from output message type.

Details

This message indicates Mass Copy or Copy-of function is used when source and destination formats are different. It is typically expected to be used with XML-to-XML transform.

02. InvalidMap

Message

Cannot deserialize map, {0}.

Details

Something is wrong with the YAML file containing map definition and cannot be read for back-end processing. No XSLT will be generated in this case.

03. InvalidMapNodeName

Message

Supplied map node name '{0}' is invalid.

Details

A map is organized as a tree of mapping node (like XML schema) and there are rules regarding the name of these node names. There exists a map node in YAML that does not follow these rules. The map node name is printed in the error.

04. InvalidSelectorFragmentFullName

Message

Supplied selector fragment full name '{0}' is invalid.

Details

A fully qualified reference to a source schema node in the map is invalid. Most likely cause is hand editing of YAML file. The printed details help to identify that in schema and in in YAML file to indicate where the error has happened.

05. JsonAttributeError

Message

Attribute is not allowed for JSON selector.

Details

Attributes are specific to XML. By mistake if they are used for JSON input or output, this error is thrown.

06. JsonDefaultNamespaceError

Message

Map should not have a default namespace as JSON output requires no namespace.

Details

There exists a default namespace definition in the map YAML. Also, the output is of type JSON. There is no concept of namespaces for JSON and therefore it is an error.

07. JsonSourceNamespaceError

Message

Map should not have source namespaces definition for input '{0}'.

Details

Source namespace is applicable only when input/source message is of type XML. For any other map specs, specifying source namespace in YAML will lead to this error.

08. NodeNameError

Message

Only support node name as constant (no expression allowed).

Details

There is a map node that violates naming - looks like expressions are used like functions. Carefully examine the name of nodes for odd patterns

09. SchemaNodeNameResolutionFailed

Message

Schema node name could not be resolved in scheme file '{0}' at line number '{1}' and line position '{2}'.

Details

In the map YAML, at line# and Col# indicated by {1} and {2} there is reference to a schema node. The referred schema node cannot be found in schema file indicated by {0}

10. UnrecognizedExpression

Message

Expression could not be parsed. Invalid or unrecognized expression '{0}'.

Details

There is an invalid expression {0}. Look for this text on the right side of key/value pairs in the map YAML specification.

11. UnrecognizedExpressionPart

Message

Expression could not be parsed. Part of expression '{0}' is invalid or unrecognized after '{1}'.

Details

There is an invalid expression {0}. Look for this text on the right side of key/value pairs in the map YAML specification. The back end could make progress with part of the expression and found error at column position indicated.

12. UnrecognizedExpressionWithErrorDetail

Message

Expression could not be parsed. Invalid or unrecognized expression '{0}'. Error details: '{1}'.

Details

There is an invalid expression {0}. Look for this text on the right side of key/value pairs in the map YAML specification. There is additional information in Error details.

13. UnrecognizedFilterExpression

Message

Expression could not be parsed. Filter expression '{0}' in selector fragment '{1}' is invalid or unrecognized.

Details

This error is also related to bad expression, but specific to filter condition in a selector expression.

14. UnrecognizedFunction

Message

Function '{0}' is unrecognized or not supported.

Details

Map YAML contains a function {0} which is not supported by BE. This error isn't possible if only UX is used to create a map. When running into this error, make a note of the function name for future communication as well as check whether its use in map is intentional?

15. UnrecognizedFunctionInValue

Message

Function '{0}' is unrecognized or not supported in node's value expression.

Details

Either same as above or the use of a supported function is wrong in the context of the mapping because of data types, simple node vs collections etc.

16. TargetSchemaNotFound

Message

Internal Error: Target Schema '{0}' is not loaded.

Details

Internal issue indicating some infra issues. If a few re-tries does not resolve the issue, engineering needs to better understand the circumstances in which this error comes up.

17. UnsupportedFunctionError

Message

Unrecognized function '{0}'.

Details

Map YAML contains a function {0} which is not supported by BE. This error isn't possible if only UX is used to create a map. When running into this error, make a note of the function name for future communication as well as check whether its use in map is intentional?

18. NotImplementedStatementType

Message

Internal Error: The statement type '{0}' is not implemented and unsupported.

Details

Some unsupported constructs {0} are used in map YAML specification.

19. NotImplementedExpression

Message

Internal Error: Expression Generator failed to recognize input expression.

Details

Map YAML contains an expression other than constant, selector, variable or function. That expression type isn't supported yet.

20. NotImplementedMessageType

Message

Internal Error: The message type is not implemented.

Details

As of now, Data Mapper supports only XML and JSON message types. If any other type is specified in YAML, we will get this error. Check for typos. Unlikely to happen if UX is used.

21. FunctionParameterCountError

Message

Invalid function expression, function '{0}' accept strictly {1} parameter(s).

Details

A valid data mapper function expression {0} is used with incorrect number of arguments. {1} is the correct #of arguments.

22. IsNilError

Message

Function is-nil is only valid for XML input.

Details

If is-nil function is used for non XML, this error condition happens.

23. IsNilParameterError

Message

The only parameter of is-nil should be a selector.

Details

Function is-nil is called with inappropriate argument type.

24. IsNullError

Message

Function is-null is only valid for JSON input.

Details

If, is-null function is used for non JSON, this error condition happens.

25. UnsupportedNodeType

Message

Internal Error : Non XML node found in map object model.

Details

Internal issue indicating some infra issues. If a few re-tries do not resolve the issue, engineering needs to better understand the circumstances in which this error comes up. The minimal holistic YAML file that produces this error will be of trouble shooting aid to engineering.

26. CopyOfParameterError

Message

Function 'copy-of' can only have one selector parameter.

Details

The function named copy-of is called with inappropriate parameter type.

27. NodeNameEmptyError

Message

Empty node name is not allowed for selector.

Details

Map YAML is incorrectly formed. One or more selector fragments are empty or whitespaces. Identify patterns // or / / in YAML. Either there are issues in reading the source schema or map YAML is incorrectly authored.

28. NamespaceException

Message

Namespace prefix '{0}' is a reserved namespace prefix, which can only be used for namespace '{1}', while here it is used for namespace '{2}'.

Details

A reserved namespace is incorrectly used in the map. The error has details.

29. ExpectedKeyName

Message

Expected key name but cannot locate it.

Details

The map YAML specification has errors. One or more of the keys (in key value pairs) is mis-formed.

30. InvalidForStatement

Message

Invalid $for statement '{0}'. Error details: {1}

Details

In map YAML, there is a wrongly constructed $for statement. Error messages have details. These details in error message are useful troubleshooting aid at all levels - self-examination by user, CSS and Engineering.

31. InvalidForStatementFunctionCall

Message

"$for" statement should be a function call with 1 or 2 parameters.

Details

In map YAML there is a $for with 0 or more than 2 parameters. This is incorrect. Examine $for in your map YAML to identify the source of error.

32. InvalidForStatementParameterCount

Message

Invalid number of provided parameters: '{0}'. $for statement should have 1 or 2 parameters.

Details

Similar to above, but this time supplied count of parameters to $for is printed as part of the error message, further aiding in isolation and fixing the error.

33. InvalidForStatementCollection

Message

First parameter should be a selector.

Details

Error happens when $for is used in map YAML but the first parameter to $for isn't a selector.

34. InvalidForStatementIndex

Message

Second parameter should be a variable.

Details

Error happens when $for is used with two parameters. The optional 2nd parameter isn't of the correct type.

35. InvalidIfStatement

Message

Invalid $if statement '{0}'. Error details: {1}

Details

Error happens when $if is used in map YAML incorrectly. The message has the actual details. These details are useful trouble shooting aid at all levels.

36. InvalidIfStatementFunctionCall

Message

"$if" statement should be a function call with 1 parameter.

Details

Error happens when $if is used with incorrect number of parameters.

37. InvalidIfStatementParameterCount

Message

"$if" statement should have 1 parameter.

Details

Error happens when $if is used with incorrect number of parameters.

38. InvalidValueExpression

Message

Invalid expression in node value. Error details: {0}

Details

For a mapping node in map YAML, the node value details, to be assigned to output node, are in error. Details in error message.

39. MetadataOrRootNodeExpected

Message

Expected map metadata key name or root node mapping definition but cannot locate it.

Details

The map YAML file is incorrectly formed. If it is generated by UX, check for corruption sources.

40. NotKeyValueStructure

Message

Expected a map structure but cannot locate it.

Details

The map YAML file is incorrectly formed. If it is generated by UX, check for corruption sources.

41. StatementInRoot

Message

Root node cannot be a statement.

Details

The map YAML file is incorrectly formed. if statement is generated by UX, check for corruption sources. Error is specific to how the 1st mapping is described in YAML.

42. UnexpectedAttribute

Message

Found attribute '{0}' in map file, which is not allowed for output type other than '{1}'.

Details

Attributes are specific to XML. By mistake if they are used for JSON input or output, this error is thrown.

43. UnexpectedMetadataKeyName

Message

Unexpected map metadata key name '{0}'.

Details

Metadata section of the YAML file has unexpected contents. It’s a small section. Manual inspection will be adequate to identify the cause.

44. MultipleRootNodesInMap

Message

Multiple root nodes are not allowed in map.

Details

The map YAML is in error. The node hierarchy isn't well formed. More than one top level node is present.

45. DuplicateMetadataDefinitionInMap

Message

Duplicate map metadata key name '{0}'.

Details

Map YAML metadata section has errors. {0} appears more than once. This is not allowed.

46. InvalidYaml

Message

Invalid YAML. Unable to parse. Error: '{0}'.

Details

Error has details of what is wrong with the map YAML file. Details of error are useful troubleshooting aid for engineering and CSS.

47. SchemaNodeKeyAlreadyPresent

Message

Schema '{0}' contains multiple nodes with same key: '{1}'.

Details

XML schema related error, details in the error message. Unless this error is rectified, one must not proceed with creation of a production grade map.

48. SchemaNodeUnexpectedTypeAttribute

Message

In Schema '{0}' attribute node with key '{1}' contains attribute of unexpected type.

Details

XML schema related error, details in the error message. Unless this error is rectified, one must not proceed with creation of a production grade map.

49. InvalidSelectorFragmentIndex

Message

Invalid index {0} present in selector fragment {1}.

Details

Map YAML uses incorrectly formed selector expression. Error message details help in pinpointing the specific statement that needs to be corrected.