We dynamically load layers into our implementation of the CMV application, invoking the Identify widget's addLayerInfos method. This works fine, but does not let us configure the identify result template for the layer being loaded. We can't use config/identify.js to handle this, because we don't know at design time what the layer's identifier will be. (We store info on all of our possible layers, hundreds of them, in a database; users can choose to load at run time any combination of services and feature layers they need.)
A simple addition to Identify.js, to look for an "identifies" property of layerInfo objects sent to addLayerInfos method and append that the the widgets "identifies" object would allow us to configure identify results dynamically.
We dynamically load layers into our implementation of the CMV application, invoking the Identify widget's addLayerInfos method. This works fine, but does not let us configure the identify result template for the layer being loaded. We can't use config/identify.js to handle this, because we don't know at design time what the layer's identifier will be. (We store info on all of our possible layers, hundreds of them, in a database; users can choose to load at run time any combination of services and feature layers they need.)
A simple addition to Identify.js, to look for an "identifies" property of layerInfo objects sent to addLayerInfos method and append that the the widgets "identifies" object would allow us to configure identify results dynamically.