Options
  • Locked Locked
  • Replies 1 reply
  • Subscribers 9 subscribers
  • Views 267 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 rule causing strange class behavior?

mturner
I am using mfiles version 20.3.8876.7

I have a metacard rule that sets a property value for 2 specific classes.  Rules and class screen captures are attached.

When uploading a file I choose "test class".  i do not click "create" yet. 

I then change the class to "reports - MPCI".  This class has a property named "insurance line".  the "test class" does not have this property.
The metadata card rule sets the value of "insurance line" to "Federal Crop Insurance (MPCI)".

now, if i change the class back to "test class".  The "insurance line" property now appears on the "test class".  If i click "create", mfiles saves the document with the "insurance line" property.

How do I avoid this behavior?  I dont want my users to have to remove properties that are not supposed to be on a class.

thanks for you help.

15148.zip
  • Hi,
    First of all: how often is that users switch back and forth between classes in real life? Not very often in my experience, but yes, it may occur. If in your situation it is a problem that requires attention, then perhaps you could handle it with an additional rule in Metadata Card Configuration. You should be able to set the default value to Empty and to hide the property in "Test class" or any other class where this property is not relevant (you can set the filter to Class - IsNoneOf - Reports MCPI).
    As you have discovered properties stick with an object once you have put values into them. If that value is removed before the object is saved the first time the property will probably disappear as well if it is not configured to be in that class. So hiding the property is just a precaution.
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.