Options
  • Locked Locked
  • Replies 3 replies
  • Subscribers 8 subscribers
  • Views 605 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Metadata Card Configuration: Hide property based on value

Former Member
Former Member
Hi,

1: I'm testing with metadata card configuration.

I'd like to hide a field from the meta data card when there is no value in the field.
Is this even possible?

Condition:
{
    "Properties": {
        "MF.PR.Name": null  (or "")
    }
}


Behaviour:

{
    "Properties": {
        "MF.PR.Name": {
            "IsHidden": true
        } 
    } 
}



2:
on page 16 of "CONFIGURING THE METADATA CARD", there is stated "Properties without groups are always added ABOVE any property groups.".
I noticed that my undefined properties always appear at the bottom, BELOW the last defined group.

3:
In general, The document could use some more practical samples in stead of flat explanation of functions.

Parents

  • 1: This is me making a sad face --> :-\ I would like to see this enhanced, at least with basics as Empty/Null, NotEmpty, etc

    This limitation to lookupID's is not mentioned in the documentation and it doesn't stroke with the documented part where you can use the name of a workflow state as a property condition:

    You can also use workflows and workflow states as property conditions. You may use aliases or IDs for workflows or
    workflow states in the condition:

    {
    "Properties": {
     "38": "Processing job applications",
     "39": "Applicant selected for interview"
     }
    }


    Can you clarify that?


    We are working to add more possibilities to the filters in future releases. In my comment I meant that the filter property data type must be select from list or select from list (multi-select). You can surely use aliases etc. The built-in "Workflow (ID 38)" and "Workflow state (ID 39)" are single-select lookup properties in the database. This is explained in chapter 3.5 in the documentation:

    Note: Currently only SSLU (single-select lookup) and MSLU (multi-select lookup) properties are supported in
    property-based conditions.

    Mika
Reply

  • 1: This is me making a sad face --> :-\ I would like to see this enhanced, at least with basics as Empty/Null, NotEmpty, etc

    This limitation to lookupID's is not mentioned in the documentation and it doesn't stroke with the documented part where you can use the name of a workflow state as a property condition:

    You can also use workflows and workflow states as property conditions. You may use aliases or IDs for workflows or
    workflow states in the condition:

    {
    "Properties": {
     "38": "Processing job applications",
     "39": "Applicant selected for interview"
     }
    }


    Can you clarify that?


    We are working to add more possibilities to the filters in future releases. In my comment I meant that the filter property data type must be select from list or select from list (multi-select). You can surely use aliases etc. The built-in "Workflow (ID 38)" and "Workflow state (ID 39)" are single-select lookup properties in the database. This is explained in chapter 3.5 in the documentation:

    Note: Currently only SSLU (single-select lookup) and MSLU (multi-select lookup) properties are supported in
    property-based conditions.

    Mika
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.