SortPriority field (RunnerCatalog)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • betdynamics
    Junior Member
    • Sep 2010
    • 534

    #1

    SortPriority field (RunnerCatalog)

    If there is a non-runner, does the SortPriority field change in the RunnerCatalog?
  • BetfairDeveloperProgram
    Administrator
    • Oct 2008
    • 679

    #2
    Hi betdynamics,

    Yes, the sortPriority field will change for the non-runner (and other runners) in RunnerCatalog.

    The non-runner will be displayed at the bottom of the existing set of runners. e.g. in an original field of 8 runners, a single nonrunner would have sortPriority = 8

    Thanks

    Neil

    Comment

    • betdynamics
      Junior Member
      • Sep 2010
      • 534

      #3
      Thanks.

      Shouldn't the SortPriority therefore be part of the "Runner" type as it is dynamic data [in addition to being part of "RunnerCatalog"]?

      Alistair

      Comment

      • BetfairDeveloperProgram
        Administrator
        • Oct 2008
        • 679

        #4
        Hi Alistair,

        Thanks for your feedback.

        This wasn't as part of the "Runner" type, because it only changes in these circumstances. In US racing non-runners stay in the same order for the sake of consistency. In the majority of markets the sortPriority remains constant throughout the lifetime of a market.

        Let me know if there is a specific case where the lack of the sortPriority in the "Runner" type could cause an issue.

        Thanks

        Neil

        Comment

        • betdynamics
          Junior Member
          • Sep 2010
          • 534

          #5
          Neil

          No worries - I can see that the SortPriority is "less dynamic" so I can always get the revised order from RunnerCatalog if I need to get hold of it.

          Alistair

          Comment

          Working...
          X