Hi Michael,

ControlID should be set in uploadcontrol when you want to use server-side events. It is important to set unique ID for the whole application. For instance if you have instantiated one igUpload widget in Page1.aspx and another one in Page2.aspx then our advice is to set unique identifiers for both - according to naming convention you prefer. E.g. for those in Page1.aspx page1_uploader1 and for Page2.aspx to be page2_uploader1. Do not set them when using WebUpload for asp.net because these IDs are set automatically.

Thanks,

Miro Hristov

Hi Angel,

in your sample code you state that "serverID1" is the ControlID of the upload control. if this is not the id attribute of the HTML element, how can i find out the controlID, or should i leave it as "serverID1"

i am using the igUpload control via javascript only and not razor or aspx implementation

Thanks

Michael

Sorry, I worked it out.

Looking closer at your code sample I realised the event handler can be wired up in the controller. I had an earlier sample where the handler was wired up in App_Start.

Therefore I can create a custom class to capture the record data that also contains the handler code. That way when it fires I can tell which record/activity it's for.

Thanks again for your useful feedback.

Hi Team,

If the "ControlId" gives me a clear idea regarding the "type" of page the upload occurred in; what is the suggested approach to provide view specific data so that the upload can be matched with a specific record or activity?

By the way, in the above sample code, "serverID1" is the "ControlId" property value of the control. It's a unique identifier (globally across pages) for that file upload so that the server-side module can match the handler with the actual upload control . This is not the ID of the actual HTML element on the page, because you may have many pages with different uploads, and the module which fires events is global for all upload operations.

Thanks,

Angel