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 - Confused!

So, this is what I am trying to do:

I have a Project Object, which has a property called Client, which is a multi-select look-up from my Client Object.

For my Document Classes, I have a property of Project which obviously is a multi-select lookup of my Project Object.

Now, for Views, grouping etc. I can use an indirect reference to group on Client if required. However, in some circumstances it would be nice to have the Client object referenced directly on the Document.

So, in my test Vault, I added the Client property to a document class. If I then create a new document of that class and reference it to a project, it instantly asks me if I want to auto-fill the Client. Whilst this achieves what I want to a point, I'd rather just have the Client auto-filled.

So, I created a metadata rule (and this is where the confusion starts) and for Objects type of Document, where the Project Field is Not Null, it should set the property Client to the value of Project.Client

I had this working (although I'm beginning to doubt my own sanity) and it was working perfectly. As soon as I chose a Project, my Client property was being updated correctly.

I then exported the Metadata Card config and imported it into my Live Vault. It wouldn't work and the error was related to the dynamic placeholder value (i.e. Project.Client).

So I went back to my test Vault and it was working, and the placeholder (in the configuration screen) looked like this:

{{Project.Client}} (the double curly brackets are correct - this is how it looked).

I then tried to edit this in configuration (in my test Vault) and it then gave an error saying Project couldn't be used as a Placeholder. Now, on either Vault, if I try to set the value as Dynamic and try to enter a Placeholder, the only options I am getting are Client and Owner (Client).

Two issues:

1. I have no idea how it was working or why it isn't working now. Any ideas would be most welcome (and also any ideas why I have so few placeholder options).

2. This seems as though it should be fairly simple to do - but what is the best way? If I reference a project to a document, how do I easily set another property on my document metadata card to be the value of a property on the related Project object?

For number 2, I've looked at the Automatic Filling of Properties document and using the Named Value Manager (which I think will work) - but I think it should be easier than this and I still cannot get my head around how it was working and then not.

Thanks in advance!!
  • a couple of questions to make sure you can copy/move your configuration back and forth between your test vault and your production vault:
    [list type=decimal]
    • Do you use Aliases (the same) in both vaults, and do you use those as reference when defining your configuration (rather than IDs)?

    • Did you add the Client property to your document class in the production vault?

    [/list]
  • 1. I use Aliases wherever possible.

    2. Yes.

    I think I'm missing something in my understanding of placeholders. If instead of trying to populate my Client property (multi-select lookup) I try to populate a text property, then the list of placeholders I have is a substantially bigger list of values I can use. I assume this is due to the type of property it is?