Hi @drooij 

You can try updating the sync rule and include an ‘order_by’ tag.

Then order by a user_def field.

For example, user_def1 will have values of 1,2,3…..

<hierarchy_select return_only_requested_attrs="true" max_rows="50000">
  <primary_table>TASK_STATUS</primary_table>
  <from>
    <table>TASK_STATUS</table>
  </from>
  <attrs>
    <attr>TASK_STATUS.ACTIVE</attr>
    <attr>TASK_STATUS.DESCRIPTION</attr>
    <attr>TASK_STATUS.DESC_MESSAGE_ID</attr>
    <attr>TASK_STATUS.STATUS</attr>
    <attr>TASK_STATUS.TASK_STATUS</attr>
    <attr>TASK_STATUS.IMAGE_ID</attr>
    <attr>TASK_STATUS.USER_DEF1</attr>
  </attrs>
  <where>
    <data_constraint>
      <constraint>
        <left_operand>TASK_STATUS.ACTIVE</left_operand>
        <operator>EQ</operator>
        <right_operand>Y</right_operand>
      </constraint>
    </data_constraint>
  </where>
  <order_by>
    <asc>task_status.user_def1</asc>
  </order_by>
</hierarchy_select>

Let me know if that works.

Cheers!

Hi @Shneor Cheshin unfortunatel that didn’t work. It’s based on the Message Id or Description field on Task Status (code table)

Hi @drooij 

The next best option I can think of is a custom screen for status updates.

Cheers!