SUP MBO base64 string - better idea?
We have SUP 2.1.3 ESD #3.
I am trying to send an base64 string (image) to the SAP backend via a WebService (generated from SAP - SOAP) via a MBO in a native App.
I tried the following:
Load argument for the string is a personalization key. Backend SAP is RAWSTRING, SUP offers Binary. But I must provide a lenght - 15.000 is quite small for a picture but I think quite big for an personalization key default value.
In code I try to set the value of the personalization key and synchronize the MBO.
We didn't use MBO operation - because then I wouldn't get feedback if the operation was successful! The webservice responses if the action was sucessfull or not.
MBO is in a "on demand" cache group with all values (hour minute seconds) set to zero.
I don't think that the MBO concept here is the best idea - since it is unflexible concerning the size of the lenght of the binary.
But what else to do?
We cannot just create oData services since it is additional development afford.
What would you suggest? Use the SUP as a proxy and call call the responded URL directly in code?
I think using MBO here as caching is totally "useless"?!
For some reasons we would use MBOs - caching data, but other calls would be better if they could be done "directly". How to effectively mix them?