The M-Files Community will be updated on Tuesday, April 2, 2024 at 10:00 AM EST / 2:00 PM GMT and the update is expected to last for several hours. The site will be unavailable during this time.

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

Concatenation of Properties: Using Placeholders versus Aliases

Dear Forum,

When concatenating properties placeholders can be inserted manually or with aliases.

Are there specific situations in which manual OR aliases should or should not be used?

For example are they two different methods of achieving the exact same output? 

Are there any specific benefits or drawbacks associated with using one over the other?

I have already read this --> https://www.m-files.com/user-guide/latest/eng/Automatic_values.html but I couldn't find a further explanation to the above  questions.

Any advice would be great - thanks!

Parents
  • Good question! The end result should be the same with both approaches (using IDs or using aliases), they are just different ways of referring to the vault element. I would say aliases are always preferable since then you can move the same configuration to other vaults which might have different IDs for the property definitions but the aliases would be the same. I cannot think of any situation straight away where IDs would be preferred but perhaps someone else can. 

    For a bit of historic background, it was only possible to use IDs in the placeholders until relatively recently but we added the alias option to make it easier to manage multi-vault environments. Cannot recall the version where this was added right now.

Reply Children
  • agree completely with Joonas, we have used on the beginning only ids especially in all our metadata card rules which often caused that those are failing when vault is migrated. Generally speaking, IDs can get changed in M-Files (from properties, workflows to imported users) so it is generally always better to use aliases.