[BUG]: CustomRequirementRule doesn't appear to work

[AScott-WWF]

I have been trying to configure a Custom requirements rule, so I can target an install against all devices, but will only trigger if an older version is found.

In the Docs (https://msendpointmgr.com/intune-app-factory/#58-modify-the-appjson-file), it states:

CustomRequirementRule
This section is by default left empty, but can be utilized if additional File, Registry, or Script based requirement rules is needed. This section will be further documented in the future.

I had assumed the formatting of the App.json "CustomRequirementRule" section would follow a similar layout as the "DetectionRule" content, but it appears not.
As an example, I have tried adding the following to a "Microsoft ODBC Driver 17 for SQL Server" deployment (via its App.json file) so it will only install the newest ODBC Driver 17 version where an older ODBC Driver 17 version is already installed / detected:

"CustomRequirementRule": [
    {
        "Type": "Registry",
        "DetectionMethod": "VersionComparison",
        "KeyPath": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft ODBC Driver 17 for SQL Server\\CurrentVersion",
        "ValueName": "Version",
        "Operator": "lessThan",
        "Value": "<replaced_by_pipeline>",
        "Check32BitOn64System": "false"
    }
],

This fails to work, however the same content (albeit with a different "Operator" (greaterThanOrEqual)) works fine on the "DetectionRule":

"DetectionRule": [
    {
        "Type": "Registry",
        "DetectionMethod": "VersionComparison",
        "KeyPath": "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft ODBC Driver 17 for SQL Server\\CurrentVersion",
        "ValueName": "Version",
        "Operator": "greaterThanOrEqual",
        "Value": "<replaced_by_pipeline>",
        "Check32BitOn64System": "false"
    }
],

Does CustomRequirementRule work? / Has anyone managed to use this function?

[obuolinis]

I got curious and went to test it :) It does work as you would expect actually. The only caveat is that the current Prepare-AppPackageFolder.ps1 script doesn't have the logic to support any dynamic "replaced_by_pipeline" entries, you can only use static version number. Your code for CustomRequirementRule worked perfectly fine for me as long as i entered a proper version for "Value".

[AScott-WWF]

That confirms my suspicion, that this is a bug, as it means in it's current state you can not use this CustomRequirementRule to 'automatically' create the rule based on the version of the application it is packaging. That's a shame as we have a few apps where we currently target the deployment at all devices, but the Requirement rule prevents it being run where an earlier version does not exist.
Sounds like the current Prepare-AppPackageFolder.ps1 script needs to have the logic added so it can correctly support any dynamic "replaced_by_pipeline" entries.
I'll have a look at that script and see if I can incorporate the necessary changes

[ChristianOe]

@AScott-WWF: You can use a CustomRequirementRuleScript for your need.
You like to update your application if it is installed. Its not necessary to detect if the version is older because this should do your deployment and supersedence.

You can use somethink like this:

If (Get-CimInstance -ClassName Win32_Product | Where-Object {$_.Name -like "Microsoft ODBC Driver 17 for SQL Server*"})
{return $true} else {return $false}

You can use as CustomRequirementRule:
"CustomRequirementRule": [
{
"Type": "Script",
"DetectionMethod": "BooleanOutput",
"ScriptFile": "CustomRequirementRule.ps1",
"ScriptContext": "system",
"Operator": "equal",
"Value": "true",
"RunAs32BitOn64System": "false",
"EnforceSignatureCheck": "false"
}
],

Otherwise anybody should implement this demand in Prepare-AppPackageFolder.ps1.