You will need to use the remedy api to write the binary data to a remedy attachment field.
Two approaches off the top of my head: Use the native .net/sybase to store the data in whatever native format sybase uses to store binary data, then either write something triggered in the view form/ticket creation to use the remedy api to retrieve the attachment from the db, Use the remedy .net api to store the write the binary data into an attachment field in a regular remedy form, then relate or copy the remedy attachment data to your ticketing form. Axton On 8/17/07, RAMTRI, Nisha, IDC <[EMAIL PROTECTED]> wrote: > ** > > Hi List, > > We are on ARS 6.3 and Sybase 5.1 here in the organisation. We are in the > process of building a console which allows our users to submit calls in a > customised form. This has a .NET front-end which through a stored procedure > inserts records in a Remedy staging table (which is a regular form) and this > staging form in turn inserts records in other main forms at the back-end. > > Now we have a requirement to allow users to attach some files as attachments > in the GUI and send them to final attachment fields on the regular form. Can > anyone give ideas for a good way of doing this? I have made an attachment > field in the staging form so that it can pass the files to the other regular > forms. But my stored procedure is not able to update/pass value to this > attachment field on staging form. Hence I am stuck in this. > > Can anyone suggest what I should be doing in this case? > > Thanks. > > Warm Regards, > > Nisha Ramtri > IEA Remedy Team > RBS India Development Centre > > *********************************************************************************** > The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered > Office: 36 St Andrew Square, Edinburgh EH2 2YB. > Authorised and regulated by the Financial Services Authority > > This e-mail message is confidential and for use by the > addressee only. If the message is received by anyone other > than the addressee, please return the message to the sender > by replying to it and then delete the message from your > computer. Internet e-mails are not necessarily secure. The > Royal Bank of Scotland plc does not accept responsibility for > changes made to this message after it was sent. > > Whilst all reasonable care has been taken to avoid the > transmission of viruses, it is the responsibility of the recipient to > ensure that the onward transmission, opening or use of this > message and any attachments will not adversely affect its > systems or data. No responsibility is accepted by The > Royal Bank of Scotland plc in this regard and the recipient should carry > out such virus and other checks as it considers appropriate. > Visit our websites at: > www.rbs.com > www.rbs.com/gbm > www.rbsgc.com > *********************************************************************************** > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit > http://www.messagelabs.com/email > ______________________________________________________________________ > __20060125_______________________This posting was > submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
