cancel
Showing results for 
Search instead for 
Did you mean: 

Error During ChangeSet Offline Call

Angelo_Ab
Explorer
0 Kudos
211

Hi,

from yesterday I have a problem during ChangeSet offline call.

The app return this error: "Error: Attempt to get length of null array"

In the Mobile Client Log Upload i have this:

commit change set error Params: {"serviceUrl":"https://xxxxxxxxxx.hana.ondemand.com/s4-backend-odata/sap/opu/odata/sap/ZSERVICE","offlineEnabled":true} Error: Attempt to get length of null array

The previous week I can call ChangeSet without problem.

I checked every change I made and all seems ok. I do not understand what's the problem. 

I checked all the rules and actions and all seems ok.

I checked also all the arrays in the rules with some alerts and all of them has correct length.

The error seems to come from the Framework.

Someone experienced the same issue ? Any idea ?

ChangeSet action code:

{
    "_Type": "Action.Type.ODataService.ChangeSet",
    "ActionResult": {
        "_Name": "ChangeSetCreateSalesOrder"
    },
    "OnFailure": "/somanagement/Actions/CreateSalesOrderActions/MessageErrorChangeSetCreateSalesOrder.action",
    "OnSuccess": {
        "Name": "/somanagement/Actions/GenericToastMessage.action",
        "Properties": {
            "Message": "$(L,'SalesOrderCreatedSuccess')"
        }
    },
    "Target": {
        "Service": "/somanagement/Services/ServiceV2.service"
    },
    "Actions": [
        "/somanagement/Actions/CreateSalesOrderActions/CreateSalesOrderHead.action",
        "/somanagement/Rules/CreateSalesOrder/CreateSalesOrderItems.js",
        "/somanagement/Rules/CreateSalesOrder/CreateSalesOrderTexts.js"
    ]
}

Thank you,

Angelo.

View Entire Topic
Angelo_Ab
Explorer
0 Kudos

@bill_froelich 

Update:

after the deactivation of Media property(in SEGW) in the Entity Item I'm able to use CreateEntity action.

Seems like that when an Entity is configured to transfer a Stream you cannot use CreateEntity but you can only use a createMedia.

I do not know if this is a standard OData behavior but it seems to be the case.