sortby incorrectly sorts objid alphabetically not numerically

Modified on 2025-06-10 12:17:11 +0200

sortby=objid sorts alphabetically, eg:

1, 11, 140, 2, 20, 3

However, objid is a number so it should sort numerically: 1, 2, 3, 11, 20, 140

And invalidates the answer here when you have more than 9999 objects: https://helpdesk.paessler.com/en/support/solutions/articles/673-how-can-i-get-a-list-of-the-most-recently-added-devices (e.g. objid 9999 is treated as more recent than objid 10000)

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Alex,

I agree, this sorting does not really make sense. I can confirm that this was already the same in some older PRTG version I have running (17.x) and the sorting is the same, so it seems to be like that for some time now and I'm not sure if this ever really sorted properly. I've added this to an internal list we have about a new PRTG API (no ETA on that). I will also create a bugticket, maybe it can be fixed for the current API as well.

Kind regards,

Erhard

Jan, 2019 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

sortby incorrectly sorts objid alphabetically not numerically

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.