resource-instance-select vm looks up tile's related resources one at a time

[whatisgalen]

A resource-instance-list datatype node can have references to N other resource-instances. Once that list gets large, the report slows down considerably.

in the resource-instance-select viewmodel, there's some logic executed for each related resource instance in the tile value:

var updateNameAndOntologyClass = function(values) {
                var names = [];
                var value = ko.unwrap(values);
                if (!self.multiple && value && !Array.isArray(value)) {
                    value = [value];
                }
                if(!!value) {
                    value.forEach(function(val) {
                        if (val) {
                            if(!val.resourceName) {
                                Object.defineProperty(val, 'resourceName', {value: ko.observable()});
                            }
                            if(!val.ontologyClass) {
                                Object.defineProperty(val, 'ontologyClass', {value:ko.observable()});
                            }
                            if(!val.iconClass) {
                                Object.defineProperty(val, 'iconClass', {value: ko.observable()});
                            }
                            resourceUtils.lookupResourceInstanceData(ko.unwrap(val.resourceId))
                                .then(function(resourceInstance) {
                                    if (resourceInstance) {
                                        names.push(resourceInstance["_source"].displayname);
                                        self.displayValue(names.join(', '));
                                        val.resourceName(resourceInstance["_source"].displayname);
                                        val?.iconClass(self.graphLookup[resourceInstance["_source"].graph_id]?.iconclass || 'fa fa-question');
                                        val.ontologyClass(resourceInstance["_source"].root_ontology_class);
                                    }
                                });
                        }
                    });
                }
            };

... which is a problem, because resourceUtils.lookupResourceInstanceData( executes a single search query each time it's called. For tiles where there might be 100 related resources, this is a major performance hit.