Insert Nested Parent Entity values into Document Dynamically

Ideas & Features
1

Is there a way of creating a document that can show Data values from the Entity it is linked to? ie its parent

I would like to lay out the Values on a page differently than the ‘Entity View’ has them layed out. but this would be needed for every entity in the database so creating a document for each one doesnt make sense as there are far to many entities

I would like 1 document layout that could pull data from any Entity it is linked to and display the data in a custom fashion.

Use example.

We have a database of Events and for each event i need to create a single page that shows the crew for the Event this info

  • Loadin date
  • load out date
  • show start date
  • show end date
  • Project manager name/contact email/Phone number
  • Venue
  • Location
  • Crew associated with show and their roles
  • Url link to Box files

Etc etc, the list goes on

thanks

2

AH WAIT! Just edited because I think I got it. Now I see you’re using the default embedded documents. I suggest you ditch it. Use rich text field. It gives the power of a document within the entity itself. Unless there’s a specific reason you’re using it which I’m missing.

You can think of each event entity as that “Document” with all the details. No?

Leaving the old text for the sake of archive:

Hey! I’m a bit confused as to what you need… This seems a bit different to Embedding field values in a doc, as you need all entities in the database to have the same layout. 2 things that could solve it:

  1. Move the fields to bottom and they will be bigger along the page. Instead of smaller in the heading. Use multiple entity views to make it more structured. Get data from other places using formulas and lookups.
  2. If you need to export as pdf and send it, you use PDF templates and then lay it out how you’d like and pull from data.

I’m curious as to how your ideal doc layout looks like. I don’t understand what’s missing from what you described, but maybe I’m missing something.

Thanks!

3

Yes, but with limitations.

A script can certainly create and link a document containing “parent” field values, but the document would be static and would not be automatically updated to reflect the parent’s field values when they change.

In theory, the script could automatically update (re-create) the document whenever some fields are changed in the parent, but that would be somewhat hacky and brittle.

4

What are the drawbacks with the current ability to hide/reorder fields on entity view?
It sounds like these pieces of info are mostly basic fields, with Crew being the only collection field.

5

Thankyou. I never even thought about rich text field embedded in the entity. That could work. I’ll have to do some testing.