Attachment don't flow to mobile (SUP +DOE)
I tried to use attachment function in doe +SUP but i have a problem.
The message arrived in mobile but without attachment content.
The attachment don't flow to mobile (SUP).
In doe DOE portal monitor ( Queue Tracking ) there are some Queues (MMW_Q_) with my attachments.
The Queue Details
EMPLOYEE teste 04.06.2011 22:21:11 193 SAPMSSY1 0050560106351ED0A3DA8F02B0259D69
The others objects (not attachment function) arrived perfectly in mobile.
Any idea about how to do work with attachment in DOE +SUP ?.
Siva R Krishna replied
I actually explained in other thread of yours about how the attachment functionality actually works. Keeping that in mind, I have a suggestion for you.
Model your data objects in such a way that the attachments are downloaded to DOE as part of normal initial/delta download. Now I guess you would have modelled ESDMA in DOE and used that ESDMA in SUP to develop the application. But the catch here is when you deploy this ESDMA bundle in SUP, the configured service is a regular service in DOE. Meaning it can push data from DOE to SUP to device or take data from SUP and perform regular operations like CRUD and Backend search.
But in order to get attachment from Device, you need to call a seperate service in DOE. But as far as I know in SUP, there is nothing available like that. So the option is, when you see a particular record in device which has a attachment field with value 'X', provide an option in device application by placing a button to call the attachment service in DOE directly. All you need to provide to this service is the sycnkey of that record along with the attachment field along with the logon credentials of DOE.
Until Sybase provides an option to call attachment service from the ESDMA bundle directly, you have to call DOE service directly from the device. ( As far as I know, there is nothing available in SUP like you want but I might be wrong here)
Hope you understood.