Hi,
We've extended the HTML client via the vise.relateditems.specs extension point and the data that is rendered in the view/columns displays correctly as long as we don't apply a filter using the filter box in the UI. If we attempt to apply the filter, then we start to see some unexpected results and the result are a little different in 6.5 vs. 6.7.
Looking at the HTTP request that's sent to /ui/list/ex, I see the following JSON payload:
{
"constraintObjectId":"urn:vmomi:ClusterComputeResource:domain-c978:91164109-1fa2-4368-80cb-fe0cf4e1926f",
"queryFilterId":"relatedItemsListFilterId",
"filterParams":[
"com.simplivity.cluster.related.hosts"
],
"requestedProperties":[
"id",
"primaryIconId",
"name",
"labelIds",
"simplivity:virtualControllerName",
"simplivity:state",
"simplivity:clusterName",
"simplivity:datacenterName",
"simplivity:currentVersion",
"simplivity:managementIp",
"simplivity:storageIp",
"simplivity:federationIp",
"simplivity:virtualControllerShutdownStatusString",
"simplivity:upgradeStatus"
],
"dataModels":[
"simplivity:HostSystem"
],
"searchTerm":"jesse",
"searchableProperties":[
"name",
"simplivity:virtualControllerName",
"simplivity:state",
"simplivity:clusterName",
"simplivity:datacenterName",
"simplivity:currentVersion",
"simplivity:managementIp",
"simplivity:storageIp",
"simplivity:federationIp"
],
"take":100,
"skip":0,
"page":1,
"pageSize":100,
"sort":[
{
"field":"simplivity:datacenterName",
"dir":"asc"
}
],
"group":[
],
"listViewId":"com.simplivity.host.list",
"isLiveRefreshRequest":false
}
which looks as I would expected since it includes the necessary data, including the requestedProperties. However, if I set a breakpoint in my DataProviderAdapter, it looks like the QuerySpec.ResourceSpec.PropertySpec list isn't populated from the requestedProperties that are in the payload. In 6.5, the list is empty. In 6.7, it seems like the list of propertySpecs is always a single entry and the entry seems to be the property that we're sorting on. Again, this only happens when we attempt to apply a filter.
Is this behavior expected or is there something wrong with the way in which the QuerySpec is being generated from the HTTP request?
Thank you,
Jesse