Connect with us and enhance your M-Files experience using Unitfly Toolkit for M-Files. Here’s how to get started.
I'm trying to configure Property Operations to update a Related Object metadata card to reference the source object.
Example: On Object A metadata card we have a property that is a value list for Object B. When filling out that property we would like the metadata card on Object B to automatically fill out the property that is pointing back to Object A. This would be similar to Managed Properties in the Compliance Kit.
So far what I have that is kind of working is this.
The issue that I'm having is if I delete out the property on Object A it doesn't deleted out the other property in Object B. This would be if we had a mistake and deleted out that property then we wouldn't want them attached anymore.
Not sure if the Dynamic Value is what's causing the issue. I'm not sure what other value to put in.
Hopefully this kind of makes sense.
First step would be to add filter "Attached Agronomy BOL is not empty" on your first rule.
For the second rule, you need to set Target > Reference as "Attached Agronomy Invoices" and then again use this property in Target > Properties > "Attached Agronomy Invoices"
So the logic for the second rule (if we have Object A and Object B) would be:
"Find an object that has the indirect reference to trigger source".
The rule is then searching for other objects in the vault that are referencing the trigger source "Object A" via the property "Choose Object A" and then on that found object (Object B) remove the value from that same property you used for finding the other object (Choose Object A).
I hope I explained it better this time.
can you please tell me is the "Attached Agronomy BOL" multi-select or just a single value drop-down? And how did you test it?
Firstly, can you please deleted the "Monitored properties" conditions from the rule?
- the easiest way to delete something from the configuration is to right-click on the line and select "Remove Value"
Secondly, can you please create the rules from scratch? If you change a configuration a lot and do not use "Remove Value" some of the older configuration can be saved in the background (in the "Advanced" tab JSON)
If that does not help, the last resort would be to try to debug it using verbose logs 🙂
Multi-select should not mess with the execution. Also, everything from the rules seems fine.
Can you please send me the full configuration of the rules (in JSON format)?
And also, please send me the verbose logs from when you executed the rules and they did not work.
@jwittkopf, since the reversed process would be triggered from the different object, you would need new rules with the same logic for other object.
I would just recommend to restrict rule triggering with monitored properties and search filters as much as possible. To avoid looping.