Version filter not working

Hi Kent,

Versions must be numerical and in the format of major.minor.patch unless doing an Equal to or Not equal to comparison.

At the moment your version filter will not be working as what you have specified cannot be parsed into this format.

Regards, Jeremy.

We support major.minor.patch.build sorry. The text needs to be in that format e.g. 1.0.0.31110

In order to use a greater/less than operator, both sides of the equation need to be in that format. If you are using the equal or not equal then the format does not matter. So both the version in the filter and the version in the error payloads need to be in this format.

This restriction is because the filtering code is using the .NET version classes for parsing and comparison for greater/less than operators.

Hi Kent,

Sorry for the late reply, I've been discussing with the team a good solution to this problem. The issue will be in the error payloads coming from your app, that if they have a two part version number (384 / 1.4.6.384). These will never get filtered out as it cannot be parsed with our current code.

We've decided we will put in some custom handling for this two part build / version numbering (as it is coming from our provider code so we should support it).

Looking at the filters you have set up to date, the first one "384 / 1.4.6.384" will never work as again you can only specify one part. This is bad UX on our part so we will be providing more help for when you select a greater/less than operator. We will validate the input to ensure it can be parsed.

The second two filters will work, but only if the error payload has a version number with a single part. If the payload version number is like "384 / 1.4.6.384", then no greater/less than filter will be able to match this currently (we're going to fix this too).

We'll be looking into this fix today and will update again when the changes are live.

Hi Kent,

We are currently implementing a solution to the issue and will have it released tomorrow. The solution involves updating the Version filters to include an option to specify if you are targeting a build number (e.g. "123") or a version number (e.g. "1.2.3"). Once the solution is released you will be able to recreate your filters to target the correct values. Thank you for your patience.

Regards, Mitchell.

Hi Kent,

We're still working on the fixes. They shouldn't be far off now but we will update you again when we've deployed the changes.

Thanks.

Hi Kent,

We have just released an update to our version inbound filter to allow you target specifically build numbers or version numbers. When creating a new inbound filter by version you can select either "Version" or "Build number" to indicate how version numbers in your error payloads will be treated. In your case you can create one filter to use "Version" and compare by less than or equals "1.4.6.384" and another filter to use "Build number" and compare by less than or equal to 384. Any version filters created earlier will default to targeting "Version". Let me know if you have anymore questions.

Cheers, Mitchell.