Check discussion for this article.

I would like to advise against this course of action, there are several reasons:

1. Ensemble messages should be as small as possible. If you can pass id only, pass id only, etc. Minimizing message size keeps production efficient.
2. ResultSet does not contain the data itself, it's more like a compiled instructions on how to get the data. Only when you're calling Next method the data is actually loaded into memory
3. Results of SQL query should be immediately acted upon, because the older the SQL results, the more they differ with reality. it is best to pass parameters and execute query in-place.

If you want it for debugging purposes you can add a trace event which would store ids only for example, but if you actually need to pass a set of results between different business hosts it may be beneficial to you to rethink the production architecture.

Here's some questions:

1. What business hosts do you have?
2. What data do you pass between different hosts?
3. Can you pass parameters between hosts and execute a query on a target host?
4. Can you pass not a set between hosts, but rather elements individually?

Some options:

• Check this example
• Use ZEN reports
• Produce CSV and use LibreOffice to convert CSV to XLSX. Article about this approach.
• Use Apache POI to generate XLSX. Here's Apache POI JGW wrapper and ObjectScript API but you'll need to extend it.

> - Utilize another language or library that has methods to parse the data into an Excel file (https://stackoverflow.com/questions/17684610/python-convert-csv-to-xlsx).

If you want to use Python from Cache, check PythonGateway.

If you want to transfer data via REST check RESTForms project (part 2).

Mimedata is subscripted by name and index.

So in your case:

set name = "BulkFileUpload"
for i=1:1:%request.CountMimeData(name)
    set mimeData = %request.GetMimeData(name, , i)
}

On each iteration mimeData variable would hold the stream with one next mimedata.

%request is simply an object of %CSP.Request class, check the docs or code to know how it works.

Additionally you can use this snippet to see what's inside %request, %response and %session objects:

set %response.ContentType = "html"
do ##class(%CSP.Utils).DisplayAllObjects()
quit $$$OK

<FILEFULL>  - Caché attempted to allocate a disk block for more global data or routine storage, but the attempt failed because the Caché database is full and could not be expanded.

Affected db is /hs-connect-hom/db/BPINTEGRADEV-GLB.

Bitmap indices maintain one node per each chunk of 64 000 id's, if at least one id from that range exists. So random integer ids can slow bitmaps down. On the other hand if there are two consecutive but spread (i.e 1..1000 and 100000...110000) id sequences it would generate just 2 global nodes so everything should be ok in that scenario.

Check index global in various scenarios:

Class Example.Bitmap Extends %Persistent
{

Property ID As %Integer(MINVAL = 1);

Property Value As %Integer(MAXVAL = 9, MINVAL = 0);

Index IDKEY On ID [ IdKey, Unique ];

Index ValueIndex On Value [ Type = bitmap ];

ClassMethod Populate(startid, endid, step = 1) As %Integer
{
    set count = 0
    do ..%KillExtent()
    for i = startid:step:endid {
        set count = count + 1
        set ^Example.BitmapD(i) = $lb("", $random(10))
    }
    
    do ..%BuildIndices()
    
    quit count
}

Query Select(value) As %SQLQuery
{
SELECT ID
FROM Example.Bitmap
WHERE Value = :value
}

/// do ##class(Example.Bitmap).Test()
ClassMethod Test()
{
    do ..TestOne(1, 1000000)
    do ..TestOne(100000000, 101000000)
    do ..TestOne(1, 1000000000, 1000)
}

ClassMethod TestOne(startid, endid, step = 1)
{
    set startTS = $zh
    set count = ..Populate(startid, endid, step)
    set endTS = $zh
    
    set populateTime = endTS - startTS
    
    set startTS = $zh
    set rs = ..SelectFunc($random(10))
    
    set endTS = $zh
    
    set queryTime = endTS - startTS
    
    write $$$FormatText("Start: %1, End: %2, Step: %3, Count: %4, Populate Time: %5, Query Time: %6", startid, endid, step, count, populateTime, queryTime),!
}
}