With the “Add Document” Action in a Button/Rule: The Document Name field does not seem to allow references, e.g. `Collected Meeting Notes - <%= Entity.Client.Name %> Both forms get interpreted literally: [image] [image] [image] Furthermore, I am unable to open the created document - on ALT-cl…

I’m not sure why Oleg’s suggestion is not working as intended, but here’s a JS-based workaround: <% const fibery = context.getService('fibery'); const x = await fibery.getEntityById(Entity.Type, Entity.Id, ['Client']); const client = x['Client']['Name']; %> <% NAME("Collected Meeting Notes-" + cli…

Automation Rules: Can't reference Rule/Entity fields for defining Document Name

Bugs & Issues

Chr1sG May 30, 2022, 10:19pm 2

See here

1 Like

Topic		Replies	Views
Markdown template in the "name" field of generated documents (automation) Bugs & Issues	5	541	December 7, 2021
Trigger on doc changes not working Get Help automations	23	474	April 15, 2023
Document creation by Automation is Broken Bugs & Issues	2	212	June 2, 2022
New Rules Action: Duplicate and Link a Document Ideas & Features	0	282	May 30, 2022
Make "creation context" available to scripts Automations	8	1072	March 1, 2022

Automation Rules: Can't reference Rule/Entity fields for defining Document Name

Related topics