In the Sort component, the property dropdown is not getting populated with values.

Hi ​@khn ,
The Sort component only shows properties that are marked as orderable in the Oak index.
If it works on dev/local but not on stage/prod, it means that the actual index definition on stage/prod does not have orderable=true on those properties, even if your code repo looks the same.

In Cloud Service, manual index tweaks in dev/local don’t automatically exist in stage/prod unless they are packaged and deployed and reindexed.

Check below things:
On each environment (Author, /crx/de -> /oak:index):

• Open your custom asset index, for example: /oak:index/your-asset-index/indexRules/dam:Asset/properties/<your-property>
• For each property you expect in the Sort dropdown, verify it has both:

  ordered   = true   (boolean)
  orderable = true   (boolean)
  

• Compare dev vs stage/prod. You’ll see orderable missing or an older index version on stage/prod.

Try below solution:

• Define the index in code, not manually:
  • In your index definition (under /apps/.../oak-index/*.json or .xml), for each sortable property add:

    "properties": {
      "myProp": {
        "name": "jcr:content/metadata/yourProperty",
        "type": "String",
        "ordered": true,
        "orderable": true
      }
    }
    

• Deploy the code to all environments via Cloud Manager (or your CI pipeline).  
• Trigger reindex for that index on Cloud Service:
  • Set "reindex": true (or bump "reindexCount") in the index definition once and redeploy.
  • Wait for reindex to complete.
• Open the Sort component dialog on stage/prod -> Property field. The same properties as dev should now appear.

Thanks,
Amit