Get properties of an existing object in another metadata card

In an M-Files view of the world you typically would not do this. If you need to view the creator details then you would click on the object in the invoice metadata card and view it separately.

I concede that this is not what users want sometimes, though.

You have a couple of options:

1. You "copy" values from the creator across to the invoice. You could create dummy properties ("Creator cell phone") and use the "simple concatenation of property values" to populate the value from the related object. The problem with this "copy" is maintaining it, though: if the cell phone number changes then the invoice will only be updated if it's modified; the value isn't "live".

2. You write a user interface extension ("UIX") that adds a separate/new tab which is shown when an invoice is selected. This tab could be programmed to display data from the invoice and creator directly. Unfortunately this is not a small amount of code, so it unrealistic for installations that do not have access to software development resources.

Regards,

Craig.

In an M-Files view of the world you typically would not do this. If you need to view the creator details then you would click on the object in the invoice metadata card and view it separately.

I concede that this is not what users want sometimes, though.

You have a couple of options:

1. You "copy" values from the creator across to the invoice. You could create dummy properties ("Creator cell phone") and use the "simple concatenation of property values" to populate the value from the related object. The problem with this "copy" is maintaining it, though: if the cell phone number changes then the invoice will only be updated if it's modified; the value isn't "live".

2. You write a user interface extension ("UIX") that adds a separate/new tab which is shown when an invoice is selected. This tab could be programmed to display data from the invoice and creator directly. Unfortunately this is not a small amount of code, so it unrealistic for installations that do not have access to software development resources.

Regards,

Craig.