Maestro: Display property mapping in Layer editor does not match the generated XML

[jumpinjackie]

Original Link: https://trac.osgeo.org/mapguide/ticket/2747

Per this thread: ​http://osgeo-org.1560.x6.nabble.com/Out-of-Order-SelectionPanel-js-td5288902.html

I tried reproducing the problem with data provided by Gordon. It turns out that the layer properties I'm selecting to show does not match the generated XML in terms of display order.

[jumpinjackie]

I can't reproduce this anymore

[RenoSun]

Hi Jackie,

Are there any ways to fix the same problem with AIMS 2017 (MapGuide 3.1.1.4601)?

http://osgeo-org.1560.x6.nabble.com/AIMS-2014-to-AIMS-2017-Selection-Panel-Display-Order-Issues-td5346401.html

Mapguide-Rest, and Ajax Viewer (Basic Layout) will return the right order of labels and values, but Fusion will not ...

The "QUERYMAPFEATURE" is getting the values with the right order, but not the order or the label
names...

However, there is another request came with the DisplayName(s) under LayerMetadata was replied with the wrong order of the DisplayName(s)...

Thank you very much!

[RenoSun]

Actually the Ajax Viewer has the same LayerMetadata with the same order that the data connection configuration XML has, but under Feature ... it responded the correct order of both label names, and values.

However, it's able to displayed the correct feature info.

Also, it's the correct order of the label and value under Feature response by using Fusion too.

Any codes that I may change in order to display the content with the order under Feature????

[RenoSun]

Temporary solution here for this problem with Fusion users:

under FusionSF.js:

convertExtendedFeatureInfo: function (efi) {
...
var layerMeta = selLayer.LayerMetadata[0];
//add this
var layerFeature = selLayer.Feature[0];
...
var metaProp = layerMeta.Property[j];
//add this
var featureProp = layerFeature.Property[j]
...
//change metaProp.DisplayName[0] to following code
pvals.push(featureProp.Name[0]);
...
}