SAP Asset Manager 2010 - Selective Uploads

[former_member497771]

Hi,

We are trying to do a selective Upload on Notification Edit. So, when the User edits and saves a notification, just the edited notification should be posted to SAP and downloaded back to the device with actual notification number. In NotificationUpdate.action, I've included "RequestOptions" tag with UpdateMode and UpdateCategory properties. I've created a custom Upload action and specified the "UpdateCategory" name which I've created previously on the NotificationUpdate.action under the "UploadCategories" property. But the selective upload is not working as expected for the below scenarios:

1. When I create two Notification's locally and edit only the second local notification and save it, technically it should only post the second notification back to SAP, but it is posting both the local notifications to SAP even though I've not edited the first local notification.

{
"Service": "/SAPAssetManager/Services/AssetManager.service",
"UploadCategories": [ "Cat1" ],
"OnSuccess" : "/XYZ/Actions/Notifications/CreateUpdate/ZNotificationAutoDownload.action",
"_Type": "Action.Type.OfflineOData.Upload"
}

2. When I create a Local work order and a Local Notification, then I've edited a local notification and saved it. It is posting both the local work order and local notification back to SAP instead of just the local notification where I've mapped the "UploadCategory". Looks like the UploadCategory is truly not working as expected for local items.

Can any of you please tell me if I need to do something differently to overcome this issue with local items?

We are using SAP Asset Manager 2010, Application Version 2010.0.2, SAPMDC version 5.1.1-0001 on iOS device with iOS 14.

Thanks in advance.

[bill_froelich]

There are scenarios where non-tagged category items will still be uploaded based on the following.

"When performing a partial upload, Offline OData automatically includes all requests that the specified requests depend on, regardless of whether or not those dependent requests were marked with the same upload category. For example, if an app creates Customers(101) followed by Orders(1) related to Customers(101), and marked Orders(1) with the upload category “very high,” when flushing upload category “very high,” the request to create Customers(101) will also be included in the upload even though it was not included in the “very high” upload category.

You can specify multiple upload categories when performing the upload. Any operation that contains one of these upload categories will be sent during the upload.

If one request within a change set is marked with an upload category, all requests within the change set are automatically treated as having that upload category."