Offline Errors Sorted By Code
-10000
|
|
Name |
DEBUG_EXCEPTION |
Code |
-10000 |
Category |
ClientInternalError |
Message |
Debug exception: %s |
Description |
An exception occurred during debugging. The exception details will be indicated in the runtime. |
-10001
|
|
Name |
ERROR_EXECUTING_SQL_STMT |
Code |
-10001 |
Category |
ClientInternalError |
Message |
An error occurred executing SQL statement: %s. Reason: %s. |
Description |
This error occurs when an SQL statement execution fails. The statement and the cause of the failure are provided in the error context. This issue may indicate potential client SDK bugs that require further investigation by SAP. |
-10002
|
|
Name |
EXTERNAL_EXCEPTION |
Code |
-10002 |
Category |
ClientInternalError |
Message |
%s |
Description |
A client-side error, as described in the runtime details, has occurred. This error code is intended for use by the Offline OData SDK users to generate runtime application errors. |
-10005
|
|
Name |
ERROR_CONNECTING_TO_DB |
Code |
-10005 |
Category |
ClientInternalError |
Message |
An error occurred connecting to the database using connection string "%s". Reason: %s. |
Description |
This error occurs when there is a failure in connecting to the database. The connection string and the reason for the failure are filled in by the error context to provide a complete understanding of the issue at hand. |
-10006
|
|
Name |
DB_NOT_FOUND |
Code |
-10006 |
Category |
ClientInternalError |
Message |
An error occurred connecting to the database using connection string "%s". Reason: %s. |
Description |
This error occurs when the application cannot find the database file, resulting in an inability to establish a connection. |
-10010
|
|
Name |
ERROR_LOADING_EDM_METADATA |
Code |
-10010 |
Category |
ClientInternalError |
Message |
An error occurred while loading the OData metadata. |
Description |
An error occurred when attempting to load the OData metadata from the local store. This issue may indicate potential client SDK bugs that require further investigation by SAP. |
-10016
|
|
Name |
ERROR_LOADING_MAPPING |
Code |
-10016 |
Category |
ClientInternalError |
Message |
An error occurred while loading the mapping of OData metadata to database metadata. |
Description |
An error occurred during the initialization process for mapping OData metadata to database metadata. This issue may indicate potential client SDK bugs that require further investigation by SAP. |
-10021
|
|
Name |
FATAL_PARSE_ERROR |
Code |
-10021 |
Category |
ClientInternalError |
Message |
Error at URL position %lu: fatal parsing error. |
Description |
This error indicates a fatal internal JSON parsing error at the given position. This issue might be caused by malformed JSON data passed to the Offline OData client SDK. If the error occurs during the upload preprocessing stage, it may suggest potential Offline OData client SDK bugs that require further investigation by SAP. |
-10022
|
|
Name |
URL_SYNTAX_ERROR |
Code |
-10022 |
Category |
ClientInternalError |
Message |
Error at URL position %lu: "%s" was unexpected at this point. |
Description |
The client encountered unexpected data at a particular URL position. For example, an incorrectly formatted GET query to the URL '/Customers?$expand=ID ID' will result in this error. |
-10023
|
|
Name |
UNEXPECTED_EOI |
Code |
-10023 |
Category |
ClientInternalError |
Message |
Prematurely reached the end of the request URL. |
Description |
The URL parser reached the end of the request URL prematurely. For instance, an incorrectly formatted GET query to the URL '/Customers(1' will result in this error. |
-10024
|
|
Name |
ILLEGAL_TYPE_VALUE |
Code |
-10024 |
Category |
ClientInternalError |
Message |
Error at URL position %lu: "%s" is an illegal %s. |
Description |
This error occurs when an illegal value for the data type is encountered in the URL at a certain position. For instance, an incorrectly formatted GET query to the URL '/Customers(guid'12345')' will result in this error, as 12345 is an illegal value of Edm.Guid. |
-10026
|
|
Name |
EMPTY_RESOURCE_PATH |
Code |
-10026 |
Category |
InvalidInput |
Message |
The request is invalid because there is no resource path. |
Description |
This error arises when a request is made without specifying a resource path. For instance, attempting a POST request to the root URL '/' will lead to this error. |
-10027
|
|
Name |
INVALID_ENTITY_CONTAINER |
Code |
-10027 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is an invalid entity container name. |
Description |
An invalid entity container name is given at the specified URL position. For example, making a GET request to an invalid container in the URL '/Invalid.Products' will cause this error. |
-10029
|
|
Name |
INVALID_KEY_PREDICATE |
Code |
-10029 |
Category |
InvalidInput |
Message |
Error at URL position %lu: a key predicate can only follow a resource path that identifies a collection of entities. |
Description |
At the certain URL position, a key predicate follows a resource path that does not identify a collection of entities, leading to this error. An example of this is the GET request to /OrderItems(ID=1,LineID=1)/Order(1), where Order(1) is incorrectly specified. The URL should correctly identify the related entity as /OrderItems(ID=1,LineID=1)/Order. |
-10030
|
|
Name |
INVALID_UNNAMED_KEY_VALUE |
Code |
-10030 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid unnamed key value. Unnamed key values are only allowed for key predicates of entity types with a single key property. |
Description |
The error code is outdated as the URL parser has been updated to provide more descriptive error messages. |
-10031
|
|
Name |
WRONG_NUMBER_OF_KEY_VALUES |
Code |
-10031 |
Category |
InvalidInput |
Message |
Error at URL position %lu: wrong number of key values for entity type "%s.%s". |
Description |
The number of key values provided in the URL for a given entity type does not match the number of key properties defined in the metadata of the entity type. |
-10032
|
|
Name |
INVALID_KEY_PROPERTY |
Code |
-10032 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a key property of entity type "%s.%s". |
Description |
The given key property name is not the one that has been defined in the metadata of the specific entity type at the URL position. For instance, suppose the key property name is ID for the entity type of the Customers entity set, the GET request with an invalid key property name in the URL '/Customers(invalid=1)' will result in this error. |
-10033
|
|
Name |
DUPLICATE_KEY_PROPERTY |
Code |
-10033 |
Category |
InvalidInput |
Message |
Error at URL position %lu: key property "%s" appears more than once in the key predicate. |
Description |
Duplicate key properties have been detected within the given URL. For example, making a GET request to the URL 'Customers(ID=1,ID=1)' will result in this error. |
-10034
|
|
Name |
INVALID_KEY_PROPERTY_TYPE |
Code |
-10034 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid key property type for "%s": expected "%s", received "%s". |
Description |
A wrong value for the key property is received at a certain URL position. Expected data type and the actual value received are listed in the error message. For instance, if the data type of the ID property is Edm.Int64, making a GET request with an unexpected string value for the ID property in the URL \"Customers(ID='abc')\" will trigger this error. |
-10035
|
|
Name |
INVALID_NULL_IN_KEY_PREDICATE |
Code |
-10035 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid null literal in a key predicate. |
Description |
Invalid null literal is found in a key predicate at the URL position. For instance, making a GET request to the URL '/Customers(null)' will result in this error. |
-10036
|
|
Name |
INVALID_PROPERTY |
Code |
-10036 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a property of "%s.%s". |
Description |
If an incorrect property name is used in either the GET filter query 'Customers?$filter=invalidName eq 1' or in the POST request payload, this error will occur because the given property name is not part of the target entity type. |
-10037
|
|
Name |
INVALID_EMPTY_PAREN |
Code |
-10037 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "()" is invalid for this path segment. |
Description |
Empty parenthesis "()" is invalid for the path segment at the given URL position. The GET request to the URL '/Customers(1)/FirstName()' is an example that will result in this error. |
-10038
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_PROP |
Code |
-10038 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following a property. |
Description |
For example, making a GET request to the URL '/Customers(1)/ID/test' which contains invalid '/test' path segment following the ID property will lead to this error. |
-10039
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_E_SET |
Code |
-10039 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following an entity set. |
Description |
For instance, making a GET request to the URL '/Customers/$value' will cause the error because $value is not a valid path segment for the Customers entity set. |
-10047
|
|
Name |
ERROR_SETTING_PARAMETER |
Code |
-10047 |
Category |
ClientInternalError |
Message |
An error occurred while setting a parameter with %s value in a prepared statement. |
Description |
An internal client error occurred while configuring the parameters for an SQL prepared statement. The error message suggests potential issues within the client SDK. If this error persists, please contact SAP. |
-10048
|
|
Name |
DUPLICATE_QUERY_OPTION |
Code |
-10048 |
Category |
InvalidInput |
Message |
Error at URL position %lu: system query option "%s" is used more than once in the URL. |
Description |
An example GET query that will result in this error is making a GET request with the $top query option used twice in the URL, such as '/Customers?$top=10&$top=10'. |
-10049
|
|
Name |
NOT_POSITIVE_TOP |
Code |
-10049 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the value associated with $top must be positive. |
Description |
The value associated with $top should be positive, but a violation is detected at the URL position. For instance, the negative value for $top in the URL '/Customers?$top=-10' will cause the error. |
-10050
|
|
Name |
NEGATIVE_SKIP |
Code |
-10050 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the value associated with $skip is negative. |
Description |
The value associated with $skip cannot be negative, but a negative value is found at the URL position. For instance, setting $skip to a negative value in the URL '/Customers?$skip=-1' will cause the error. |
-10051
|
|
Name |
ORDER_BY_MUST_END_WITH_PROPERTY |
Code |
-10051 |
Category |
InvalidInput |
Message |
Error at URL position %lu: $orderby expressions must end with a simple property. |
Description |
The $orderby expressions must end with a primitive property. The attempt to sort results by complex properties or collection properties would be considered a violation. |
-10054
|
|
Name |
ERROR_LOADING_DB_METADATA |
Code |
-10054 |
Category |
ClientInternalError |
Message |
An error occurred while loading the database metadata. |
Description |
A client internal error occurred during the initialization the database metadata. This issue may indicate potential Offline OData client SDK bugs that require further investigation by SAP. |
-10055
|
|
Name |
STORE_ALREADY_OPEN |
Code |
-10055 |
Category |
PreconditionFailed |
Message |
Cannot open the store because it is already open. |
Description |
The error message indicates an attempt to open a store that has already been opened. |
-10056
|
|
Name |
STORE_PREVIOUSLY_CLOSED |
Code |
-10056 |
Category |
PreconditionFailed |
Message |
Cannot open the store because it has been closed. |
Description |
The error message, applicable only to the legacy SMP SDK, indicates that the store has already been closed, and the store object in memory has been freed. To open the store again, it's necessary to allocate a new store object. |
-10058
|
|
Name |
STORE_NOT_OPEN |
Code |
-10058 |
Category |
PreconditionFailed |
Message |
Cannot perform the requested operation because the store is not open. |
Description |
Attempting to make Offline OData queries on a local store that hasn't been opened will result in the error. |
-10061
|
|
Name |
ERROR_EXPANDING_DEPLOY_FILE |
Code |
-10061 |
Category |
ClientInternalError |
Message |
An error occurred while expanding the deploy file received from the server. Reason: %s. |
Description |
The UltraLite client internal error states that the operation to expand the deployment on local devices has failed. Possible causes include insufficient storage space and inadequate permissions. |
-10062
|
|
Name |
ERROR_INITIALIZING_STORE |
Code |
-10062 |
Category |
ClientInternalError |
Message |
An error occurred while initializing the store. |
Description |
An unexpected runtime error occurred, resulting in the failure of the store open operation. If this issue persists despite manual retries, contact SAP for assistance. |
-10063
|
|
Name |
UNSUPPORTED_KEY_WORD |
Code |
-10063 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a supported keyword. |
Description |
An unsupported keyword is given at the named URL position. For example, in the GET query to the URL 'Customers(ID=NaN)', the keyword NaN is not supported as the data type for the ID property is EDM.Int64. |
-10064
|
|
Name |
UNABLE_TO_DELETE_DB |
Code |
-10064 |
Category |
ClientInternalError |
Message |
The database file located at "%s" could not be deleted. |
Description |
The database file at a certain location could not be deleted. This error code is deprecated and not used. |
-10067
|
|
Name |
COULD_NOT_CREATE_DB |
Code |
-10067 |
Category |
ClientInternalError |
Message |
Could not create the store. Reason: %s. |
Description |
The client database creation failed due to the cause indicated in the context. Possible causes could be insufficient storage space or inadequate permissions. |
-10069
|
|
Name |
INVALID_PROPERTY_VALUE_TYPE |
Code |
-10069 |
Category |
InvalidInput |
Message |
An invalid value type for property "%s" was provided. A "%s" was expected. |
Description |
The error indicates that in the payload of the modification request, the supplied value for a property does not match the expected data type of the property. This error code applies exclusively to the legacy SMP SDK. |
-10070
|
|
Name |
INVALID_USE_OF_EXPAND |
Code |
-10070 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $expand system query option can only be used when retrieving an entity set or entity type. |
Description |
For example, the error will arise when making a GET request to the URL '/Customers(101)/ID?$expand=Orders', as the expansion of the Orders navigation property is not applicable to the ID property. |
-10071
|
|
Name |
INVALID_NAVIGATION_PROPERTY |
Code |
-10071 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a navigation property of "%s.%s". |
Description |
The word given at the named URL position is not a navigation property of the stated entity. For instance, making a GET query to the URL 'Customers?$expand=null' will result in the error as the name of the provided navigation property is invalid for the target entity type. |
-10072
|
|
Name |
INVALID_USE_OF_SELECT |
Code |
-10072 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $select system query option can only be used when retrieving an entity set, entity type, or complex type. |
Description |
For instance, making a GET query to the URL '/Customers(1)/ID?$select=Surname' will result in the error as the use of the $select query option is not permitted when retrieving an individual ID property. |
-10073
|
|
Name |
SELECT_OF_NON_EXPANDED_ITEM |
Code |
-10073 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is selected but is not an expanded navigation property of "%s.%s". |
Description |
The error occurs when a selected string does not correlate with an expanded navigation property, meaning the select is applied to navigation property that has not been expanded. For instance, making the GET query to the URL 'Customers(192)?$select=Orders/*' will result in the error as the Orders navigation is selected but is missing from the expand query option. |
-10074
|
|
Name |
FOLLOWED_PROPERTY_IN_SELECT |
Code |
-10074 |
Category |
InvalidInput |
Message |
Error at URL position %lu: a simple property cannot be followed by a path expression in a $select clause. |
Description |
For example, making a GET query to the URL 'Customers(1001)?$select=ID/value' will result in the error due to the unexpected path segment '/value' following the primitive ID property. |
-10075
|
|
Name |
INVALID_USE_OF_TOP |
Code |
-10075 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $top system query option can only be used when retrieving a collection. |
Description |
The error indicates that the $top query option is used in a request that does not retrieve a collection. For example, the GET query to the URL 'Customers(1)?$top=1' that retrieves an individual entity type instance with $top will lead to the error. |
-10076
|
|
Name |
INVALID_USE_OF_SKIP |
Code |
-10076 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $skip system query option can only be used when retrieving a collection. |
Description |
The error aries when the $skip query option is used in a request that does not retrieve a collection. For example, the GET query to the URL 'Customers(1)?$skip=1' that retrieves an individual entity type instance with $skip will lead to the error. |
-10077
|
|
Name |
ORDER_BY_OF_NON_EXPANDED_ITEM |
Code |
-10077 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" appears in $orderby but is not an expanded navigation property of "%s.%s". |
Description |
The error arises when using a navigation property for the $orderby query option, which is not included in the $expand query option. For example, executing a GET request to the URL 'Customers(1)?$orderby=Orders/ID' will result in the error because the Orders navigation property has not been expanded in the $expand query option yet. |
-10078
|
|
Name |
INVALID_USE_OF_ORDER_BY |
Code |
-10078 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $orderby system query option can only be used when retrieving a collection or when retrieving a single entity with an $expand. |
Description |
The error arises when the $orderby system query is misused. It should only be used for retrieving a collection or when expanding the navigation properties of a single entity using the $expand query. For example, executing a GET request to the URL 'Customers(1)?$orderby=ID' will result in the error because only a single entity instance is being retrieved and the sort operation is not applicable. |
-10081
|
|
Name |
ERROR_STMT_NOT_PREPARED |
Code |
-10081 |
Category |
ClientInternalError |
Message |
An error occurred while attempting to execute the following SQL statement which was not prepared: "%s". |
Description |
Indicates that an error occurred while attempting to execute an SQL statement that was not prepared leading to malfunction. The error message suggests potential issues within the client SDK. If this error persists, please contact SAP. |
-10082
|
|
Name |
INVALID_USE_OF_FILTER |
Code |
-10082 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $filter system query option can only be used when retrieving a collection. |
Description |
This error is triggered when a $filter system query option is used out of context. It should only be employed during data collection. For example, making a GET request to the URL 'Customers(1)?$filter=ID eq 1' will result in the error. |
-10083
|
|
Name |
FILTER_MUST_BE_BOOLEAN |
Code |
-10083 |
Category |
InvalidInput |
Message |
The $filter system query option must evaluate to a Boolean value. |
Description |
The error denotes that the $filter system query option did not result in a Boolean value, which it should. For example, making a GET request to the URL 'Customers?$filter=ID add 100' will result in the error. |
-10084
|
|
Name |
INVALID_ARITHMETIC_TYPE |
Code |
-10084 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not an arithmetic type. |
Description |
The error highlights that a particular string is not an arithmetic type, though it needs to be. For example, the GET query to the URL \"/Customers?$filter=-'string'\" will lead to the error. |
-10085
|
|
Name |
TYPES_NOT_PROMOTABLE |
Code |
-10085 |
Category |
InvalidInput |
Message |
There is no automatic promotion of EDM types "%s" and "%s". |
Description |
This error occurs when automatic promotion of EDM data types fails in the query URL. The client SDK has been designed to auto promote for the arithmetic data types in the filter query and the promotion error should not happen under normal circustance. If this error occurs unexpectedly, it could signal potential client SDK bugs necessitating further investigation from SAP. |
-10086
|
|
Name |
GENERIC_FILTER_ERROR |
Code |
-10086 |
Category |
InvalidInput |
Message |
Error at URL position %lu: %s. |
Description |
This error signifies an unknown issue with the filter query located in the specified URL position. The error message implies possible client SDK problems. If this error persists, please contact SAP. |
-10087
|
|
Name |
TYPES_NOT_COMPARABLE |
Code |
-10087 |
Category |
InvalidInput |
Message |
Error at URL position %lu: EDM types "%s" and "%s" are not comparable. |
Description |
This error signifies that the two data values in the filter query URL are of different types and cannot be compared. For example, requesting a GET query to 'Customers?$filter=ID gt true', which attempts to compare an integer value with a Boolean value, will lead to this error. |
-10088
|
|
Name |
BOOLEAN_RELATION_OP_ERROR |
Code |
-10088 |
Category |
InvalidInput |
Message |
Error at URL position %lu: Edm.Boolean types are not comparable using operator "%s". |
Description |
This error indicates that comparing a Boolean data type with the given operator is not supported. For example, the filter query 'Customers?$filter=true le ( ID eq 1 )' will result in the error. |
-10089
|
|
Name |
INVALID_BOOLEAN_TYPE |
Code |
-10089 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a Boolean type. |
Description |
This error shows that a Boolean value is expected at the given URL position but a non-Boolean value is provided instead. For example, make the filter query 'Customers?$filter=not ID' will result in the error as the ID property is an integer, not a Boolean. |
-10090
|
|
Name |
INVALID_EDM_TYPE_NAME |
Code |
-10090 |
Category |
InvalidInput |
Message |
"%s" is not a valid EDM type. |
Description |
The error shows that the specified EDM type isn't currently supported in the Offline OData client SDK. This error indicates a limitation of the client SDK and further development effort is required from SAP to support the new data type. |
-10091
|
|
Name |
UNSUPPORTED_METHOD_CALL |
Code |
-10091 |
Category |
NotSupported |
Message |
Error at URL position %lu: "%s" is not a supported method. |
Description |
This error occurs when an unsupported method is used at the given URL position. For instance, making a GET query to the URL '/Customers?$filter=isof(Customer)' will result in the error as the isof function is currently not supported by the Offline OData client SDK. |
-10092
|
|
Name |
UNKNOWN_METHOD_CALL |
Code |
-10092 |
Category |
ClientInternalError |
Message |
Error at URL position %lu: "%s" is an unknown method call. |
Description |
The error refers to an error where an unknown method call is used. For example, making a GET query with the unkown method hello in the URL '/Customers?$filter=hello(ID)' will result in this error. |
-10093
|
|
Name |
INVALID_PARAMETER_TYPE |
Code |
-10093 |
Category |
InvalidInput |
Message |
Error at URL position %lu: expected a parameter that evaluates to "%s". |
Description |
The error arises when the expected parameters that should evaluate to a specified type are not satisfied, indicating that the provided parameters for the function call in the URL do not match the signature of the function. For example, making a GET query to the URL '/Customers?$filter=cast(ID, 1)' will result in the error as the parameters for the cast function are not correctly specified. |
-10094
|
|
Name |
INVALID_PARAMETER_COUNT |
Code |
-10094 |
Category |
InvalidInput |
Message |
Error at URL position %lu: method "%s" does not take %lu parameters. |
Description |
The error indicates that the number of parameters provided in the URL does not match the number of parameters expected for this method. For example, making a GET query to the URL '/Customers?$filter=round()' will result in the error as the number of parameters for the round function is not correctly provided. |
-10095
|
|
Name |
CAST_TO_BOOLEAN |
Code |
-10095 |
Category |
InvalidInput |
Message |
Error at URL position %lu: cast to Edm.Boolean is not supported. |
Description |
The error occurs when there is an unsuccessful attempt to cast a given value to Edm.Boolean. For example, making a GET request to the URL \"/Customers?$filter=cast(ID,'Edm.Boolean')\" will result in the error as casting an integer to Boolean is not supported. |
-10096
|
|
Name |
INVALID_MEMBER_EXPRESSION_END |
Code |
-10096 |
Category |
InvalidInput |
Message |
Error at URL position %lu: a member expression in $filter must end with a simple property. |
Description |
The error occurs when an expression member in $filter is not terminated by a simple property. For example, making a filter query to the URL '/Customers?$filter=1 eq Orders' will lead to the error as the filter terminates with a navigation property. |
-10097
|
|
Name |
INVALID_NAV_PROP_MULTIPLICITY |
Code |
-10097 |
Category |
InvalidInput |
Message |
Error at URL position %lu: navigation property "%s" of "%s.%s" cannot be used as a member expression in $filter because its end cardinality is *. |
Description |
This error arises when a navigation property with the cardinality of many is used as a member expression in $filter, which is not permissible. For instance, making a filter query to the URL '/Customers?$filter=1 eq Orders/ID' will result in the error as the Orders navigation property is a collection. In the OData specification, the all and any lambda operators can be used to filter a navigation property that identifies a collection. |
-10098
|
|
Name |
INVALID_CAST_EDM_TYPE |
Code |
-10098 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is an invalid EDM type. |
Description |
The error occurs when the actual parameters provided do not match the expected parameters for an Entity Data Model type name. For example, making a GET query to the URL '/Customers?$filter=cast(ID, 'Edm.Int128') gt 100' will result in the error as the Edm.Int128 is not a valid EDM type. The desired EDM type name should be Edm.Int64. |
-10099
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_C_TYPE |
Code |
-10099 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following a complex type property. |
Description |
The error occurs when an incorrect path segment follows a complex property in the request URL. For example, requesting the URL '/Customers(1001)/Address/$ref' will result in the error because of the unexpected segment following the Address complex property. |
-10100
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_E_TYPE |
Code |
-10100 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following an entity type. |
Description |
The error appears when an incorrect path segment follows an entity type in the request URL. For example, requesting the $value of a non-media entity, such as '/Customers(1001)/$value', will lead to the error. |
-10101
|
|
Name |
NO_METADATA_DOC |
Code |
-10101 |
Category |
ClientInternalError |
Message |
The metadata document could not be loaded. |
Description |
The error message describes an error that the metadata document does not exist in the client database. This issue should typically not occur under regular circumstances. If this error persists, contact SAP. |
-10103
|
|
Name |
SPECIFIED_ENTITY_KEY_EXISTS |
Code |
-10103 |
Category |
NotFound |
Message |
The specified key for the new entity is a duplicate of an existing entity. |
Description |
The error message indicates that during a POST request to create a new entity, an existing key property value is being used in the payload. |
-10104
|
|
Name |
ERROR_COMMITTING_DB_TRANSACTION |
Code |
-10104 |
Category |
ClientInternalError |
Message |
An error occurred while committing a database transaction. Reason: %s. |
Description |
The error occurs when there is an error while saving changes to the database. The detailed reason will be specified in the runtime details. The error message suggests potential issues within the client SDK. If this error persists, please contact SAP. |
-10105
|
|
Name |
ERROR_GENERATING_ENTITY_ID |
Code |
-10105 |
Category |
ClientInternalError |
Message |
An error occurred while generating a local entity ID value. |
Description |
The error indicates there is a problem with the client device while generating a new UUID for a newly created local entity. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10106
|
|
Name |
INVALID_LINK_ADDRESS |
Code |
-10106 |
Category |
InvalidInput |
Message |
Invalid link address: "%s". |
Description |
The error message indicates that the link request failed because the specified target of the link is invalid. For instance, a POST request to link a Customer entity with the Orders entity set will lead to this error. |
-10107
|
|
Name |
ERROR_UPDATE_ENTITY_NOT_EXIST |
Code |
-10107 |
Category |
NotFound |
Message |
The update entity request failed because the provided entity does not exist. |
Description |
This error occurs when an attempt is made to modify the stream property of an entity, but the entity does not exist in the client database. |
-10109
|
|
Name |
ERROR_UPDATE_STREAM_NOT_EXIST |
Code |
-10109 |
Category |
NotFound |
Message |
The update media stream request failed because the provided media stream does not exist. |
Description |
This error occurs when an attempt is made to update the stream property of an entity, but the media stream has not yet been downloaded to the client database. |
-10110
|
|
Name |
NO_SERVICE_DOC |
Code |
-10110 |
Category |
ClientInternalError |
Message |
The service document could not be loaded. |
Description |
The error describes the issue that the service document is missing in the client database. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10111
|
|
Name |
FATAL_INTERNAL_ERROR |
Code |
-10111 |
Category |
ClientInternalError |
Message |
A fatal internal error has occurred. |
Description |
This error indicates a critical internal malfunction within the client application. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10119
|
|
Name |
ERROR_UPDATE_ENTITY_WRONG_TYPE |
Code |
-10119 |
Category |
InvalidInput |
Message |
The modify entity request failed because the provided entity was not the right type for the entity set. |
Description |
This error is triggered when an attempt to modify an entity fails because the type of entity supplied does not match the type required for the specific entity set. This error might be due to unintended programming mistakes or possibly a bug in the client SDK. In the event of a suspected SDK issue, contact SAP for support. |
-10120
|
|
Name |
ERROR_ADDING_LINK_WRONG_TYPE |
Code |
-10120 |
Category |
InvalidInput |
Message |
The update link request failed because an entity of type "%s.%s" was expected, but an entity of type "%s.%s" was provided. |
Description |
This error occurs when an update link request fails because the type of entity provided does not match the expected entity type as specified in the error message. For example, in a POST request to link a Customer entity with an Order entity, providing an unexpected edit link of a Product entity in the payload will result in this error. |
-10124
|
|
Name |
INVALID_USE_OF_INLINE_COUNT |
Code |
-10124 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $inlinecount/$count system query option can only be used when retrieving a collection. |
Description |
This error indicates misuse of the $inlinecount/$count system query option. This option can only be used during the retrieval of a collection. For example, making a GET request to the URL '/Customers(192)?$count=true', which uses the $count system query for a single entity instance, will result in the error. |
-10125
|
|
Name |
CANNOT_DELETE_PRIMARY_ENTITY |
Code |
-10125 |
Category |
InvalidInput |
Message |
Cannot delete this entity instance because another entity instance is dependent on it. |
Description |
This error is generated when an attempt to delete an entity instance is denied because another entity instance relies on it. It is recommended to investigate the referential constraint associated with the entity type in the metadata. |
-10127
|
|
Name |
ERROR_GENERATING_E_TAG |
Code |
-10127 |
Category |
ClientInternalError |
Message |
An error occurred while generating an ETag value. |
Description |
The client experienced a temporary issue while generating the ETag for the updated entity. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10128
|
|
Name |
ERROR_E_TAGS_DIFFER |
Code |
-10128 |
Category |
InvalidInput |
Message |
The request on an entity failed because its ETag did not match the request's conditions. |
Description |
This error is raised when a request on an entity is unsuccessful due to a mismatch of the ETag. A quick note: using the ETag '*' for an update request can help resolve the ETag mismatch issue for most cases. |
-10129
|
|
Name |
LINK_SOURCE_NOT_EXIST |
Code |
-10129 |
Category |
NotFound |
Message |
The modify link request failed because the source entity does not exist. |
Description |
This error results from a failed link update request when the source entity targeted for the modification doesn't exist in the local database. |
-10130
|
|
Name |
LINK_LINKED_NOT_EXIST |
Code |
-10130 |
Category |
NotFound |
Message |
The modify link request failed because the linked entity does not exist. |
Description |
This is another side of the error -10129, it emerges when the modify link request failed because the linked entity involved doesn't exist. |
-10131
|
|
Name |
MODIFY_LINK_VIOLATES_CARDINALITY |
Code |
-10131 |
Category |
InvalidInput |
Message |
A modify link request failed because the modification violated the cardinality of the relationship. |
Description |
This error occurs when a modify link request has failed due to a rule violation related to the cardinality of the relationship. It is advisable to review the metadata for the comprehensive definition of these relationships. |
-10132
|
|
Name |
INVALID_DOWNLOAD_SUBSET |
Code |
-10132 |
Category |
InvalidInput |
Message |
The provided download subset string is invalid. |
Description |
The errors indicates that the string included in the download subset is a not valid defining query name. The refresh subset must contain only valid defining query names that have been previously added as defining queries. |
-10133
|
|
Name |
DEFINING_QUERY_NOT_FOUND |
Code |
-10133 |
Category |
InvalidInput |
Message |
A defining query with name "%s" does not exist. |
Description |
The error indicates that the provided defining query name in the download subset cannot be found in the local store. For the partial download, the download subset must contain only defining query names that have been successfully added as defining queries. |
-10134
|
|
Name |
INVALID_DEFINING_QUERY |
Code |
-10134 |
Category |
InvalidInput |
Message |
An invalid defining query was provided. Request name: "%s". Request value: "%s". |
Description |
This error happens when an invalid defining query is provided. The defining query name and defining query value are detailed in the error message. The defining query name should not be empty and it must not contain the comma character. |
-10135
|
|
Name |
DEFINING_QUERY_NAME_TOO_LONG |
Code |
-10135 |
Category |
InvalidInput |
Message |
A name provided for a defining query exceeded the maximum allowable length of %s: "%s". |
Description |
This error occurs when the name provided for a defining query exceeds the maximum allowable length. The exceeded length is specified in the error message. For Offline OData, the defining query name length should not exceed 128 characters. |
-10136
|
|
Name |
INVALID_ENTITY_EXISTS_PARAMETER |
Code |
-10136 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.entityexists expects a member expression that consists of navigation properties. |
Description |
The error indicates that the parameter for the sap.entityexists function is invalid as it is expecting a navigation property as the parameter. For example, the GET query to the URL '/Customers?$filter=sap.entityexists(ID)' will result in the error as the ID key property is not a expected navigation property for the sap.entityexists function. |
-10137
|
|
Name |
SHIM_STORE_OPTIONS_NOT_PROVIDED |
Code |
-10137 |
Category |
InvalidInput |
Message |
Error opening the store. No store options were provided. |
Description |
A configuration error that arises when attempting to open the store without specifying store options. If this error occurs unexpectedly, it could signal potential programming errors in the client application. |
-10138
|
|
Name |
MISSING_SERVICE_ROOT |
Code |
-10138 |
Category |
InvalidInput |
Message |
Error opening the store. No service root was provided. |
Description |
This error occurs when there is an attempt to open the store without providing a service root. A valid service root URL is mandatory for the client application to initialize the store properly. |
-10139
|
|
Name |
INVALID_PAGE_SIZE |
Code |
-10139 |
Category |
InvalidInput |
Message |
Error opening the store. The page size is not valid. |
Description |
This error occurs when a negative page size was specified as the parameter when opening the store. |
-10141
|
|
Name |
MISSING_USERNAME |
Code |
-10141 |
Category |
InvalidInput |
Message |
Error opening the store. A password was provided without also providing a username. |
Description |
The legacy username and password parameters are designed for use in basic authentication scenarios when working with the ilodata command line utility to interact with the server. These parameters must always be provided as a pair. If the password is present but the username is missing, the error will occur. |
-10142
|
|
Name |
MISSING_PASSWORD |
Code |
-10142 |
Category |
InvalidInput |
Message |
Error opening the store. A username was provided without also providing a password. |
Description |
Similar to error -10141, if the username is present but the password is missing, the error will occur. |
-10143
|
|
Name |
MISSING_STORE_NAME |
Code |
-10143 |
Category |
InvalidInput |
Message |
Error opening the store. No store name was provided. |
Description |
This error occurs when attempting to open a store with an empty store name. An empty store name is invalid for the client SDK. |
-10144
|
|
Name |
MISSING_STORE_PATH |
Code |
-10144 |
Category |
InvalidInput |
Message |
Error opening the store. No store path was provided. |
Description |
The error happens when an empty store path is provided when attempting to open a store. An empty store path is invalid for the client SDK. |
-10145
|
|
Name |
SHIM_MISSING_REQUEST |
Code |
-10145 |
Category |
InvalidInput |
Message |
The request was not provided. |
Description |
This error occurs when a null request has been supplied for execution. However, if this error arises unexpectedly, it could indicate potential application programming errors or possible client SDK bugs. In the latter case, contacting SAP support may be necessary. |
-10146
|
|
Name |
REQUEST_TYPE_NOT_SUPPORTED |
Code |
-10146 |
Category |
NotSupported |
Message |
This type of request is not supported. |
Description |
The error indicates that an unsupported or disallowed type of request has been made. For instance, deleting an entity via a navigation property of the ErrorArchive entity is not supported. A DELETE request to the URL 'ErrorArchive(1)/RequestEntity' will result in the error. |
-10147
|
|
Name |
MISSING_PAYLOAD |
Code |
-10147 |
Category |
InvalidInput |
Message |
The modification request payload is missing. |
Description |
The error occurs when no payload is supplied for an action call or a media stream modification request. |
-10148
|
|
Name |
INVALID_PAYLOAD_TYPE |
Code |
-10148 |
Category |
InvalidInput |
Message |
The provided payload is invalid or not supported for a modification request. |
Description |
The errors occur when the provided payload cannot be recognized for an entity modification request. This error code pertains to the legacy SMP SDK only. |
-10149
|
|
Name |
DROP_DB_NOT_FOUND |
Code |
-10149 |
Category |
ClientInternalError |
Message |
The store could not be dropped because it was not found. |
Description |
This error occurs when an attempt to drop a store fails because the store could not be found. For example, attempting to drop a store that has already been deleted will lead to this error. |
-10150
|
|
Name |
COULD_NOT_DROP_DB |
Code |
-10150 |
Category |
ClientInternalError |
Message |
Could not drop the store. Reason: %s. |
Description |
The error denotes an unsuccessful attempt at dropping a store, with the reason specified in the error message. One potential cause for this error could be that the store is currently open in another process. |
-10151
|
|
Name |
ERROR_COMPUTING_BASIC_AUTH |
Code |
-10151 |
Category |
ClientInternalError |
Message |
An error occurred while computing the basic authentication http header. |
Description |
The error indicates that the ilodata command line utility was unable to generate the basic authentication HTTP header with the provided user and password. The client SDK has been designed to avoid this kind of error. If this error occurs unexpectedly, it could indicate potential client SDK bugs, and engagement with SAP support may be necessary. |
-10152
|
|
Name |
INVALID_USE_OF_SKIP_TOKEN |
Code |
-10152 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the $skiptoken system query option can only be used when retrieving a collection. |
Description |
This error points to a misuse of the $skiptoken system query option. In accordance with standard practice, this option is exclusively used when retrieving a collection of data, not on a singular entity type instance. For example, the query 'Customers(101)?$skiptoken=1' incorrectly applies $skiptoken to an entity type instance, and thus triggers the error. |
-10153
|
|
Name |
INVALID_SKIP_WITH_SKIP_TOKEN |
Code |
-10153 |
Category |
InvalidInput |
Message |
Error at URL position %lu: $skip cannot be used with $skiptoken. |
Description |
This occurs when $skip and $skiptoken are used together, which is not allowed. For instance, making a GET query to the URL 'Customers?$skiptoken=1&$skip=10' will result in the error. |
-10154
|
|
Name |
INVALID_SKIP_TOKEN_ITEM_COUNT |
Code |
-10154 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the number of items in the $skiptoken list does not match what is expected. |
Description |
This error occurs when the number of items in the $skiptoken list does not match the expected count. For example, making a GET request to the URL \"/Customers?$skiptoken=X'01',X'02'\" will result in the error due to the extra item in the skip token. |
-10155
|
|
Name |
INVALID_SKIP_TOKEN_ITEM_TYPE |
Code |
-10155 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid EDM type of a $skiptoken item; expected "%s" but received "%s". |
Description |
This error indicates a mismatch in the EDM type of the value provided for the $skiptoken item: the value provided does not match the expected type. For instance, making a GET query to the URL \"/Customers?$skiptoken='invalid'\" will result in the error as the $skiptoken is expecting a value of the type Edm.Binary, not an Edm.String. |
-10156
|
|
Name |
INVALID_CUSTOM_HEADER |
Code |
-10156 |
Category |
InvalidInput |
Message |
An invalid custom header was provided. Header name: "%s". Header value: "%s". |
Description |
This error is prompted by an invalid custom header. The name and value of the invalid header are included in the error message. For example, an empty header name is considered invalid. |
-10157
|
|
Name |
SHIM_ALLOCATE_PROPS_ENT_MISSING |
Code |
-10157 |
Category |
InvalidInput |
Message |
Could not allocate entity properties because an entity was not provided. |
Description |
This application programming error occurs when a client attempts to allocate the properties of a null entity. The error pertains only to the legacy SMP SDK. |
-10158
|
|
Name |
INVALID_ENTITY_TYPE |
Code |
-10158 |
Category |
InvalidInput |
Message |
"%s" is an invalid entity type. |
Description |
This error indicates that the specified entity type is not valid. Please cross-verify the entered entity type with the metadata. |
-10159
|
|
Name |
MULTI_ENTITIES_HAVE_SAME_KEY |
Code |
-10159 |
Category |
ClientInternalError |
Message |
Multiple entities have the same key. Use a local key to disambiguate. |
Description |
The conflict arises when the client creates a local entity using a specific key, followed by downloading another entity with the same key from the back end. Use the key property to query the entity will result in the error. It is essential to use the edit link generated locally when querying an entity that was created offline to prevent conflicts due to identical keys. To resolve the conflict, undo the local changes made to that specific entity. |
-10160
|
|
Name |
ERROR_UPLOADING_REQUEST_QUEUE |
Code |
-10160 |
Category |
ClientInternalError |
Message |
An error occurred while uploading the queued requests. |
Description |
This is a system error that occurs during the upload of queued requests; it disrupts the upload process. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
-10161
|
|
Name |
ERROR_UPLOAD_ALREADY_IN_PROGRESS |
Code |
-10161 |
Category |
PreconditionFailed |
Message |
Another thread is already uploading the request queue. |
Description |
This error indicates that another thread is already uploading the request queue, thus the current operation can't proceed. |
-10163
|
|
Name |
UPDATE_ENTITY_DENIED |
Code |
-10163 |
Category |
InvalidInput |
Message |
Permission to update "%s" denied. |
Description |
The error indicates that the client is trying to modify read-only entities. For example, updating an existing ErrorArchive entity is not permitted. |
-10164
|
|
Name |
ERROR_EXECUTING_REQUEST |
Code |
-10164 |
Category |
ClientInternalError |
Message |
An error occurred while executing a request. |
Description |
The error message indicates that an internal client-side issue occurred during the execution of a request. This error should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10165
|
|
Name |
METHOD_NOT_PROVIDED |
Code |
-10165 |
Category |
InvalidInput |
Message |
The request method was not provided. |
Description |
This error typically occurs when there is an absence of the requisite HTTP request method, such as POST, PUT, DELETE, and so on. For instance, calling a function import or action without supplying the request method will result in this error. |
-10166
|
|
Name |
INVALID_PATH_FOR_METHOD |
Code |
-10166 |
Category |
InvalidInput |
Message |
Invalid resource path for a %s request. |
Description |
The error occurs when the resource path for a specific request (method specified in error message) is invalid. An example of this error would be an unsupported POST request to a simple property of an entity type. |
-10167
|
|
Name |
WRONG_REQUEST_PAYLOAD |
Code |
-10167 |
Category |
InvalidInput |
Message |
The wrong type of payload was supplied for this request. |
Description |
This happens when an unfit type of payload is supplied for a particular request. For example, creating a new media entity without including the media stream in the payload will result in this error. |
-10168
|
|
Name |
BATCH_QUERY_OPERATION_EXPECTED |
Code |
-10168 |
Category |
InvalidInput |
Message |
The batch request failed because a non-read request was found outside of a changeset. |
Description |
For Offline OData, all modification requests in the batch must be included in the change sets, while read requests must be placed outside of the change sets. Attempting to put modification requests outside of the change sets in a batch request will result in this error. |
-10169
|
|
Name |
EMPTY_BATCH |
Code |
-10169 |
Category |
InvalidInput |
Message |
The batch request failed because it does not contain any query operations or changesets. |
Description |
This error signifies that an empty batch request has been received. A valid batch request should include at least one change set. |
-10170
|
|
Name |
EMPTY_CHANGE_SET |
Code |
-10170 |
Category |
InvalidInput |
Message |
The batch request failed because it contains an empty change set. |
Description |
This error occurs when the client identifies an empty change set in the batch request. A valid change set should include at least one modification request. |
-10171
|
|
Name |
INVALID_BATCH_OBJECT |
Code |
-10171 |
Category |
InvalidInput |
Message |
The batch request failed because it contains unrecognized batch items. |
Description |
This error from the legacy SMP SDK is raised when the batch request contains unrecognized items, indicating that the batch request was incorrectly constructed. |
-10172
|
|
Name |
INVALID_CHANGE_SET_OBJECT |
Code |
-10172 |
Category |
InvalidInput |
Message |
The batch request failed because a changeset contains unrecognized items. |
Description |
This error from the legacy SMP SDK is raised when a change set in a batch request contains unrecognizable items, indicating that the change set within the batch request was incorrectly constructed. |
-10173
|
|
Name |
INVALID_CUSTOM_COOKIE |
Code |
-10173 |
Category |
InvalidInput |
Message |
An invalid custom cookie was provided. Cookie name: "%s". Cookie value: "%s". |
Description |
This error is triggered by invalid custom cookies; the name and value are specified in the error message. For example, an empty cookie name or value could result in this error. |
-10174
|
|
Name |
MISSING_HOST |
Code |
-10174 |
Category |
InvalidInput |
Message |
Error opening the store. No host was provided. |
Description |
This error means the necessary server host information was not provided during the store opening process. |
-10175
|
|
Name |
INVALID_PORT |
Code |
-10175 |
Category |
InvalidInput |
Message |
Error opening the store. An invalid port was provided. |
Description |
The error occurs when an invalid server TCP port number is specified. For example, specifying a server HTTP port number larger than 65535 will result in this error. |
-10176
|
|
Name |
MISSING_IDENTITY_PASSWORD |
Code |
-10176 |
Category |
InvalidInput |
Message |
Error opening the store. An identity certificate was provided without also providing an identity password. |
Description |
This error occurs when a client authentication certificate is provided, but the corresponding identity password is missing. |
-10177
|
|
Name |
MISSING_IDENTITY_FILE |
Code |
-10177 |
Category |
InvalidInput |
Message |
Error opening the store. An identity password was provided without also providing an identity file. |
Description |
The error occurs when an identity password is provided, but the corresponding identity file is not present. |
-10178
|
|
Name |
IDENTITY_OVER_HTTP |
Code |
-10178 |
Category |
InvalidInput |
Message |
Error opening the store. An identity certificate cannot be used without enabling HTTPS. |
Description |
This error is thrown when an identity certificate is present without enabling HTTPS for the synchronization. |
-10179
|
|
Name |
CERTIFICATE_OVER_HTTP |
Code |
-10179 |
Category |
InvalidInput |
Message |
Error opening the store. A trusted certificate cannot be used without enabling HTTPS. |
Description |
The error occurs when a trusted certificate is used, but HTTPS has not been enabled for the synchronization. |
-10181
|
|
Name |
READ_IN_CHANGE_SET |
Code |
-10181 |
Category |
InvalidInput |
Message |
The batch request failed because it contains a read request within a changeset. |
Description |
The error indicates that the batch request includes a read request within a change set, which is not allowed. A change set can contain only modification requests, such as POST, PUT, PATCH, and DELETE. |
-10182
|
|
Name |
INVALID_MAX_PAGE_SIZE |
Code |
-10182 |
Category |
InvalidInput |
Message |
"%s" is an invalid max page size specified in the Prefer header. |
Description |
The error shows that the provided max page size in the Prefer header is incorrect. A positive integer is expected. |
-10183
|
|
Name |
CANNOT_UPDATE_KEY_PROPERTY |
Code |
-10183 |
Category |
InvalidInput |
Message |
The modify property request failed because a key property "%s" cannot be updated. |
Description |
This error happens when an attempt is made to update a key property that should remain constant. |
-10184
|
|
Name |
NULLIFYING_NON_NULL_PROPERTY |
Code |
-10184 |
Category |
InvalidInput |
Message |
Property "%s" cannot be set to null because it is not nullable. |
Description |
The error indicates that a property's value cannot be set to null since it's marked as non-nullable in the metadata. |
-10185
|
|
Name |
INVALID_GUID_VALUE |
Code |
-10185 |
Category |
InvalidInput |
Message |
The property value "%s" is not a valid GUID. |
Description |
This error is shown when a property is of the type Edm.Guid but the value provided for the property is not a valid GUID (Global Unique Identifier). |
-10186
|
|
Name |
STORE_VERSION_TOO_NEW |
Code |
-10186 |
Category |
NotSupported |
Message |
This store cannot be opened because it was created by a newer version of the software. |
Description |
This error suggests that the store was created using a newer SDK version, and the current software is attempting to access it using an older SDK version, thus the store can't be opened. Upgrading to the new SDK version resolves this issue. |
-10188
|
|
Name |
NO_E_SET_OR_E_TYPE_FOR_URL |
Code |
-10188 |
Category |
InvalidInput |
Message |
The provided URL "%s" does not resolve to an entity set or entity type. |
Description |
The error indicates that the provided URL is not a valid entity set or entit type. For instance, making a PUT request to the URL 'ErrorArchive(1)/AffectedEntity' will result in this error. |
-10190
|
|
Name |
REPLACE_DB_FAILED |
Code |
-10190 |
Category |
ClientInternalError |
Message |
Replacing the database failed. |
Description |
The error indicates a serious client-side issue occurred during the process of replacing the local database with the one downloaded from the server. If the error isn't caused by storage issues on the device, it's advised to reach out to SAP support for further assistance. |
-10191
|
|
Name |
SERVICE_ROOT_NOT_ABSOLUTE |
Code |
-10191 |
Category |
InvalidInput |
Message |
The service root must be an absolute HTTP or HTTPS URL. |
Description |
This error is shown when the service root URL is not an absolute HTTP or HTTPS URL. For instance, using the file URL like 'file://abc' as the service root will result in this error. |
-10192
|
|
Name |
REQUEST_MODE_MISSING |
Code |
-10192 |
Category |
InvalidInput |
Message |
The request mode is missing. |
Description |
The error arises when the request mode is missing. For the legacy SMP SDK, the request mode (such as Read, Create, Update, Patch or Delete) must be explicitly set for each request. |
-10193
|
|
Name |
ERROR_DELETE_LINK_NOT_EXIST |
Code |
-10193 |
Category |
NotFound |
Message |
The delete link request failed because no link exists between the provided entities. |
Description |
This error means that an attempt was made to delete a link that doesn't exist between two entities. |
-10194
|
|
Name |
INVALID_ENTITY_SET_WITH_IS_LOCAL |
Code |
-10194 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.islocal cannot be used with entity set "%s.%s" because it cannot contain local entities. |
Description |
The error indicates that the sap.islocal function is used on an internal entity set that does not support local modifications. For example, the sap.islocal function cannot be used with the ErrorArchive entity set, making a GET request to the URL '/ErrorArchive?$filter=sap.islocal()' will result in this error. |
-10195
|
|
Name |
ANDROID_CONTEXT_NOT_PROVIDED |
Code |
-10195 |
Category |
InvalidInput |
Message |
The Android Context object was not provided. |
Description |
The error happens when the Android Context object is missing for an Android application. The error code is for the legacy SMP SDK only. |
-10196
|
|
Name |
SHIM_UNKNOWN_REQUEST_OBJECT |
Code |
-10196 |
Category |
ClientInternalError |
Message |
The provided request object is of an unknown type. |
Description |
The error message is from the legacy SMP SDK, indicating that the request object submitted for execution is improperly formed, and the request type of the request object cannot be identified. |
-10197
|
|
Name |
PRODUCER_ERROR |
Code |
-10197 |
Category |
ServerSideError |
Message |
A request failed against the backend OData producer - code: "%s", error: "%s", inner error: "%s". |
Description |
The error is from the legacy SMP SDK, indicating that the uploaded request has failed from the OData backend side. |
-10198
|
|
Name |
RESOURCE_NOT_FOUND |
Code |
-10198 |
Category |
NotFound |
Message |
The requested resource could not be found. |
Description |
This error message is shown when the requested resource could not be found. For example, attempting to read a non-existent entity results in this error. |
-10199
|
|
Name |
IOS_SHIM_MISSING_STORE_DELEGATE |
Code |
-10199 |
Category |
InvalidInput |
Message |
Cannot open the store. The store delegate was not set. |
Description |
The error is from the legacy SMP SDK, indicating that the store delegate object is not properly configured before opening the store. |
-10200
|
|
Name |
JAVA_SHIM_MISSING_STORE_DELEGATE |
Code |
-10200 |
Category |
InvalidInput |
Message |
Cannot open the store. The store listener was not set. |
Description |
The error is from the legacy SMP SDK, indicating that the store listener object is not properly configured before opening the store. |
-10201
|
|
Name |
CANNOT_PUT_LOCAL_ENTITY |
Code |
-10201 |
Category |
InvalidInput |
Message |
Cannot perform a PUT against an entity with an unresolved key property. Use PATCH instead. |
Description |
The error indicates that for a locally-created entity without set key properties, a PUT operation attempting to set the key property to null is not permitted. Instead, use the PATCH operation if the key property is nullable. |
-10202
|
|
Name |
DROP_DB_IN_USE |
Code |
-10202 |
Category |
ClientInternalError |
Message |
The store could not be dropped. Ensure that the store is closed. |
Description |
The error indicates that the database could not be deleted. It is usually due to the store being currently in use or open. |
-10203
|
|
Name |
NOT_GLOBAL_INIT |
Code |
-10203 |
Category |
ClientInternalError |
Message |
The operation could not be performed because the library has not been globally initialized. |
Description |
This internal error points to an issue with the client not being initialized properly before carrying out any operations. This issue should typically not occur under regular circumstances. If this error persists, please contact SAP. |
-10209
|
|
Name |
ANDROID_CERT_STORE_ERROR |
Code |
-10209 |
Category |
InvalidInput |
Message |
There was an error opening the Android certificate store: %s. |
Description |
This is an Android specific error indicating a problem while trying to access the Android certificate store. |
-10211
|
|
Name |
REQUEST_FAILED_SEE_RESPONSE |
Code |
-10211 |
Category |
ClientInternalError |
Message |
The request failed. See the response payload for more details. |
Description |
This error is from the legacy SMP SDK, showing that the request being executed has failed, and the details of the failure are in the response for the request. |
-10212
|
|
Name |
DEEP_INSERTS_NOT_SUPPORTED |
Code |
-10212 |
Category |
NotSupported |
Message |
Deep inserts are not supported with this Offline Store. |
Description |
The error indicates that the current Offline OData store does not support these operations. Please upgrade to a newer SDK version. |
-10213
|
|
Name |
DEEP_INSERT_TO_ENTITY_SET |
Code |
-10213 |
Category |
NotSupported |
Message |
Deep inserts to entity sets are not supported. |
Description |
The error indicates that the SDK being used does not support such deep insert operations. Please upgrade to a newer SDK version. |
-10214
|
|
Name |
TOO_MANY_SYSTEM_DOWNLOADS |
Code |
-10214 |
Category |
PreconditionFailed |
Message |
The Offline Store has been requested to perform a download too many times consecutively from the server. The Offline Store is being closed automatically. |
Description |
This error message signifies that the Offline Store has been attempting too many consecutive downloads from the server, triggering an automatic closure as a safety measure. This issue should typically not occur under normal circumstances. If this error occurs constantly, please contact SAP. |
-10215
|
|
Name |
MEDIA_STREAMS_NOT_SUPPORTED |
Code |
-10215 |
Category |
NotSupported |
Message |
Media streams are not supported by the current Offline Store or the server it is communicating with. |
Description |
The error suggests that the SDK being used does not support media streams. Please upgrade to a more recent SDK version. |
-10216
|
|
Name |
GENERATED_URL_FOR_STREAM_REQUEST |
Code |
-10216 |
Category |
InvalidInput |
Message |
"%s" is a generated URL and cannot be used to register a media stream request. |
Description |
The error suggests that a URL generated by the client was incorrectly used to register a media stream defining query. The URL for the defining query should be valid and functional within the back-end OData server |
-10217
|
|
Name |
INVALID_STREAM_URL |
Code |
-10217 |
Category |
InvalidInput |
Message |
"%s" is not a media entity. A URL that references a media entity is required when registering a media stream request. |
Description |
This error occurs when an incorrect URL pointing to a non-media entity is mistakenly used as the defining query for a media stream. |
-10218
|
|
Name |
NON_MEDIA_ENTITY_IN_STREAM_REQUEST |
Code |
-10218 |
Category |
InvalidInput |
Message |
"%s.%s" is not a media entity and therefore cannot be used to register a media stream request. |
Description |
The error signifies that the provided entity type in the defining query for a media stream is not a media entity and it does not contain any stream properties. |
-10219
|
|
Name |
NO_STREAM_REQUEST |
Code |
-10219 |
Category |
InvalidInput |
Message |
"%s" is not a media stream request and therefore cannot be unregistered. |
Description |
This error signifies that the provided defining query does not represent a media stream request, and thus can't be unregistered as such. |
-10220
|
|
Name |
EXPAND_IN_STREAM_URL |
Code |
-10220 |
Category |
InvalidInput |
Message |
"%s" contains an $expand system query option and therefore cannot be registered. |
Description |
The error indicates that the $expand operator is used to retrieve related information in the provided media defining query, which makes the query unsuitable for registration. |
-10221
|
|
Name |
STREAMING_TO_INVALID_URL |
Code |
-10221 |
Category |
InvalidInput |
Message |
The provided URL is not valid for modifying a media stream. |
Description |
The error denotes that the request to modify a media stream can only be applied to an entity type that has media streams. For example, attempting to upload a stream to a non-media entity will result in this error. |
-10222
|
|
Name |
NO_INPUT_STREAM_IN_MEDIA_RESOURCE |
Code |
-10222 |
Category |
InvalidInput |
Message |
No input stream was provided in the media stream payload. |
Description |
This error is from the legacy SMP SDK and indicates that a null input stream has been provided for an UploadMedia request. |
-10223
|
|
Name |
NO_CONTENT_TYPE_IN_MEDIA_RESOURCE |
Code |
-10223 |
Category |
InvalidInput |
Message |
No content type was provided in the media stream payload. |
Description |
The error indicates that the media stream payload lacks a necessary content type, which specifies the media type of the resource. The Content-Type HTTP header is necessary for the media stream payload. |
-10224
|
|
Name |
ERROR_READING_FROM_INPUT_STREAM |
Code |
-10224 |
Category |
ClientInternalError |
Message |
Failed to read data from the input stream provided in the media stream payload: "%s". |
Description |
This error is for the legacy SMP SDK, indicating that an unexpected I/O error occurred while reading from the input stream provided for the UploadMedia request. |
-10225
|
|
Name |
MEDIA_STREAM_ALREADY_AVAILABLE |
Code |
-10225 |
Category |
InvalidInput |
Message |
The media stream for "%s" is already available in the Offline Store. |
Description |
The error indicates that there is an attempt to register a media stream defining query in the Offline Store that already exists, resulting in a duplication error. |
-10226
|
|
Name |
MEDIA_ENTITY_DOES_NOT_EXIST |
Code |
-10226 |
Category |
InvalidInput |
Message |
"%s" does not exist and therefore cannot be used to register a media stream request. |
Description |
The error indicates that there is an attempt to register a media stream defining query for an entity that does not exist, thereby causing the error. |
-10227
|
|
Name |
REQUEST_EXISTS |
Code |
-10227 |
Category |
InvalidInput |
Message |
A request with name "%s" already exists. |
Description |
The error indicates that a defining query with the given name already exists, and therefore cannot be added again. |
-10228
|
|
Name |
READING_STREAM_IN_BATCH |
Code |
-10228 |
Category |
NotSupported |
Message |
Reading a media stream in a batch request is not supported. |
Description |
The error indicates that a GET query to retrieve a media stream has been added to a batch request, which is not supported. |
-10229
|
|
Name |
INVALID_STREAM_REQUEST_NAME |
Code |
-10229 |
Category |
InvalidInput |
Message |
An empty or null media stream request name was provided. |
Description |
The error indicates an attempt to add a media stream defining query with an invalid name. An empty or null string is not a valid defining query name. |
-10230
|
|
Name |
STREAM_REQUEST_NAME_TOO_LONG |
Code |
-10230 |
Category |
InvalidInput |
Message |
A name provided for a media stream request exceeded the maximum allowable length of %s: "%s". |
Description |
The length of the defining query's name should not exceed 128 characters. |
-10231
|
|
Name |
ANDROID_STREAM_LISTENER_MISSING |
Code |
-10231 |
Category |
InvalidInput |
Message |
No listener was provided for a call to read a media stream. |
Description |
This error specifically pertains to the executeMediaDownload API within the legacy Android SMP SDK, which requires a media download listener. |
-10232
|
|
Name |
WRONG_METHOD_FOR_STREAM_READ |
Code |
-10232 |
Category |
ClientInternalError |
Message |
Media streams cannot be read using this method. |
Description |
This error is solely associated with the legacy SMP SDK, where an inappropriate method was used to read media streams. |
-10233
|
|
Name |
WRONG_METHOD_FOR_NON_STREAM_READ |
Code |
-10233 |
Category |
ClientInternalError |
Message |
Only media streams can be read using this method. |
Description |
This error is strictly tied to the legacy SMP SDK, where a method for media streams was improperly used to read non-media streams. |
-10234
|
|
Name |
REQUEST_FOR_MEDIA_STREAM_EXISTS |
Code |
-10234 |
Category |
InvalidInput |
Message |
A registered media stream request already exists for "%s". |
Description |
The error indicates that an attempt to add a media stream defining query has failed because a query with a different name to retrieve the same media stream already exists. |
-10235
|
|
Name |
UPDATE_BINDING_TO_ENTITY_SET |
Code |
-10235 |
Category |
InvalidInput |
Message |
Updating a link using entity bindings cannot target an entity set. |
Description |
The error indicates an unsuccessful attempt was made to update a link using entity bindings targeting a navigation property with the many cardinality. Updating a link using entity binding should target the navigation property with the zero or one cardinality. |
-10236
|
|
Name |
INVALID_ENTITY_SET_WITH_IS_ERROR |
Code |
-10236 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.inerrorstate cannot be used with entity set "%s.%s" because it cannot contain entities in an error state. |
Description |
The error indicates that the sap.inerrorstate function is inapplicable to internal entity sets like ErrorArchive and RequestQueue. For example, attempting to make a GET query to the URL '/ErrorArchive?$filter=sap.inerrorstate()' will result in this error. |
-10237
|
|
Name |
VALUE_EXCEEDS_MAX_LENGTH_FACET |
Code |
-10237 |
Category |
InvalidInput |
Message |
The length of the value provided for property "%s" exceeds the maximum length specified in the metadata. |
Description |
The error indicates that the value provided for a property exceeds the length limit for the property. Please check the MaxLength attribute defined in the metadata for the property. |
-10239
|
|
Name |
ROW_EXCEEDS_PAGE_SIZE |
Code |
-10239 |
Category |
ClientInternalError |
Message |
The request failed because the data exceeds the database page size. |
Description |
The error denotes that the operation that attempted to insert or update a row exceeds the database page size. For UltraLite, the default page size is 4KB. With the exception of BLOB columns, a row must fit entirely on a single database page. |
-10241
|
|
Name |
INVALID_QUERY_FOR_ARCHIVE_ENTITY |
Code |
-10241 |
Category |
InvalidInput |
Message |
Error at URL position %lu: Invalid path for accessing an entity through the ErrorArchive. |
Description |
The error indicates that an invalid request path has been detected while accessing the ErrorArchive entity set. For example, the GET request to '/ErrorArchive(1)/AffectedEntity/pk' is not supported. |
-10242
|
|
Name |
INVALID_STORE_NAME |
Code |
-10242 |
Category |
InvalidInput |
Message |
Error opening the store. An invalid store name was provided. |
Description |
For example, the store name exceeding 125 characters, and the store name containing path separators, are invalid. |
-10243
|
|
Name |
INVALID_STORE_PATH |
Code |
-10243 |
Category |
InvalidInput |
Message |
Error opening the store. An invalid store path was provided. |
Description |
This error usually refers to a structural or logical error in the path's format or syntax. For instance, providing an HTTP URL as the store path will result in this error. |
-10244
|
|
Name |
INVALID_STORE_ENCRYPTION_KEY |
Code |
-10244 |
Category |
InvalidInput |
Message |
Error opening the store. An invalid store encryption key was provided. |
Description |
The error indicates that the provided store encryption key contains invalid characters, such as a semicolon. |
-10245
|
|
Name |
UNSUPPORTED_STREAM_IN_DEEP_INSERT |
Code |
-10245 |
Category |
NotSupported |
Message |
Creating a media stream in a deep insert is not supported. |
Description |
This error indicates that an attempt to create a media stream within a deep insert has failed because such an operation is not supported. |
-10246
|
|
Name |
MODIFYING_STREAM_IN_BATCH |
Code |
-10246 |
Category |
NotSupported |
Message |
Modifying a media stream in a batch request is not supported. |
Description |
This error arises when there is an attempt to modify a media stream within a batch request using an outdated SDK. Upgrade to a newer SDK version to remove the limitation. |
-10248
|
|
Name |
SERVICE_ROOT_CHANGED |
Code |
-10248 |
Category |
PreconditionFailed |
Message |
The provided service root "%s" does not match the one used when the store was created: "%s". |
Description |
This error indicates that the client is attempting to open the store using a different service root than the one used to initialize it. Changing the service root for the store is not permitted. |
-10249
|
|
Name |
NON_N_S_STRING_CUSTOM_HEADER |
Code |
-10249 |
Category |
InvalidInput |
Message |
Only custom header/cookie values that are of type NSString are supported. |
Description |
This error occurs in the legacy SMP SDK only, indicating that an invalid value that is not of the NSString type is provided as a header value or cookie value. |
-10251
|
|
Name |
NOT_HANDLE_UNKNOWN_TYPE |
Code |
-10251 |
Category |
ClientInternalError |
Message |
Unknown "%s" response type. |
Description |
This error suggests a client internal fault that an unknown response type from lower level is detected while preparing the JSON response. This issue may indicate potential client SDK bugs that need further investigation by SAP. |
-10252
|
|
Name |
ERROR_ENCODING_JSON |
Code |
-10252 |
Category |
ClientInternalError |
Message |
An error occurred while generating the JSON body. |
Description |
This error indicates a client internal exception while producing the JSON response body. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10253
|
|
Name |
NO_E_SET_FOR_E_TYPE |
Code |
-10253 |
Category |
ClientInternalError |
Message |
No entity set could be found for entity type "%s.%s". |
Description |
This error is flagged when the client can't find any entity set that is using the given entity type. This error suggests that there is an orphaned entity type that is not associated with any entity set. |
-10254
|
|
Name |
AMBIGUOUS_E_SET_FOR_E_TYPE |
Code |
-10254 |
Category |
ClientInternalError |
Message |
The entity set for entity type "%s.%s" is ambiguous. Please specify the entity set explicitly. |
Description |
When multiple entity sets use the same entity type, it is important to specify the entity set for that entity type to prevent ambiguity. |
-10256
|
|
Name |
INVALID_STORE_PATH_SCP |
Code |
-10256 |
Category |
InvalidInput |
Message |
An invalid store path was provided. The store path must be a file URL identifying a directory. |
Description |
This error is specific to the Offline OData Cloud SDK and indicates that an invalid file URL has been provided as the store path. For instance, attempting to provide an HTTP URL as the store path will result in this error. |
-10257
|
|
Name |
INVALID_PAGE_SIZE_SCP |
Code |
-10257 |
Category |
InvalidInput |
Message |
The pageSize parameter must be greater than 0 if specified. |
Description |
This error is specific to the Offline OData Cloud SDK and indicates that a non-positive value was provided as the page size, which is invalid. |
-10259
|
|
Name |
INVALID_VALUE |
Code |
-10259 |
Category |
InvalidInput |
Message |
"%s" is an invalid value for property "%s" of entity type "%s.%s". |
Description |
This error signifies that an inappropriate value has been provided for a specific entity type's property. For example, setting the value 1024 to a property with the type Edm.Byte will result in this error. |
-10260
|
|
Name |
DATA_TYPE_NOT_SUPPORTED_SCP |
Code |
-10260 |
Category |
NotSupported |
Message |
SAP OData data type: "%s" is currently not supported in the Offline OData API. |
Description |
For instance, enumeration types that utilize non-integer values are currently unsupported in the OData 4.0 protocol. |
-10262
|
|
Name |
NO_READ_EDIT_LINK_FOR_DOWNLOAD_STREAM |
Code |
-10262 |
Category |
InvalidInput |
Message |
A read link or edit link is required for the downloadStream method. |
Description |
The error suggests that either the read link or the edit link should be provided for the DownloadStream API to identify the URL of a media stream, otherwise it will result in the error. |
-10263
|
|
Name |
NO_EDIT_LINK_FOR_UPLOAD_STREAM |
Code |
-10263 |
Category |
InvalidInput |
Message |
An edit link is required for the uploadStream method. |
Description |
The error indicates that the parameter for an uploadStream request is invalid since the edit link is not present. |
-10264
|
|
Name |
INVALID_STREAM_TYPE_FOR_UPLOAD_STREAM |
Code |
-10264 |
Category |
ClientInternalError |
Message |
The content stream passed to the uploadStream method must be a ByteStream or a CharStream. |
Description |
The error message signifies that for the present UploadStream API, it is essential to provide either a ByteStream object or a CharStream object as the media content. Failure to do so will lead to the error. |
-10265
|
|
Name |
MANDATORY_COOKIES_NOT_AVAILABLE |
Code |
-10265 |
Category |
InvalidInput |
Message |
Mandatory cookies are not available. |
Description |
This error takes place when the HTTP client in the client application is not correctly initialized, and necessary cookies for communicating with the cloud server are absent. |
-10266
|
|
Name |
INVALID_SYSTEM_QUERY_OPTION |
Code |
-10266 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a valid system query option. |
Description |
This error indicates an incorrect system query option at a specific URL position. For instance, in the GET query to the URL '/Customers?$custom=val', $custom is not a valid OData system query option. |
-10267
|
|
Name |
NO_TARGET_ENTITY_FOR_DELETE_LINK |
Code |
-10267 |
Category |
InvalidInput |
Message |
The target entity must be specified for a delete link operation when the end cardinality of the relationship is *. |
Description |
To delete the link from a source entity to a target entity for a specific navigation property, the target entity can only be omitted if the navigation property is single-valued. |
-10268
|
|
Name |
UNABLE_TO_DETERMINE_URL |
Code |
-10268 |
Category |
ClientInternalError |
Message |
Unable to determine the URL for the operation. |
Description |
The error indicates that the edit link of the requested entity can not be resolved. If this error occurs unexpectedly, it could signal potential programming errors or client SDK bugs. For the latter case please contact SAP. |
-10269
|
|
Name |
INVALID_EDM_DECIMAL |
Code |
-10269 |
Category |
ClientInternalError |
Message |
"%s" is an invalid Edm.Decimal with precision %ld and scale %ld. |
Description |
The error indicates that the provided value is not valid for the decimal property. |
-10270
|
|
Name |
DUPLICATED_NESTED_LAMBDA_VARIABLE |
Code |
-10270 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the lambda variable, "%s", is nested with a lambda operator that uses the same lambda variable name. |
Description |
This error is triggered when two lambda variables with the same name are nested within a lambda operator at a certain URL position. |
-10271
|
|
Name |
INVALID_LAMBDA_NAV_PATH |
Code |
-10271 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the navigation path that prepends a lambda operator must identify a collection. |
Description |
According to the OData specification, the all and any lambda operator applies a Boolean expression to each member of a collection. Applying these lambda operators to the navigation path identifying a singular entity instance will result in this error. |
-10272
|
|
Name |
NON_BOOLEAN_LAMBDA_EXPRESSION |
Code |
-10272 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the lambda expression does not evaluate to a Boolean value. |
Description |
According to the OData specification, the lambda expression is expected to yield a Boolean value. For instance, in the GET query to the URL '/Customers?$filter=Orders/all( d: d/Quantity add 5 )', the lambda query evaluates to an integer value instead of a Boolean and therefore will result in the error. |
-10273
|
|
Name |
INVALID_LAMBDA_VARIABLE_USE |
Code |
-10273 |
Category |
InvalidInput |
Message |
Error at URL position %lu: a lambda variable must prefix a member expression. |
Description |
The error indicates a syntax error for the lambda query in the URL. Refer to the example in the OData specification for how the lambda variable d is placed before the member expression: Orders?$filter=Items/all(d:d/Quantity gt 100) |
-10274
|
|
Name |
JSON_SYNTAX_ERROR |
Code |
-10274 |
Category |
ClientInternalError |
Message |
Error at JSON position %lu: "%s" was unexpected at this point. |
Description |
The error indicates that a client internal JSON parsing error occurred. This issue should typically not occur under normal use cases. If it happens, contact SAP support for assistance. |
-10275
|
|
Name |
FIXING_REQUEST_NOT_SUPPORTED |
Code |
-10275 |
Category |
NotSupported |
Message |
Fixing the target request is not supported by this version. |
Description |
The error denotes that in the current implementations of the client SDK, only the POST request for creating an entity and the PATCH request for updating an entity are allowed to be fixed. |
-10276
|
|
Name |
HTTP_HEADER_NOT_SUPPORTED |
Code |
-10276 |
Category |
NotSupported |
Message |
HTTP header "%s" is not supported by this version. |
Description |
The error indicates that the client SDK being used must be upgraded to a newer version to support the OfflineOData.NonMergeable header. |
-10277
|
|
Name |
READING_REQ_ENTITY_NOT_SUPPORTED |
Code |
-10277 |
Category |
NotSupported |
Message |
Reading request entity is not supported by this version. |
Description |
The error indicates that the client SDK being used must be upgraded to a newer version to support reading the RequestEntity navigation property of the ErrorArchive entity. |
-10278
|
|
Name |
INVALID_COMPLEX_TYPE |
Code |
-10278 |
Category |
ClientInternalError |
Message |
"%s" is an invalid complex type. |
Description |
The error indicates the complex type name that was provided is not defined in the metadata. |
-10279
|
|
Name |
INVALID_USE_OF_REMOVE_AFTER_UPLOAD |
Code |
-10279 |
Category |
InvalidInput |
Message |
The header OfflineOData.RemoveAfterUpload can only be used with requests that create a new entity or media stream. |
Description |
The error indicates that the HTTP header OfflineOData.RemoveAfterUpload is incorrectly used for a modification request that is not a POST request. For example, trying to set the header for an HTTP PATCH request will result in the error. |
-10280
|
|
Name |
REMOVE_AFTER_UPLOAD_NOT_SUPPORTED |
Code |
-10280 |
Category |
NotSupported |
Message |
Cannot perform the requested operation because the header OfflineOData.RemoveAfterUpload was specified but is not supported. |
Description |
The error indicates that the client SDK in use needs to be upgraded to a newer version to support the feature. |
-10281
|
|
Name |
INVALID_BIND_ON_PRINCIPAL_ENTITY |
Code |
-10281 |
Category |
InvalidInput |
Message |
Invalid bind operation performed on the principal entity "%s.%s" using navigation property "%s". Since the OData back end does not support bind operations, put the bind operation on the dependent entity so its dependent properties can be updated to create the relationship in the backend. |
Description |
The error indicates that when the OData back end does not support bind operations, attempting to perform a bind operation on the principal entity Using a navigation property that navigates to the dependent entity will result in the error. The correct method is to place the bind operation on the dependent entity so its dependent properties can be updated to establish the relationship in the back end. |
-10283
|
|
Name |
INVALID_HEADER_FORMAT |
Code |
-10283 |
Category |
InvalidInput |
Message |
The value of the OfflineOData.HeaderFormat, "%s", is invalid: %s. |
Description |
The primary use case for the OfflineOData.HeaderFormat is to specify key properties of related entities in the HTTP slug header when creating media resources. However, it's flexible enough to be utilized in other scenarios as well. The value for the OfflineOData.HeaderFormat follows the 'headerName:headerFormat' syntax. |
-10284
|
|
Name |
INVALID_HEADER_FORMAT_NOT_KEY |
Code |
-10284 |
Category |
InvalidInput |
Message |
"%s" is not a key property of "%s.%s". |
Description |
The error indicates that an invalid value is provided in the OfflineOData.HeaderFormat header. The property specified in the headerFormat section is not a key property of the target entity. |
-10285
|
|
Name |
INVALID_HEADER_FORMAT_ENTITY_NOT_FOUND |
Code |
-10285 |
Category |
InvalidInput |
Message |
"%s" does not exist. |
Description |
The error indicates that the value for the OfflineOData.HeaderFormat header is not valid as the specified entity ID does not exist. |
-10286
|
|
Name |
INVALID_HEADER_FORMAT_NOT_ENTITY |
Code |
-10286 |
Category |
InvalidInput |
Message |
"%s" does not refer to an entity. |
Description |
The error indicates that the value for the OfflineOData.HeaderFormat header is not valid as the provided value does not refer to an entity. |
-10287
|
|
Name |
INVALID_HEADER_FORMAT_FORMAT |
Code |
-10287 |
Category |
InvalidInput |
Message |
The value of the OfflineOData.HeaderFormat, "%s", is not formatted correctly. |
Description |
The error indicates that the value for the OfflineOData.HeaderFormat header is not valid due to its incorrect format. |
-10289
|
|
Name |
FAIL_TO_UPDATE_RELATIONSHIP |
Code |
-10289 |
Category |
InvalidInput |
Message |
Failed to update relationship of entity type "%s.%s" using navigation property "%s", because the operation would update the dependent entity key property "%s", which isn't allowed. |
Description |
The error indicates that when a referential constraint is defined for the relationship and the properties in the referential constraint are also primary keys of the entity, the request to update the relationship will fail if the dependent entity's key properties are modified in the request. |
-10290
|
|
Name |
FAIL_TO_REMOVE_RELATIONSHIP |
Code |
-10290 |
Category |
InvalidInput |
Message |
Failed to remove a relationship of entity type "%s.%s" using navigation property "%s", because the operation would nullify a non-nullable property "%s", which isn't allowed. |
Description |
This error indicates that a delete link request would violate the nullability constraint for that property defined in the metadata, resulting in this error. |
-10291
|
|
Name |
GET_AUTH_STREAM_PARMS_FAILURE |
Code |
-10291 |
Category |
CommunicationError |
Message |
Communication with the server failed with HTTP status code: %s, response body: %s |
Description |
The error indicates that the authentication request failed due to a communication issue between the client and server. This issue might be caused by HTTP request timeouts or session timeouts. Error status codes and response bodies can help identify the problem. |
-10292
|
|
Name |
FAILED_TO_CONNECT_TO_SERVER |
Code |
-10292 |
Category |
CommunicationError |
Message |
Failed to establish a socket connection to the server. Error description: %s |
Description |
This error arises when establishing a socket connection to the server failed. This could be due to server unavailability, network issues, proxy settings, or firewall restrictions. |
-10293
|
|
Name |
DELETING_ERROR_ARCHIVE_IN_BATCH |
Code |
-10293 |
Category |
InvalidInput |
Message |
Deleting from the ErrorArchive in a batch request is not supported. |
Description |
This error indicates that deleting from the ErrorArchive in a batch request is not supported. |
-10294
|
|
Name |
ERROR_DELETE_ENTITY_NOT_EXIST |
Code |
-10294 |
Category |
NotFound |
Message |
The delete entity request failed because the provided entity does not exist. |
Description |
The error happens when the media entity being deleted doesn't exist. |
-10295
|
|
Name |
ERROR_DELETE_STREAM_NOT_EXIST |
Code |
-10295 |
Category |
NotFound |
Message |
The delete media stream request failed because the provided media stream does not exist. |
Description |
The error indicates that the attempt to delete the stream property of a media entity failed because the media stream does not exist. |
-10296
|
|
Name |
MISSING_INFO_FOR_TRANSACTION_MERGE |
Code |
-10296 |
Category |
ClientInternalError |
Message |
Required information is missing from some requests in the request queue to perform transaction merging. Unable to perform transaction merging at this time. |
Description |
The error shows that the transaction merging is being skipped due to some unexpected internal errors. The error suggests potential data inconsistencies within the client database. If this error continues, consider clearing the local database and redoing the initial download, or contacting SAP support for assistance. |
-10297
|
|
Name |
INVALID_DEFINING_QUERY_NAME |
Code |
-10297 |
Category |
InvalidInput |
Message |
An invalid defining query name was provided. Defining query names must not be the empty string and can not include a comma character. |
Description |
The error message indicates that the name of the defining query is invalid. An empty defining query name and a defining query name containing a comma character are not valid. |
-10298
|
|
Name |
GENERATED_URL_FOR_DEFINING_QUERY |
Code |
-10298 |
Category |
InvalidInput |
Message |
"%s" is a generated URL and cannot be used as the URL for a defining query. |
Description |
The error message indicates that client-generated URLs cannot be used as defining queries. Defining queries should refer to valid back-end resources without ambiguity. |
-10299
|
|
Name |
INVALID_URL_FOR_DEFINING_QUERY |
Code |
-10299 |
Category |
InvalidInput |
Message |
"%s" is not a valid URL for a defining query. |
Description |
The error indicates that the requested URL does not identify a specific entity or entity set, thus cannot be used as a defining query. Defining queries are intended to fetch entity sets or individual entities. For example, the GET request 'Customers(101)/$links/Orders' is a valid OData query, but it is not a valid defining query since it retrieves only a single relationship. |
-10300
|
|
Name |
NO_MEDIA_STREAMS_IN_URL |
Code |
-10300 |
Category |
InvalidInput |
Message |
"%s" is not a valid defining query with automatically retrieve media streams set to true because the URL does not identify any media entities. |
Description |
The error indicates that the automatic media stream retrieval option can be enabled only for defining queries that identify media entities or entities with stream properties. |
-10301
|
|
Name |
URL_DOES_NOT_IDENTITY_SINGLE_ENTITY |
Code |
-10301 |
Category |
InvalidInput |
Message |
"%s" does not identify a single entity. |
Description |
The error indicates that the modification request failed because the request URL does not refer to a specific entity. The request URL that identifies an entity set, a count, or a simple or complex property cannot be used for a modification request. |
-10302
|
|
Name |
ILLEGAL_VALUE |
Code |
-10302 |
Category |
ClientInternalError |
Message |
Illegal value. |
Description |
The error will occur if an attempt is made to set a property value that falls outside the valid value range. |
-10303
|
|
Name |
ERROR_CANCEL_NO_DOWNLOAD |
Code |
-10303 |
Category |
NotFound |
Message |
Cannot cancel because no download is occurring. |
Description |
The error is thrown when a cancel download operation is attempted but no download is currently active. |
-10304
|
|
Name |
ERROR_CANCEL_NO_UPLOAD |
Code |
-10304 |
Category |
NotFound |
Message |
Cannot cancel because no upload is occurring. |
Description |
The error occurs when a cancel upload operation is attempted but no upload is currently active. |
-10305
|
|
Name |
ERROR_SYSTEM_REFRESH_IN_PROGRESS |
Code |
-10305 |
Category |
PreconditionFailed |
Message |
The current download cannot be cancelled because it will leave the Offline Store in an inconsistent state. |
Description |
The error indicates that the attempt to cancel an ongoing download has been rejected to prevent inconsistencies in the Offline Store. |
-10306
|
|
Name |
NON_CONTENT_ID_REFERENCE_TO_NEW_ENTITY |
Code |
-10306 |
Category |
InvalidInput |
Message |
A request in the change set uses URL "%s" to reference an entity created in the same change set. Use a Content-ID reference to reference entities created in the same change set. |
Description |
The error arises when a request in the change set references an entity ID that was created in the same changeset, instead of using a Content-ID reference. Referencing the entity ID that was generated in the same change set will result in this error. Using a Content-ID to reference entities created in the same change set is the recommended approach according to the OData specification. |
-10307
|
|
Name |
NON_CONTENT_ID_REFERENCE_TO_NEW_ENTITY_LINKS |
Code |
-10307 |
Category |
InvalidInput |
Message |
A request in the change set uses URL "%s" in a $links/$ref body to reference an entity created in the same change set. Use a Content-ID reference to reference entities created in the same change set. |
Description |
Similar to the error -10306, when making a link request that references an entity created within the same change set, the Content-ID should be used instead of the entity key for referencing the entity. |
-10308
|
|
Name |
NON_CONTENT_ID_REFERENCE_TO_NEW_ENTITY_BINDS |
Code |
-10308 |
Category |
InvalidInput |
Message |
A request in the change set uses URL "%s" in a bind to reference an entity created in the same change set. Use a Content-ID reference to reference entities created in the same change set. |
Description |
Similar to the error -10308, when binding to an entity created within the same change set, the Content-ID should be used instead of the entity key for referencing the entity. |
-10309
|
|
Name |
METADATA_NOT_LOADED |
Code |
-10309 |
Category |
ClientInternalError |
Message |
The metadata has been unloaded. Please load the metadata using loadMetadata() before trying to use the OfflineODataProvider. |
Description |
The error indicates that the metadata has been explicitly unloaded; consult the error message to ensure that it is properly loaded. |
-10310
|
|
Name |
ENTITY_SET_NOT_FOUND |
Code |
-10310 |
Category |
ClientInternalError |
Message |
Cannot find the entity set "%s". |
Description |
The error denotes that the entity set specified in the request could not be found in the metadata. |
-10311
|
|
Name |
PROPERTY_NOT_FOUND_FULL_TYPE |
Code |
-10311 |
Category |
ClientInternalError |
Message |
"%s" is not a property of "%s". |
Description |
The error indicates that the client is trying to refer to or perform an operation on a property that does not exist in the mentioned entity or complex property. One possible reason is that the metadata was changed. |
-10313
|
|
Name |
PROPERTY_NOT_FOUND_NS_TYPE |
Code |
-10313 |
Category |
ClientInternalError |
Message |
"%s" is not a property of "%s.%s". |
Description |
The error is similar to the error -10311, indicating that the referred property could not be found in the target entity type or complex type. |
-10314
|
|
Name |
SEND_STORE_FAILED |
Code |
-10314 |
Category |
CommunicationError |
Message |
Failed to send the Offline Store. Reason: (MOBILINK_COMMUNICATION_ERROR) error %ld (%s) (system code %ld). Please refer to MobiLink Communication Errors for the MobiLink error details. |
Description |
The error occurred while sending the Offline Store due to a MOBILINK_COMMUNICATION_ERROR. Please refer to MobiLink Communication Errors for the MobiLink error details. |
-10315
|
|
Name |
UPSERTED_LAST_DOWNLOAD_WITH_ERROR_ARCHIVE |
Code |
-10315 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.upsertedlastdownload cannot be used with the ErrorArchive. |
Description |
The error indicates that the sap.upsertedlastdownload function cannot be used on the internal ErrorArchive entity set. For instance, making a GET request to the URL'/ErrorArchive?$filter=sap.upsertedlastdownload()' will result in this error. |
-10316
|
|
Name |
SEND_STORE_NOT_SUPPORTED |
Code |
-10316 |
Category |
NotSupported |
Message |
Sending store is not supported. |
Description |
The error indicates that the client is utilizing an outdated SDK version that does not offer support for sending stores. It is recommended to upgrade to a more recent SDK version. |
-10317
|
|
Name |
INVALID_TIMEOUT_VALUE |
Code |
-10317 |
Category |
InvalidInput |
Message |
The timeout parameter must be greater than 0 if specified. |
Description |
The timeout parameter will be used to transmit periodic liveness packets to the server. A negative value for this parameter is not valid. Additionally, the timeout value should ideally be larger than 30 seconds to prevent an excessive number of liveness checks. |
-10318
|
|
Name |
INVALID_EDM_TYPE_TO_X_SCRIPT |
Code |
-10318 |
Category |
ClientInternalError |
Message |
%s is an invalid EDM type code to the OData core library. |
Description |
The error indicates that the given EDM type is not valid or recognized by the OData library. The recommended solution for this issue is to upgrade the client SDK to a more recent version. If this error persists, contact SAP support for assistance. |
-10319
|
|
Name |
INVALID_DATA_TYPE_FROM_X_SCRIPT |
Code |
-10319 |
Category |
ClientInternalError |
Message |
%s is an invalid data type from the OData core library. |
Description |
The data type from OData core library cannot be recognized by the Offline SDK. The recommended solution for this issue is to upgrade the client SDK to a more recent version. If this error persists, contact SAP support for assistance. |
-10320
|
|
Name |
INVALID_RESPONSE_TYPE_TO_X_SCRIPT |
Code |
-10320 |
Category |
ClientInternalError |
Message |
%s is an invalid response type to the OData core library. |
Description |
This error means the response type sent to the OData library is invalid. For example, the response of the link query 'TableA(1)/$links/TableB' is not yet supported by the OData library. |
-10321
|
|
Name |
INVALID_STORE_STATE |
Code |
-10321 |
Category |
ClientInternalError |
Message |
%s store state is not supported. |
Description |
The client's internal error suggests that the client store is in an undefined state. If restarting the application cannot fix the issue, please contact SAP. |
-10322
|
|
Name |
INVALID_REQUEST_TYPE |
Code |
-10322 |
Category |
ClientInternalError |
Message |
Request type %s is not supported. |
Description |
The error suggests that an unsupported request type was received by the client, which should not occur under normal circumstances. If this error occurs, contact SAP support for assistance. |
-10323
|
|
Name |
INVALID_MEDIA_TYPE |
Code |
-10323 |
Category |
NotSupported |
Message |
The media type is invalid. |
Description |
This error refers to an issue where the content type is not properly set for the UploadMedia requests. The content type is essential to identify the type of the stream. |
-10325
|
|
Name |
INVALID_BATCH_TYPE |
Code |
-10325 |
Category |
ClientInternalError |
Message |
Batch type is neither change set nor data query. |
Description |
This error indicates that in the batch response received by the client, the batch type is neither a change set nor a data query operation. This issue should typically not occur under normal circumstances. If it happens, contact SAP support for assistance. |
-10326
|
|
Name |
INVALID_ENTITY_OPERATION |
Code |
-10326 |
Category |
InvalidInput |
Message |
The operation of the entity must be creation, updating, or deleting. |
Description |
This error suggests that in the batch request, the performed operation on an entity is not one of the allowed options: creation, updating, or deleting. |
-10327
|
|
Name |
INVALID_LINK_OPERATION |
Code |
-10327 |
Category |
InvalidInput |
Message |
The operation of the link must be creation, updating, or deleting. |
Description |
This error indicates that in the batch request, patching and retrieval of the link is not supported. |
-10328
|
|
Name |
AUTHENTICATION_TIMEOUT |
Code |
-10328 |
Category |
CommunicationError |
Message |
The request for authenticating the user timed out. |
Description |
This error refers to a timeout occurring when making an authentication request to MobiLink within the iOS SDK. The timeout threshold is configured in the SAPURLSession.configuration.timeoutIntervalForRequest property. |
-10329
|
|
Name |
INVALID_ENTITY_SET_WITH_PENDING |
Code |
-10329 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.hasPendingChanges cannot be used with entity set "%s.%s" because it cannot contain locally modified entities. |
Description |
The error indicates that the sap.hasPendingChanges method call cannot be used on internal entity set like ErrorArchive and RequestQueue. |
-10330
|
|
Name |
INVALID_USE_OF_HAS_LOCAL_RELATIVES |
Code |
-10330 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the sap.computeHasLocalRelatives query option can only be used when retrieving an entity set or entity type. |
Description |
The sap.computeHasLocalRelatives query option can only be used when querying for an entity set or entity type, and it cannot be used when retrieving a property. |
-10331
|
|
Name |
INVALID_USE_OF_HAS_RELATIVES_WITH_PENDING_CHANGES |
Code |
-10331 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the sap.computeHasRelativesWithPendingChanges query option can only be used when retrieving an entity set or entity type. |
Description |
The sap.computeHasRelativesWithPendingChanges query option can only be used when querying for an entity set or entity type, and it cannot be used when retrieving a property. |
-10333
|
|
Name |
INVALID_STRING_TRANSACTION_ID |
Code |
-10333 |
Category |
InvalidInput |
Message |
Invalid string transaction ID. String transaction IDs must not be null/nil, the empty string, or a string consisting only of whitespace. |
Description |
It is recommended to use a non-empty and meaningful string as the transaction ID when working with transactions. Using a descriptive transaction ID can make it easier to identify and manage transactions later on. For example, you might choose to include the name of the operation being performed, a timestamp, or other relevant information in the transaction ID. This will help ensure that transactions are properly identified and tracked throughout your application. |
-10334
|
|
Name |
NO_TRANSACTION_ID_ASSOCIATED |
Code |
-10334 |
Category |
InvalidInput |
Message |
Could not determine the entity ID from the referenced entity. Ensure that the referenced entity is created with 'useGeneratedIDForTransactionID' and is added to the change set prior to the referencing request. |
Description |
The useGeneratedIDForTransactionID option must be enabled to use the generated entity ID as the transaction ID. |
-10335
|
|
Name |
TRANSACTION_ID_FROM_NEW_ENTITY |
Code |
-10335 |
Category |
InvalidInput |
Message |
Cannot reference an entity that has not been created to use its entity ID for the transaction ID unless in a change set. |
Description |
The error is caused by attempting to reference an entity that has not been created for the transaction ID. |
-10336
|
|
Name |
INVALID_REQUEST_FOR_GENERATE_TRANSACTION_ID |
Code |
-10336 |
Category |
InvalidInput |
Message |
'useGeneratedIDForTransactionID' can only be used for create requests. |
Description |
The useGeneratedIDForTransactionID option is valid only when creating an entity. Using this option for PATCH requests or DELETE requests is not supported. |
-10337
|
|
Name |
COULD_NOT_DETERMINE_ENTITY_ID_FOR_TRANSACTION_ID |
Code |
-10337 |
Category |
ClientInternalError |
Message |
Could not determine the entity ID from the referenced entity to use as a transaction ID. Use loadEntity to ensure the entity ID is loaded. |
Description |
The error indicates that attempting to use an entity ID that does not exist as the transaction ID is not supported. Please make sure that the entity exists and that the editLink is correctly loaded into the memory. |
-10338
|
|
Name |
ERROR_ERROR_ARCHIVE_DELETE_WHILE_UPLOAD_IN_PROGRESS |
Code |
-10338 |
Category |
PreconditionFailed |
Message |
Cannot delete from the ErrorArchive while another thread is uploading the request queue. |
Description |
The deletion of ErrorArchive and store uploading request are exclusive to each other. |
-10339
|
|
Name |
SYNC_FILE_OPERATION_INTERRUPTED |
Code |
-10339 |
Category |
CommunicationError |
Message |
The %s was interrupted. |
Description |
The synchronization operation, such as upload, download, or file transfer, has been interrupted or explicitly cancelled. |
-10340
|
|
Name |
SYNC_FILE_FAILED_SERVER_ERROR |
Code |
-10340 |
Category |
ServerSideError |
Message |
The %s failed due to an error on the server: %s. |
Description |
The synchronization operation, such as upload or download, failed due to issues or errors on the server. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
-10341
|
|
Name |
SYNC_FILE_FAILED_BAD_STATUS_RETRY |
Code |
-10341 |
Category |
CommunicationError |
Message |
Communication with the server failed for the %s operation with status code: %d. |
Description |
The error indicates that there was a failure in communication with the server during an upload or download operation, and the status code is provided to indicate the nature of the failure. When using a client built with the SAP Business Technology Platform cloud SDK, this type of error will automatically trigger the client to retry the failed operation. |
-10342
|
|
Name |
SYNC_FILE_FAILED_BAD_STATUS |
Code |
-10342 |
Category |
CommunicationError |
Message |
Communication with the server failed for the %s operation with status code: %d. Reason: %s. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
Description |
Similar to the error -10341, the detailed reason for failure is provided in the error message. It is not something that the client will attempt to retry. |
-10343
|
|
Name |
SYNC_FILE_FAILED_AUTH_REQUIRED |
Code |
-10343 |
Category |
CommunicationError |
Message |
Communication with the server failed for the %s operation due to invalid authentication. |
Description |
The error indicates a failure in communication with the server due to invalid authentication. The issue could be due to incorrect user credentials or timed out HTTP sessions. |
-10344
|
|
Name |
SYNC_FILE_FAILED_INVALID_CHARACTER |
Code |
-10344 |
Category |
CommunicationError |
Message |
Communication with the server failed for the %s operation due to an unexpected character in an HTTP header. Reason: %s. Please refer to MobiLink Communication Errors for the MobiLink error details. |
Description |
This error indicates a failed communication between the client and server due to an unexpected character present in an HTTP header. |
-10345
|
|
Name |
SYNC_FILE_FAILED_HOST_NOT_FOUND |
Code |
-10345 |
Category |
CommunicationError |
Message |
Communication with the server failed for the %s operation because the host could not be found. Reason: %s. Please refer to MobiLink Communication Errors for the MobiLink error details. |
Description |
This error indicates a connection failure during an upload or operation due to the inability to resolve the server's hostname, or the server responded with an HTTP 404 status code. |
-10346
|
|
Name |
SYNC_FILE_FAILED_SOCKET_CONNECT |
Code |
-10346 |
Category |
CommunicationError |
Message |
The %s failed to establish a socket connection to the server. Reason: %s. Please refer to MobiLink Communication Errors for the MobiLink error details. |
Description |
The error suggests a failed attempt to establish a socket connection with the server, potentially due to network issues. Please refer to MobiLink Communication Errors for the MobiLink error details. |
-10347
|
|
Name |
SYNC_FILE_COMMUNICATION_ERROR |
Code |
-10347 |
Category |
CommunicationError |
Message |
The %s failed. Reason: %s. Please refer to MobiLink Communication Errors for the MobiLink error details. |
Description |
This error indicates a failed operation whose details are not specifically addressed. Refer to the provided URL for more details about the error. |
-10348
|
|
Name |
SYNC_FILE_DEFAULT |
Code |
-10348 |
Category |
ClientInternalError |
Message |
The %s failed. Reason: %s. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
Description |
This error signifies a failure during the synchronization. Checking out the exact reason for the failure and the provided URL might give more insights into the error. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
-10349
|
|
Name |
SYNC_FILE_MAX_RETRY |
Code |
-10349 |
Category |
ServerSideError |
Message |
The %s operation could not complete successfully after %d attempts. The last error received was: %s. Previous errors resulting in a re-attempt are logged at the WARNING level. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
Description |
This error arises when an operation fails to complete successfully after multiple attempts. Please refer to the Synchronization Errors Troubleshooting Guide to troubleshoot synchronization errors. |
-10350
|
|
Name |
CREATE_READONLY_ENTITY_INSTANCE |
Code |
-10350 |
Category |
InvalidInput |
Message |
Could not create/update an entity instance of built-in type: %s. |
Description |
The internal entity sets such as ErrorArchive, RequestQueue, and EventLog are read-only. The create and update operations are not supported for these read-only entity sets. |
-10351
|
|
Name |
QUERY_ON_WRONG_ENTITY_SET |
Code |
-10351 |
Category |
InvalidInput |
Message |
This function can only be used to retrieve entities from %s but entities from %s were requested. |
Description |
The designated API to retrieve the ErrorArchive and EventLog does not accept other entity sets as the parameter. |
-10352
|
|
Name |
CANNOT_ACCESS_ENTITY_SET_DIRECTLY |
Code |
-10352 |
Category |
InvalidInput |
Message |
The "%s" entity set cannot be accessed directly. |
Description |
The error code is deprecated and is no longer used. |
-10353
|
|
Name |
MISSING_ENTITY_ID |
Code |
-10353 |
Category |
InvalidInput |
Message |
A non-null entity ID needs to be specified. |
Description |
To undo the pending changes for an entity, the target entity ID must be specified. |
-10354
|
|
Name |
NO_ENTITY_FOUND_WITH_ID |
Code |
-10354 |
Category |
InvalidInput |
Message |
No entity with entity ID "%s" was found. |
Description |
The error indicates that the specified entity ID cannot be found in the local database for the undo pending changes operation to be executed. |
-10355
|
|
Name |
ERROR_NOTHING_CAN_BE_UNDONE |
Code |
-10355 |
Category |
NotFound |
Message |
Nothing can be undone for the given entity. |
Description |
The error message suggests that no pending changes have been found in the local database associated with the specified entity ID. |
-10356
|
|
Name |
CLIENT_UPGRADE_NEEDED_FOR_UNDO |
Code |
-10356 |
Category |
PreconditionFailed |
Message |
The request queue database needs to be updated to allow the undo operation to run. The upgrade should happen automatically after the next successful upload or store open. |
Description |
The client is utilizing an outdated SDK version that does not support the undo operation. To perform the undo operation, please ensure that the SDK is up-to-date. |
-10358
|
|
Name |
JSON_INVALID_UNICODE_SEQUENCE |
Code |
-10358 |
Category |
InvalidInput |
Message |
Error at JSON position %lu: "%s" is an invalid Unicode sequence. |
Description |
This error is thrown when there is an invalid Unicode sequence at a specified JSON position. The error message suggests potential issues within the client SDK, and it is recommended to contact SAP support for assistance. |
-10359
|
|
Name |
INVALID_VALUE_DECIMAL_SCALE_TO_ZERO |
Code |
-10359 |
Category |
ClientInternalError |
Message |
Invalid value, "%s", for the property "%s" of Type=\"Edm.Decimal\" with Scale=\"0\" (or unspecified scale ). Please report this issue to the service developer as it is most likely due to incorrect metadata. |
Description |
This error occurs when an invalid value is passed for a decimal property. Please refer to the back-end metadata for the detailed definitions of the property. |
-10360
|
|
Name |
CONCURRENT_MEDIA_STREAM_MODIFICATIONS_NOT_SUPPORTED |
Code |
-10360 |
Category |
NotSupported |
Message |
The request to modify the media stream failed because it was detected that the same media stream is being modified concurrently. Concurrent modifications of the same media stream is not supported. |
Description |
Multiple modifications to the same media stream should be serialized to prevent concurrent issues. |
-10361
|
|
Name |
CONCURRENT_CHANGE_SET_WITH_MEDIA_STREAM_NOT_SUPPORTED |
Code |
-10361 |
Category |
NotSupported |
Message |
The changeset concurrently modifies the same resource as another operation and the changeset contains a media stream operation. This is not supported. Either remove the media stream operation(s) from the changeset or ensure concurrent operations on the same resource are not performed. |
Description |
Same as -10360, multiple modifications to the same media stream in single batch request is not supported. Modifications of the same media stream should be serialized to prevent concurrency issues. |
-10362
|
|
Name |
ERROR_GENERATING_TEMP_TABLE |
Code |
-10362 |
Category |
ClientInternalError |
Message |
An error occurred generating a temp table. The most likely cause of this is a pending upload or download. Make sure all uploads and downloads have been completed and then try the operation again. |
Description |
The error message indicates that the client is busy and recommends waiting for all uploads and downloads to finish before doing a partial upload. |
-10363
|
|
Name |
INVALID_STRING_UPLOAD_CATEGORY |
Code |
-10363 |
Category |
InvalidInput |
Message |
Invalid string upload category. String upload category must not be null/nil, the empty string, or a string consisting only of whitespace. |
Description |
This error arises when an attempted upload includes a category with an invalid string value. |
-10364
|
|
Name |
GENERATE_ID_NOT_ALLOWED_WHEN_UPLOAD |
Code |
-10364 |
Category |
InvalidInput |
Message |
Only string literal or entity value can be used as the upload category when uploading. |
Description |
The error means that the generated ID couldn't be utilized as the upload category during the uploading process. |
-10365
|
|
Name |
INVALID_REQUEST_FOR_GENERATE_UPLOAD_CATEGORY |
Code |
-10365 |
Category |
InvalidInput |
Message |
'useGeneratedIDForUploadCategory' can only be used for create requests. |
Description |
The 'useGeneratedIDForUploadCategory' option can only be enabled for requests that create new entities. |
-10366
|
|
Name |
UPLOAD_CATEGORY_FROM_NEW_ENTITY |
Code |
-10366 |
Category |
InvalidInput |
Message |
Cannot reference an entity that has not been created to use its entity ID for the upload category unless in a change set. |
Description |
The error is caused by attempting to reference an entity that has not been created for the upload category. |
-10367
|
|
Name |
NO_UPLOAD_CATEGORY_ASSOCIATED |
Code |
-10367 |
Category |
InvalidInput |
Message |
Could not determine the entity ID from the referenced entity. Ensure that the referenced entity is created with 'useGeneratedIDForUploadCategory' and is added to the change set prior to the referencing request. |
Description |
The 'useGeneratedIDForUploadCategory' option must be enabled to use the generated entity ID as the upload category. |
-10368
|
|
Name |
SERVER_LOST_DOWNLOAD |
Code |
-10368 |
Category |
ServerSideError |
Message |
The server lost the data to download. |
Description |
This error indicates a server-side issue, whereby the intended data for download cannot be found by the server. Possible causes include server restarts or lack of session affinity. |
-10369
|
|
Name |
NO_FUNCTION_IMPORT_FOR_URL |
Code |
-10369 |
Category |
InvalidInput |
Message |
The provided URL "%s" does not resolve to a function import. |
Description |
Refer to the back-end metadata for the valid function import definitions. |
-10370
|
|
Name |
FUNCTION_IMPORTS_NOT_SUPPORTED |
Code |
-10370 |
Category |
NotSupported |
Message |
Function imports are not supported in this version. |
Description |
The client is utilizing an outdated SDK version that does not support the feature. To perform the desired operation, please ensure that the SDK is up-to-date. |
-10371
|
|
Name |
GET_FUNCTION_IMPORT_NOT_SUPPORTED |
Code |
-10371 |
Category |
NotSupported |
Message |
GET function imports are not supported in this version. |
Description |
Function import calls with HTTP GET request is currently not supported. |
-10373
|
|
Name |
INVALID_ENTITY_SET_OR_FUNCTION_IMPORT |
Code |
-10373 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not an entity set in entity container "%s", nor does it, and/or the specified parameters, match any function imports. |
Description |
This error arises when a discrepancy occurs at a certain URL position as the URL does not correspond to any entity sets in the entity container nor does it match any function imports. |
-10374
|
|
Name |
INVALID_FUNCTION_IMPORT_VERB |
Code |
-10374 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is a function import in entity container "%s", but the specified HTTP method is incorrect. |
Description |
This error arises when the specified HTTP method does not match the function import. The details of the incorrect method and function import are specified in the error message. |
-10375
|
|
Name |
INVALID_UPLOAD_CATEGORY |
Code |
-10375 |
Category |
InvalidInput |
Message |
Invalid string upload category. String upload category must not be null/nil, the empty string, or a string consisting only of whitespace. |
Description |
This error, similar to -10363, occurs when the string of the upload category is not valid. |
-10376
|
|
Name |
INVALID_REQUEST_FOR_GENERATE_UPLOAD_CATEGORY_L_O_DATA |
Code |
-10376 |
Category |
InvalidInput |
Message |
Specifying OfflineOData.NewID as the upload category so that the upload category is set to the generated entity ID is only allowed on create requests. |
Description |
Using OfflineOData.NewId as the value for the upload category in a PUT or PATCH request is not supported. This value can only be used together with a POST request when creating new entities. |
-10377
|
|
Name |
NO_UPLOAD_CATEGORY_ASSOCIATED_L_O_DATA |
Code |
-10377 |
Category |
InvalidInput |
Message |
Could not determine the entity ID from the referenced entity. Ensure that the referenced entity is created with 'OfflineOData.NewID<*>' and is added to the change set prior to the referencing request. |
Description |
The error indicates that the entity ID that has been referred in the upload category can not be identified. |
-10378
|
|
Name |
GENERATE_ID_NOT_ALLOWED_WHEN_UPLOAD_L_O_DATA |
Code |
-10378 |
Category |
InvalidInput |
Message |
Generated ID could not be used as upload category when uploading. |
Description |
The generated entity ID cannot be used as the upload category for partial upload. |
-10379
|
|
Name |
SYNC_FILE_FAILED_DOWNLOAD_CONFLICT |
Code |
-10379 |
Category |
ClientInternalError |
Message |
The %s failed due to a download conflict: %s. |
Description |
The download request encountered a data conflict error during the download process and will automatically attempt to retry the download for such conflicts. |
-10380
|
|
Name |
SUBSET_DOWNLOAD_ALREADY_IN_PROGRESS |
Code |
-10380 |
Category |
PreconditionFailed |
Message |
Another thread is already downloading subset (%s). |
Description |
The request to download a subset of the defining queries was rejected since another thread is currently downloading the same subset. |
-10381
|
|
Name |
ILLEGAL_LITERAL_VALUE |
Code |
-10381 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is an illegal literal value and does not match the rules for an identifier name. |
Description |
The error indicates that a wrong value was provided in the URL which is not compatible as an identifier name. |
-10382
|
|
Name |
CONVERSION_ERROR |
Code |
-10382 |
Category |
ClientInternalError |
Message |
A data type conversion error has occurred. "%s" cannot be converted to "%s". In some cases this can result if "%s" is used in an operation (such as multiplication) with a value or property of type "%s". Using the cast function with "%s" or with the other operation operand MAY fix the problem. |
Description |
The error denotes that a data conversion error has been identified in the given query. Ensure that the provided value falls within the acceptable range for its corresponding type. |
-10383
|
|
Name |
INVALID_PARAMETER_TYPE_TIME_OF_DAY |
Code |
-10383 |
Category |
InvalidInput |
Message |
Error at URL position %lu: expected a parameter that evaluates to a type with a time of day component. |
Description |
The value supplied in the query URL cannot be evaluated as the anticipated Edm.TimeOfDay type. One example is 'Trips?$filter=hour(departureDay) eq 23' (the correct one is 'Trips?$filter=hour(departureTime) eq 23'). |
-10384
|
|
Name |
INVALID_PARAMETER_TYPE_DATE |
Code |
-10384 |
Category |
InvalidInput |
Message |
Error at URL position %lu: expected a parameter that evaluates to a type with a date component. |
Description |
The value supplied in the query URL cannot be evaluated as the anticipated Edm.Date type. One example is 'Trips?$filter=month(destination) eq 11' (the correct one is 'Trips?$filter=month(departureDay) eq 11'). |
-10385
|
|
Name |
INVALID_DURATION_OPERATION |
Code |
-10385 |
Category |
InvalidInput |
Message |
Error at URL position %lu: if the left hand operand is an Edm.Duration, the right hand operand must also be an Edm.Duration. |
Description |
An invalid operation on the Edm.Duration type has been detected. Both sides should be Edm.Duration type. |
-10386
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_REF |
Code |
-10386 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following a $ref. |
Description |
This error occurs when an invalid path segment was detected at the given URL position. One example is 'Customer(1)/Orders/$ref/invalidSegment'. Only $count is allowed to follow $ref, so 'Customer(1)/Orders/$ref/$count' is valid. |
-10387
|
|
Name |
INVALID_KEY_PRED_BEFORE_REF |
Code |
-10387 |
Category |
InvalidInput |
Message |
Error at URL position %lu: $ref cannot follow a path segment with a key predicate. |
Description |
The $ref is expected to follow the referred navigation property, not the key predicate. One example is 'Customer(1)/Orders(1)/$ref' (the correct one is 'Customer(1)/Orders/$ref'). |
-10388
|
|
Name |
MISSING_ID_FOR_DOLLAR_ENTITY |
Code |
-10388 |
Category |
InvalidInput |
Message |
The system query option $id is required to specify the entity reference for an $entity request. |
Description |
For the dollar entity ($entity) query, the query option $id must be specified with a valid entity id. One invalid example is '$entity' without $id (the correct one is '$entity?$id=Customers(101)'). |
-10389
|
|
Name |
INVALID_ID_QUERY_OPTION |
Code |
-10389 |
Category |
InvalidInput |
Message |
The system query option $id does not reference an individual entity. |
Description |
The provided system query option $id does not reference an individual entity as expected. One invalid example is '$entity?$id=Customers' (the correct one should be '$entity?$id=Customers(1)'). |
-10390
|
|
Name |
MISSING_ID_FOR_DELETE_REF |
Code |
-10390 |
Category |
InvalidInput |
Message |
The system query option $id needs to be specified when removing a reference from a collection. |
Description |
When the cardinality of the navigation property is many, to unlink a single entity its ID must be explicitly set using the $id option for the delete link request. |
-10391
|
|
Name |
INVALID_USE_OF_DOLLAR_ID |
Code |
-10391 |
Category |
InvalidInput |
Message |
The system query option $id can only be used for $entity read requests or when removing a reference from a collection valued navigation property. |
Description |
The error indicates that the system query option $id was used incorrectly, it should be used only for $entity read requests or when removing a reference from a collection valued navigation property. |
-10392
|
|
Name |
ID_RESOURCE_PATH_MISMATCH |
Code |
-10392 |
Category |
InvalidInput |
Message |
The entity type referred to in the resource path (%s.%s) does not match the entity type referred to by $id (%s.%s). |
Description |
This error indicates a mismatch of entity type in the resource path and the entity type referred to by $id. One example is '/Customer(1)/Orders/$ref?$id=Customer(1)' (the correct one should like '/Customer(1)/Orders/$ref?$id=Orders(1)'). |
-10393
|
|
Name |
DUPLICATE_CONTENT_ID |
Code |
-10393 |
Category |
InvalidInput |
Message |
Content-ID "%s" is duplicated in the batch request. Content-IDs must be unique within the batch request, not just within the change set. |
Description |
This error occurs when the same Content-ID is used for different entities in the batch request. Content-IDs must be unique within the batch request. |
-10394
|
|
Name |
ERROR_GENERATING_CONTENT_ID |
Code |
-10394 |
Category |
ClientInternalError |
Message |
An error occurred generating a Content-ID. |
Description |
The client encounters unexpected issues when generating new Content-IDs, which should not occur under normal circumstances. If this error happens, contact SAP support for assistance. |
-10395
|
|
Name |
INVALID_PATH_SEGMENT_FOLLOWING_STAR |
Code |
-10395 |
Category |
InvalidInput |
Message |
Error at URL position %lu: an invalid path segment follows *. |
Description |
The error indicates an invalid URL path segment after the . One example is 'Customer?$expand=orders//anyContent'. The invalid path segment will cause this error. |
-10396
|
|
Name |
UNSUPPORTED_O_DATA_VERSION |
Code |
-10396 |
Category |
ClientInternalError |
Message |
"%s" is not a supported version of OData. |
Description |
The error occurred due to use of an unsupported version of OData in the operation or request. |
-10397
|
|
Name |
SYNC_FILE_FAILED_DEPLOY_FILE_NOT_FOUND |
Code |
-10397 |
Category |
ServerSideError |
Message |
The %s failed because no deploy file was found. |
Description |
The client failed to open the store or download due to an inability to find the desired deployment file on the server side. A manual retry is recommended to address the issue. |
-10398
|
|
Name |
ERROR_CANCEL_NO_OPERATION |
Code |
-10398 |
Category |
InvalidInput |
Message |
Cannot cancel because no operation ID is specified. |
Description |
This error occurred because the operation couldn't be cancelled due to a missing operation ID. Please provide a valid operation ID. |
-10399
|
|
Name |
CHANGE_SEND_STORE_ENCRYPTION_KEY_FAILED |
Code |
-10399 |
Category |
ClientInternalError |
Message |
Change copy store "%s" encryption key failed. |
Description |
The attempt to change the encryption key of the store copy has failed. If this error occurs unexpectedly, contact SAP support for assistance. |
-10400
|
|
Name |
SEND_STORE_WITH_NEW_ENCRYPTION_KEY_FAILED |
Code |
-10400 |
Category |
InvalidInput |
Message |
Invalid new encryption key: %s. The new encryption key must not be null/nil, empty string, or a string consisting of whitespace/semicolons. |
Description |
The provided new encryption key for the send store operation is invalid. |
-10401
|
|
Name |
SEND_STORE_COPY_STORE_FAILED |
Code |
-10401 |
Category |
ClientInternalError |
Message |
Error when sending the Offline Store with a new encryption key. Reason: copying entity store of %s failed. |
Description |
The client encountered an I/O error while copying the entity store. Possible causes include insufficient storage space and inadequate permissions. |
-10402
|
|
Name |
SEND_STORE_COPY_REQUEST_QUEUE_FAILED |
Code |
-10402 |
Category |
ClientInternalError |
Message |
Error when sending the Offline Store with a new encryption key. Reason: copying request queue of %s failed. |
Description |
The client encountered an I/O error while copying the request queue store. Possible causes include insufficient storage space and inadequate permissions. |
-10403
|
|
Name |
SEND_STORE_RENAME_FAILED |
Code |
-10403 |
Category |
ClientInternalError |
Message |
Error when sending the Offline Store with a new encryption key. Reason: renaming %s to %s failed. |
Description |
The client experienced an error while renaming the copy of the store. |
-10404
|
|
Name |
SEND_STORE_GET_SIZE_FAILED |
Code |
-10404 |
Category |
ClientInternalError |
Message |
Error when sending the Offline Store with a new encryption key. Reason: getting size of file %s failed. |
Description |
The client cannot obtain the file size of the copied store. |
-10405
|
|
Name |
CANNOT_ORDER_BY_STREAM_PROPERTY |
Code |
-10405 |
Category |
InvalidInput |
Message |
Error at URL position %lu: cannot order by a stream property. |
Description |
The orderby query option should not be used with stream properties. For example, suppose streamProperty is a stream property of entity photo, the query 'photo?$orderby=streamProperty' will cause this error. |
-10406
|
|
Name |
STREAM_PROPERTY_IN_FILTER |
Code |
-10406 |
Category |
InvalidInput |
Message |
Error at URL position %lu: cannot filter using a stream property. |
Description |
The stream property cannot be used with the filter query options. For example, suppose streamProperty is a stream property of entity photo, the query 'photo?$filter=streamProperty eq 1' will cause this error. |
-10407
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_STREAM |
Code |
-10407 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following a stream property. |
Description |
The client identified an invalid path segment following a stream property at a specific URL position. For example, suppose streamProperty is a stream property of entity photo, the query 'photo(1)/streamProperty/anySegment' and the query 'photo(1)/streamProperty/$value' will cause this error. |
-10408
|
|
Name |
STREAM_PROPERTY_PATH_TOO_LONG |
Code |
-10408 |
Category |
InvalidInput |
Message |
Stream property path is too long. |
Description |
The path of the stream property was too lengthy, exceeding the acceptable limit. The current path limit is 2048. |
-10409
|
|
Name |
NO_EDIT_LINK_FOR_DELETE_STREAM |
Code |
-10409 |
Category |
InvalidInput |
Message |
An edit link is required for the deleteStream method. |
Description |
An edit link is essential for the deleteStream method, but it wasn't provided. |
-10410
|
|
Name |
SCHEMA_UPGRADE_NOT_ALLOWED |
Code |
-10410 |
Category |
PreconditionFailed |
Message |
Schema upgrade not allowed. Reason: non-empty request queue. |
Description |
The schema upgrade operation for the client store cannot be completed as there are pending changes in the request queue that have not been uploaded. |
-10411
|
|
Name |
REQUEST_NOT_EXISTS |
Code |
-10411 |
Category |
NotFound |
Message |
A request with name "%s" does not exist. |
Description |
The specified defining query cannot be removed because it does not exist in the store. |
-10412
|
|
Name |
REQUEST_BEING_REMOVED |
Code |
-10412 |
Category |
PreconditionFailed |
Message |
A request with name "%s" is being removed. |
Description |
The request to remove the defining query with the given name has been rejected because it is already in the process of being removed. |
-10413
|
|
Name |
REMOVE_DEFINING_QUERY_NOT_ENABLED |
Code |
-10413 |
Category |
PreconditionFailed |
Message |
Cannot remove the defining query since the required option is not set in the server-side offline configuration. |
Description |
This error occurs if there is an attempt to remove a defining query when the required configuration is not set in the server-side offline configuration. |
-10414
|
|
Name |
REMOVE_DEFINING_QUERY_WITH_PARTIAL_DOWNLOAD |
Code |
-10414 |
Category |
PreconditionFailed |
Message |
Cannot remove defining query since there is a partial download which can be resumed. |
Description |
An attempt was made to remove a defining query while a partial download is ongoing. This is not allowed as it could disrupt the download process. |
-10415
|
|
Name |
REMOVE_DEFINING_QUERY_WITH_PENDING_CHANGES |
Code |
-10415 |
Category |
PreconditionFailed |
Message |
Cannot remove defining query since there are pending changes to upload. |
Description |
An attempt was made to remove a defining query while there are pending changes to upload. |
-10416
|
|
Name |
DISQUALIFIED_ENUM_NAME |
Code |
-10416 |
Category |
InvalidInput |
Message |
"%s" is not a qualified enum type name. |
Description |
The provided string isn't recognized as a valid enum type. Check the provided string for correct spelling and formatting. |
-10417
|
|
Name |
INVALID_ENUM_VALUE |
Code |
-10417 |
Category |
InvalidInput |
Message |
"%s" is not a valid enum value for type "%s". |
Description |
The value provided for the given enum type is invalid. Please review the values for this enum type. |
-10418
|
|
Name |
INVALID_ENUM_TYPE |
Code |
-10418 |
Category |
ClientInternalError |
Message |
Error at URL position %lu: "%s" is not an enum type. |
Description |
This error indicates an issue at a specific URL position. The given argument is not an enumeration type. |
-10419
|
|
Name |
DIFF_ENUM_TYPE_FOR_HAS |
Code |
-10419 |
Category |
InvalidInput |
Message |
The has operator expects left and right operands that share the same enum type. |
Description |
When using the has operator for enum property, it is expected that both operands share the same enum type. |
-10420
|
|
Name |
ARRAY_IS_NIL |
Code |
-10420 |
Category |
ClientInternalError |
Message |
Array is nil. |
Description |
This error is for the legacy iOS SMP SDK which occurs when a function that requires a non-nil array is called with a nil array. |
-10421
|
|
Name |
NO_ENOUGH_LENGTH_FOR_ARRAY |
Code |
-10421 |
Category |
ClientInternalError |
Message |
The length of cArray is not sufficient for nsArray. |
Description |
The error is for the legacy SMP SDK only, indicating that the length of the provided C-style array is smaller than it should be for the given NSArray. |
-10422
|
|
Name |
INVALID_N_S_STRING |
Code |
-10422 |
Category |
InvalidInput |
Message |
"%s" is not an NSString. |
Description |
The provided value is not an NSString. |
-10423
|
|
Name |
RE_BOOTSTRAP_NOT_ALLOWED |
Code |
-10423 |
Category |
PreconditionFailed |
Message |
Re-bootstrap not allowed. Reason: non-empty request queue. |
Description |
The re-bootstrapping operation cannot be performed while there are pending requests in the request queue. It is necessary to clear the request queue prior to initiating a re-bootstrapping process. |
-10424
|
|
Name |
CURRENT_USER_WAS_NOT_PROVIDED |
Code |
-10424 |
Category |
InvalidInput |
Message |
The current user was not provided when enable upload previous user's changes is set on. |
Description |
To support the multi-user use case, currentUser should be provided when forceUploadOnUserSwitch is set to true in OfflineODataParameter. |
-10425
|
|
Name |
HAS_ERROR_WHEN_UPLOAD_PREVIOUS_USER_CHANGES |
Code |
-10425 |
Category |
PreconditionFailed |
Message |
Return error occurred when uploading the previous user's pending changes. |
Description |
An error occurred during the upload of the previous user's pending changes when the second user opened the store. The application should use OfflineProvider.getPreviousUser() to notify the previous user and ask them to take over the device and fix the issue. This typically requires the previous user’s manual involvement. Or, the application can choose to open the store without forceUploadOnUserSwitch and rollback the changes from the previous user. This should be done with care and is generally not recommended, because the previous user’s un-uploaded work will be lost. Instead of rollback, the application can also upload the previous user’s work in the current user context. Careful consideration should be used before implementing this process, because it means the back end will receive the previous user’s request in the current user’s context, which may be a security concern. |
-10426
|
|
Name |
HAS_PENDING_REQUESTS_WHEN_USER_SWITCH |
Code |
-10426 |
Category |
PreconditionFailed |
Message |
There are pending requests inside. Please upload without the forceUploadOnUserSwitch flag first. |
Description |
This error occurs when there are pending requests in the request queue after enabling forceUploadOnUserSwitch the first time. The request should be uploaded without enabling the forceUploadOnUserSwitch flag first and then enabling it again. |
-10427
|
|
Name |
SEND_STORE_NOTE_TOO_LONG |
Code |
-10427 |
Category |
InvalidInput |
Message |
Invalid store note: "%s". Length of the note exceeds the maximum length of 120. |
Description |
The provided store note is too long for sending the store. It should not have more than 120 characters. |
-10428
|
|
Name |
FUNCTIONS_NOT_SUPPORTED |
Code |
-10428 |
Category |
NotSupported |
Message |
Functions are not supported in this version. |
Description |
The client is using an outdated SDK version that does not support function import. Please make sure that the SDK is updated to the latest version. |
-10429
|
|
Name |
ACTIONS_NOT_SUPPORTED |
Code |
-10429 |
Category |
NotSupported |
Message |
Actions are not supported in this version. |
Description |
The client is using an outdated SDK version that does not support action. Please make sure that the SDK is updated to the latest version. |
-10430
|
|
Name |
COLLECTION_PARAMETERS_NOT_SUPPORTED |
Code |
-10430 |
Category |
NotSupported |
Message |
Parameter "%s" of the method "%s" is a collection, and collection parameters are not supported in this version. |
Description |
Collection parameters are currently not supported for action and function import in the client SDK. |
-10433
|
|
Name |
NO_FUNCTION_FOR_URL |
Code |
-10433 |
Category |
InvalidInput |
Message |
The provided URL "%s" does not resolve to a function. |
Description |
The provided URL is invalid since it does not resolve to a function. |
-10434
|
|
Name |
NO_ACTION_FOR_URL |
Code |
-10434 |
Category |
InvalidInput |
Message |
The provided URL "%s" does not resolve to an action. |
Description |
The provided URL is invalid since it does not resolve to an action. |
-10435
|
|
Name |
BOUND_DATA_METHODS_NOT_SUPPORTED |
Code |
-10435 |
Category |
NotSupported |
Message |
Bound actions and functions are not supported in this version. |
Description |
Bound actions and functions are not supported in the current version of the client SDK being used. Please upgrade to a newer version of the SDK to utilize this feature. |
-10436
|
|
Name |
INVALID_PARAMETER_VALUE |
Code |
-10436 |
Category |
ClientInternalError |
Message |
An invalid value was supplied for parameter "%s" of action "%s" with type "%s". |
Description |
An invalid parameter was supplied for a specific action. The type of value provided does not match the expected type. |
-10437
|
|
Name |
UNRECOGNIZED_PARAMETER |
Code |
-10437 |
Category |
InvalidInput |
Message |
A value was supplied for non-existent parameter "%s" of action "%s". |
Description |
A value was provided for a parameter that does not exist in the specified action. |
-10438
|
|
Name |
INVALID_HTTP_METHOD_FOR_ACTION_V4 |
Code |
-10438 |
Category |
InvalidInput |
Message |
HTTP Method is not allowed in V4 Action, only POST is valid. |
Description |
The HTTP Method used is not valid for the OData V4 Action, only POST method is supported. |
-10439
|
|
Name |
NULLIFYING_NON_NULL_PARAMETER |
Code |
-10439 |
Category |
InvalidInput |
Message |
Parameter "%s" of action "%s" cannot be set to null because it is not nullable. |
Description |
A null value was supplied for a parameter of an action that isn't nullable. |
-10440
|
|
Name |
UNRECOGNIZED_DATA_TYPE |
Code |
-10440 |
Category |
ClientInternalError |
Message |
Unrecognized datatype of parameter "%s" for action "%s". |
Description |
The datatype for a given parameter is unrecognized for a specified action. |
-10441
|
|
Name |
INVALID_METHOD_NAME |
Code |
-10441 |
Category |
InvalidInput |
Message |
Error at URL position %lu: "%s" is not a valid action or function name in namespace "%s". |
Description |
The error occurs at a specific URL position: either the action or function's name in the provided namespace is invalid. |
-10442
|
|
Name |
BINDING_PARAMETER_MISMATCH |
Code |
-10442 |
Category |
InvalidInput |
Message |
Error at URL position %lu: the binding parameter of "%s" does not match the entity type. |
Description |
The error occurs at a specific URL position: the binding parameter of the action or function fails to match the entity type. |
-10443
|
|
Name |
MISSING_NON_NULLABLE_PARAMETERS |
Code |
-10443 |
Category |
InvalidInput |
Message |
Non-nullable parameter "%s" is not specified in the request body. |
Description |
The client application has failed to provide a non-nullable parameter in the request body for the action. |
-10444
|
|
Name |
BINDING_PARAMETER_TYPE_NOT_SUPPORTED |
Code |
-10444 |
Category |
NotSupported |
Message |
Binding parameter type is not supported in this version. |
Description |
The use of parameters for bounded actions is not supported. |
-10446
|
|
Name |
BIND_TO_NON_EXIST_ENTITY |
Code |
-10446 |
Category |
InvalidInput |
Message |
The bound action "%s" is binding to non-existing entity "%s". |
Description |
The entity ID provided for the bounded action does not exist in the store. |
-10447
|
|
Name |
UNSUPPORTED_SELECT_COLLECTION_PROPERTY_ITEM |
Code |
-10447 |
Category |
NotSupported |
Message |
Selecting the item of collection property with other property is not supported in this version. |
Description |
For the select query option with a collection property, currently only selecting the collection property itself is supported. For example, suppose homeAddresses is a collection property of entity set Contact and itself is a complex type, the query of 'Contact(1)?$select=name,homeAddresses/city' will cause this error. |
-10448
|
|
Name |
INVALID_PATH_SEGMENT_AFTER_COLLECTION_PROPERTY |
Code |
-10448 |
Category |
InvalidInput |
Message |
Error at URL position %lu: invalid path segment following a collection property. |
Description |
There is an error in the URL at the specified position, which has an invalid segment following a collection property. For example, suppose homeAddresses is a collection property of entity set Contact and itself is complex type, the query of 'Contact(1)/homeAddresses/invalidProperty' will cause this error. |
-10449
|
|
Name |
ORDER_BY_COLLECTION_PROPERTY_ITEM_NOT_SUPPORT |
Code |
-10449 |
Category |
NotSupported |
Message |
Query entity with the order of collection property's sub-property is not supported in this version. |
Description |
The operation of querying an entity in association with the order of a collection property's sub-property is not supported in the current SDK. For example, suppose homeAddresses is a collection property of entity set Contact and itself is complex type, the query of 'Contact?$orderby=homeAddresses/roomNumber' will cause this error. |
-10450
|
|
Name |
ORDER_BY_COLLECTION_PROPERTY_ITEM_COUNT_NOT_SUPPORT |
Code |
-10450 |
Category |
NotSupported |
Message |
Query entity with the order of collection property item count is not supported in this version. |
Description |
The operation of querying an entity in association with the item count of a collection property is not supported in the current SDK. For example, suppose hobbies is a collection property of entity set Contact, the query of 'Contact?$orderby=hobbies/$count' will cause this error. |
-10451
|
|
Name |
ORDER_ENTITY_BY_COLLECTION_PROPERTY |
Code |
-10451 |
Category |
InvalidInput |
Message |
Query entity with the order of collection property is invalid. |
Description |
Ordering the results of a GET query by an entity's collection property is invalid. For example, suppose hobbies is a collection property of entity set Contact, the query of 'Contact?$orderby=hobbies' will cause this error. |
-10452
|
|
Name |
FILTER_BY_COLLECTION_PROPERTY_ITEM_NOT_SUPPORT |
Code |
-10452 |
Category |
NotSupported |
Message |
Filter entity with collection property's sub-property is not supported in this version. |
Description |
Filtering the results of a GET query by the collection property's sub-property is not currently supported in the SDK. For example, suppose homeAddresses is a collection property of entity set Contact and itself is complex type, the query of \"Contact?$filter=homeAddresses/city eq 'London'\" will cause this error. |
-10453
|
|
Name |
FILTER_BY_COLLECTION_PROPERTY_ITEM_COUNT_NOT_SUPPORT |
Code |
-10453 |
Category |
NotSupported |
Message |
Filter entity with collection property item count is not supported in this version. |
Description |
Filtering the results of a GET query by the collection property's item count is not currently supported in the SDK. For example, suppose hobbies is a collection property of entity set Contact, the query of 'Contact?$filter=hobbies/$count gt 1' will cause this error. |
-10454
|
|
Name |
UNSUPPORTED_COLLECTION_TYPE_QUERY |
Code |
-10454 |
Category |
NotSupported |
Message |
This type of query is not supported in this version. |
Description |
The $select query option is currently not supported for collection properties. |
-10455
|
|
Name |
INVALID_ITEM_INDEX_OF_COLLECTION |
Code |
-10455 |
Category |
InvalidInput |
Message |
The item index of collection specified is invalid. |
Description |
The index of a value item for a collection property should be within the range of -1 to the maximum item count. Any integer smaller than -1 used as the index will cause this error. |
-10456
|
|
Name |
NO_SUCH_ITEM_INDEX_OF_COLLECTION |
Code |
-10456 |
Category |
InvalidInput |
Message |
The item index of the specified collection does not exist. |
Description |
The provided index exceeds the maximum number of items in the collection, so it cannot be located. For example, suppose hobbies is a collection property of entity set Contact and it has 5 items inside, the query of 'Contact(1)/hobbies/6' will cause this error. |
-10457
|
|
Name |
TYPES_NOT_COMPARABLE_IN_MEMORY |
Code |
-10457 |
Category |
ClientInternalError |
Message |
Data type is not comparable in collection item filter. |
Description |
The data type that is being filtered in a collection item is not comparable, so the filtering operation has failed. |
-10458
|
|
Name |
OPERATION_NOT_SUPPORTED_IN_MEMORY |
Code |
-10458 |
Category |
NotSupported |
Message |
Operation type "%s" is not supported in collection item filter. |
Description |
The operations and, has, like, and not like are not supported when filtering collection properties. |
-10459
|
|
Name |
UNSUPPORTED_CAST_IN_MEMORY |
Code |
-10459 |
Category |
ClientInternalError |
Message |
Cast from "%s" to "%s" is not supported in collection item filter. |
Description |
For some data types, the casting from one data type to another in a collection item filter is not supported. |
-10460
|
|
Name |
FAIL_TO_GENERATE_DEFAULT_ENCRYPTION_KEY |
Code |
-10460 |
Category |
ClientInternalError |
Message |
Failed to generate the default encryption key for the Offline Store. |
Description |
The application has failed to generate the default encryption key for the Offline Store. This issue should typically not occur under normal circumstances. If this error persists, contact SAP support for assistance. |
-10461
|
|
Name |
UPSERTED_LAST_DOWNLOAD_WITH_REQUEST_QUEUE |
Code |
-10461 |
Category |
InvalidInput |
Message |
Error at URL position %lu: sap.upsertedlastdownload cannot be used with the RequestQueue. |
Description |
The sap.upsertedlastdownload system query function cannot be used with the internal RequestQueue entity set. One example that will cause the error is the query of 'RequestQueue?$filter=sap.upsertedlastdownload()'. |
-10462
|
|
Name |
INVALID_QUERY_FOR_REQUEST_QUEUE |
Code |
-10462 |
Category |
InvalidInput |
Message |
Error at URL position %lu: Invalid path for accessing an entity through the RequestQueue. |
Description |
An error at a certain position in the URL where the path for accessing an entity through the RequestQueue is invalid. For expand, you could use one of the following two ways: RequestQueue?$expand=CustomHeaders and RequestQueue?$expand=DependentRequests. AffectedEntity can not be used. |
-10463
|
|
Name |
DELETING_REQUEST_IN_BATCH |
Code |
-10463 |
Category |
NotSupported |
Message |
Deleting from the RequestQueue in a batch request is not supported. |
Description |
The operation of deleting from the RequestQueue in a batch request is not supported in the current SDK. The deleting from the RequestQueue should only be processed at the client side while batch operations will be sent to the back end. |
-10464
|
|
Name |
UNSUPPORTED_UNDO_OPTION |
Code |
-10464 |
Category |
NotSupported |
Message |
Undo UploadCategory or TransactionID with type other than stringLiteral is not supported. |
Description |
To undo all the pending changes for a specific UploadCategory, only the UploadCategory of the type stringLiteral is supported. The same rule applies when using the undo function with a TransactionID. |
-10465
|
|
Name |
ERROR_DELETE_REQUEST_WHILE_UPLOAD_IN_PROGRESS |
Code |
-10465 |
Category |
PreconditionFailed |
Message |
Cannot delete from the ErrorArchive while another thread is uploading the request queue. |
Description |
An operation attempting to delete the ErrorArchive during another thread uploading the request queue has failed. Please delete it after uploading is done. |
-10466
|
|
Name |
CONNECTION_WAS_INTERRUPTED |
Code |
-10466 |
Category |
CommunicationError |
Message |
The connection was interrupted: %s. |
Description |
A loss or interruption of the connection has occurred, possibly due to network issues. The descriptive message is included in the main error message. |
-10467
|
|
Name |
GENERAL_INTERNAL_ERROR |
Code |
-10467 |
Category |
ClientInternalError |
Message |
An internal error has occurred: %s. |
Description |
An internal error that is not related to the user’s inputs has occurred. The descriptive message is included in the main error message. |
-10468
|
|
Name |
CONFLICT_MBT_CLIENT_INSTANCE_ID |
Code |
-10468 |
Category |
InvalidInput |
Message |
autoRegisterMbtClient adds HTTP header Client-Instance-ID implicitly, which conflicts with the CustomHeaders. |
Description |
The autoRegisterMbtClient option is trying to add Client-Instance-ID header implicitly, which conflicts with the one already present in the CustomHeaders. |
-10469
|
|
Name |
ERROR_FETCHING_CLIENT_INSTANCE_ID |
Code |
-10469 |
Category |
ClientInternalError |
Message |
An error occurred while fetching the Client-Instance-ID for Mobile Back-End Tools. |
Description |
This error occurs when fetching the Client-Instance-ID for MBT when the autoRegisterClient option is enabled. |
-10470
|
|
Name |
ERROR_DELETING_CLIENT_INSTANCE_ID |
Code |
-10470 |
Category |
ClientInternalError |
Message |
An error occurred while deleting the Client-Instance-ID for Mobile Back-End Tools. |
Description |
This error occurs when deleting the Client-Instance-ID for MBT when the autoRegisterClient option is enabled. |
-10471
|
|
Name |
DUPLICATED_KEY_PROPERTIES_IN_DEEP_INSERT |
Code |
-10471 |
Category |
NotFound |
Message |
The deep inserted entities have duplicated key properties. |
Description |
Duplicated entity key properties have been identified in the deep insert requests. |
-10472
|
|
Name |
GEOSPATIAL_PROPERTY_IN_FILTER |
Code |
-10472 |
Category |
InvalidInput |
Message |
Error at URL position %lu: cannot filter using a geospatial property. |
Description |
Filtering the query results using a geospatial property is currently not supported. |
-10473
|
|
Name |
CANNOT_ORDER_BY_GEOSPATIAL_PROPERTY |
Code |
-10473 |
Category |
InvalidInput |
Message |
Error at URL position %lu: cannot order by a geospatial property. |
Description |
Ordering the query results by a geospatial property is not supported. |
-10474
|
|
Name |
ERROR_UPGRADE_CLIENT_ONLY_SCHEMA |
Code |
-10474 |
Category |
ClientInternalError |
Message |
An error occurred while upgrading client-only schema. Error detail: %s |
Description |
This error indicates that there was a failure during the upgrade process of the client-only schema. Details of the specific error encountered are included in the message. If this error occurs, contact SAP support for assistance. |
-10475
|
|
Name |
ERROR_PURGE_CLIENT_ONLY_DATA |
Code |
-10475 |
Category |
ClientInternalError |
Message |
An error occurred while purging client-only schema. Please reset client app to proceed. |
Description |
This error means a purging error has occurred in the client-only schema. In order to solve this, a reset of the client application is required. |
-10476
|
|
Name |
ERROR_PREVIOUS_METADATA_NOT_FOUND |
Code |
-10476 |
Category |
ClientInternalError |
Message |
The previous version of client-only metadata does not exist. Please use OfflineODataProvider.purgeClientOnlyData() to purge the client-only data and try again. |
Description |
This issue occurs when the client anticipates retrieving the prior version of client-only metadata, but fails to locate it within the database. |
-10477
|
|
Name |
ERROR_EMPTY_METADATA |
Code |
-10477 |
Category |
InvalidInput |
Message |
The provided metadata text in the CSDLDocument is empty, please check if the RETAIN_ORIGINAL_TEXT option is set for proxygenerator. |
Description |
This error points out the metadata text within the supplied CSDLDocument is empty, potentially due to the RETAIN_ORIGINAL_TEXT option not being set for the proxygenerator. |
-10478
|
|
Name |
ERROR_INCOMPATIBLE_METADATA |
Code |
-10478 |
Category |
InvalidInput |
Message |
The provided metadata text in the CSDLDocument has some breaking change that is not compatible with the previous version. Please reset the client app to proceed. |
Description |
This error emerges when the metadata text within the CSDLDocument encompasses modifications that conflict with earlier versions. It is necessary to reset the client application to resolve the issue. |
-10479
|
|
Name |
ERROR_METADATA_VERSION_MISMATCH |
Code |
-10479 |
Category |
InvalidInput |
Message |
The metadata version in the client metadata does not match the version in the back end. The back-end metadata has OData version %s, but the client has odata version %s. |
Description |
This error discloses a mismatch in metadata versions. The back-end metadata and the client metadata have different OData versions. |
-10480
|
|
Name |
ERROR_METADATA_CLIENT_ONLY_ENTITY_NOT_FOUND |
Code |
-10480 |
Category |
InvalidInput |
Message |
No valid models are annotated with the ClientOnly term. Please refer to the Offline OData documentation for Offline vocabulary usage. |
Description |
This error signifies no valid models are annotated with the ClientOnly term. Refer to the Offline OData documentation for Offline vocabulary usage. |
-10481
|
|
Name |
ERROR_GENERATING_CLIENT_SCHEMA |
Code |
-10481 |
Category |
InvalidInput |
Message |
Failed to generate client-only schema. Please double check whether the client-only models are properly defined in the metadata. |
Description |
This error suggests a failure in generating the client-only schema due to possible issues with the definition of the client-only models in the client metadata. |
-10482
|
|
Name |
ERROR_CLIENT_ONLY_REQUESTS_EXIST |
Code |
-10482 |
Category |
PreconditionFailed |
Message |
The %s operation is not allowed at this point. Reason: client-only requests exist in the queue. Please purge client-only data and try again. |
Description |
If there are some client requests in the queue, the operation is not allowed in order to avoid the potential loss of requests. |
-10483
|
|
Name |
NAVIGATION_KEY_DIFFERENT_WITH_DIRECT_RELATE_ENTITY |
Code |
-10483 |
Category |
InvalidInput |
Message |
The value of navigation key: "%s" is different than the value of key: "%s" in direct related entity type: "%s". |
Description |
The error indicates a discrepancy between the value of the navigation key provided and the value of the key referred to in the direct related entity. |
-10484
|
|
Name |
CANNOT_UPDATE_LINK_THROUGH_NAVIGATION_KEY |
Code |
-10484 |
Category |
InvalidInput |
Message |
Could not modify the link using the navigation property: "%s" which is used as key in entity type: "%s". |
Description |
It is not allowed to modify the link using the navigation property to change the direct related entity. |
-10485
|
|
Name |
CANNOT_UPDATE_DEPENDENT_PROPERTY_FOR_NAVIGATION_KEY |
Code |
-10485 |
Category |
InvalidInput |
Message |
Could not update dependent property: "%s" where corresponding navigation property: "%s" is used as key in entity type: "%s". |
Description |
The error refers to the inability to update a dependent property where its corresponding navigation property is used as a key in an entity type. If you want to update it, please also update its navigation key with the same value and make sure that the entity referred to with the new value exists. |
-10486
|
|
Name |
CANNOT_REPLACE_BINDING_WITHOUT_DEPENDANT_PROPERTY |
Code |
-10486 |
Category |
InvalidInput |
Message |
A bind operation using navigation property "%s" cannot be replaced by setting dependent referential properties because no dependent value was set while dependent properties is used in key in entity "%s". Since the OData back end does not support bind operations, the bind operation will not be sent to the back end. |
Description |
The error occurs when a bind operation cannot be replaced by setting dependent referential properties due to no dependent value being set while dependent properties are used as entity key. |
-10487
|
|
Name |
CANNOT_DIRECT_POST_ENTITY_WITH_NAVIGATION_KEY |
Code |
-10487 |
Category |
InvalidInput |
Message |
Could not directly post entity:"%s", which include key properties of a directly-related entity: "%s". "%s" MUST be included either as references or as content. |
Description |
This error occurs when a directly-related entity is not properly included as either a reference or content during the posting of an entity. |
-10488
|
|
Name |
PART_KEY_WERE_REFER_IN_NAVIGATION_KEY |
Code |
-10488 |
Category |
InvalidInput |
Message |
Navigation key path of entity "%s" doesn't include all keys of directly-related entity "%s". |
Description |
The error indicates that the navigation key path of an entity does not include all keys of a directly-related entity. |
-10489
|
|
Name |
KEY_ALIAS_NAME_IS_NOT_UNIQUE |
Code |
-10489 |
Category |
InvalidInput |
Message |
Alias name "%s" is not unique within entity type "%s". |
Description |
This error message indicates an issue where the same alias name is already being used as an entity type. According to the OData specification, the alias name must be a simple identifier and must be unique within the set of aliases, structural, and navigation properties of the containing entity type and any of its base types. |
-10490
|
|
Name |
NAVIGATION_KEY_COULD_NOT_BE_NULLABLE |
Code |
-10490 |
Category |
InvalidInput |
Message |
Navigation key path "%s" in entity "%s" used a nullable navigation "%s", which is invalid. |
Description |
The error occurs when a property in partner that the navigation property refers to is nullable. |
-10491
|
|
Name |
CAN_NOT_LOCATE_PROPERTY_WITH_NAME_PATH |
Code |
-10491 |
Category |
InvalidInput |
Message |
Key path "%s" within entity type "%s" doesn't identify a property. |
Description |
The error is thrown when the key path within an entity does not identify any property. Please check the name path and make sure it can identify a property. |
-10492
|
|
Name |
KEY_PROPERTY_REF_TO_NULLABLE_NAVIGATION_PROPERTY |
Code |
-10492 |
Category |
InvalidInput |
Message |
Key path "%s" in entity "%s" should not refer to a nullable navigation property "%s". |
Description |
The error occurs when a key path refers to a nullable navigation property, which is not permissible. |
-10493
|
|
Name |
NAME_PATH_LOCATED_IS_NOT_A_SIMPLE_PROPERTY |
Code |
-10493 |
Category |
InvalidInput |
Message |
Key path "%s" within entity type "%s" identifies one property that is not a simple type. |
Description |
This error indicates that the identified property in the key path within an entity type is not a basic data type. It can not be a collection or complex type. |
-10494
|
|
Name |
NAVIGATION_KEY_PATH_IS_DUPLICATED |
Code |
-10494 |
Category |
InvalidInput |
Message |
Navigation key path "%s" in entity "%s" is used multiple times in different aliases. |
Description |
The error occurs when a navigation key path is used more than once in different aliases. Each navigation key path should be unique and not repeat. |
-10495
|
|
Name |
KEY_PROPERTY_REF_TO_NULLABLE_COMPLEX_PROPERTY |
Code |
-10495 |
Category |
InvalidInput |
Message |
Key path "%s" in entity "%s" must not refer to a nullable complex type property "%s". |
Description |
The error occurs when a nullable complex type property is incorrectly referred to in the entity's key path. A key can not be nullable, so please make sure it is not nullable. |
-10496
|
|
Name |
KEY_PROPERTY_REF_TO_NULLABLE_PROPERTY_ITEM |
Code |
-10496 |
Category |
InvalidInput |
Message |
Key path "%s" in entity "%s" can not refer to a nullable simple property "%s" in type "%s". |
Description |
The error indicates a nullable simple property is incorrectly referenced in the entity's key path. A key can not be nullable, so please make sure it is not nullable. |
-10497
|
|
Name |
KEY_REFERENCE_NOT_ENABLED |
Code |
-10497 |
Category |
PreconditionFailed |
Message |
Found a client-only entity with key property reference, but server doesn't support it. Please enable it at server side. |
Description |
This error happens when a client-only entity has a key property reference but the OData back end doesn't support it. Thus, server-side enabling is necessary. |
-10498
|
|
Name |
NAVIGATION_KEY_DIFFERENT_WITH_DEPENDANT_PROPERTY |
Code |
-10498 |
Category |
InvalidInput |
Message |
The value of navigation key: "%s" is different than the corresponding dependant property: "%s". |
Description |
The error occurs when the navigation key provided is different than the dependant property provided. Please make sure they are the same or that the dependant property is empty. |
-10500
|
|
Name |
FAIL_TO_REMOVE_RELATIONSHIP_FOR_NAVIGATION_KEY |
Code |
-10500 |
Category |
InvalidInput |
Message |
Failed to remove a relationship of entity type "%s.%s" using navigation property "%s", because the property is also used as key. |
Description |
This error indicates that a relationship could not be removed as the navigation property being used is also used as a key. If the relationship is removed, the key from the partner that the navigation property referred to would not be able to be retrieved. |
Last update: April 18, 2024