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
  • Hi

    1: Currently, it is only possible to use lookup properties (single-select and multi-select) as filter properties in the metadata card configuration.

    2: Do you have that configuration available. I cannot reproduce the error. Here's a sample implementation against the sample vault that adds the Product or service property to the proposal class. Make sure that none of your groups has "Is default = true"

    Condition:

    {
      "Class": 5
    }


    Behavior:


    {
      "Groups": { 
        "Proposal Status": { 
          "Title": "Proposal Status", 
          "IsCollapsible": true, 
          "IsCollapsedByDefault": false, 
          "HasHeader": true, 
          "IsDefault": false 
        },
        "Indexing data": {
          "Title": "Indexing data",
          "IsCollapsible": true, 
          "IsCollapsedByDefault": false, 
          "HasHeader": true, 
          "IsDefault": false
        }
      }, 
      "Properties": { 
        "1096":{ 
          "Group": "Proposal Status"
        },
        "1098": { 
          "Group": "Proposal Status"
        },
        "1004": { 
          "Group": "Indexing data"
        },
        "1034": { 
          "Group": "Indexing data"
        },
        "1040": {
          "IsAdditional": true,
          "IsHidden": false
        }
      } 
    }


    3: I'll forward your feedback to our doc team.

    Mika
Reply
  • Hi

    1: Currently, it is only possible to use lookup properties (single-select and multi-select) as filter properties in the metadata card configuration.

    2: Do you have that configuration available. I cannot reproduce the error. Here's a sample implementation against the sample vault that adds the Product or service property to the proposal class. Make sure that none of your groups has "Is default = true"

    Condition:

    {
      "Class": 5
    }


    Behavior:


    {
      "Groups": { 
        "Proposal Status": { 
          "Title": "Proposal Status", 
          "IsCollapsible": true, 
          "IsCollapsedByDefault": false, 
          "HasHeader": true, 
          "IsDefault": false 
        },
        "Indexing data": {
          "Title": "Indexing data",
          "IsCollapsible": true, 
          "IsCollapsedByDefault": false, 
          "HasHeader": true, 
          "IsDefault": false
        }
      }, 
      "Properties": { 
        "1096":{ 
          "Group": "Proposal Status"
        },
        "1098": { 
          "Group": "Proposal Status"
        },
        "1004": { 
          "Group": "Indexing data"
        },
        "1034": { 
          "Group": "Indexing data"
        },
        "1040": {
          "IsAdditional": true,
          "IsHidden": false
        }
      } 
    }


    3: I'll forward your feedback to our doc team.

    Mika
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.