Filevine does not allow the same document to exist in multiple projects. Additionally, due to the complexity of keeping revisions in sync and the creation of an excess of duplicate records, we do not copy documents to child projects since this bot already creates duplicate data. We want to limit it where possible.
As a result, document fields will be ignored unless a map to a link field has been provided, as explained below:
Using Document Preview Links
To include a document in a synchronized section, please follow these steps:
- Create Link Fields: In your project template, for each File Attachment or Attachment List field, create a helper field of the type “URL” or “URL List,” depending on whether the source field is a list.
- Map the Link Fields to your Document Fields: In the Document Field Mapping List field on the config project, for each document field to be synced, put the field code of the document field followed by the field code of its corresponding link field (the one you created in step 1) in the same field. Each item in the list represents a pair of fields, the document first, followed by the link. Example:
- A "Parent Form Section" is Intake.
- On your Intake section is a File attachment list field with a field selector of intakeDocuments.
- In your Intake section, you have just created a URL list field called intakeDocumentsLinks
- In the Document Field mapping, in one field, you put {{intake.intakeDocuments}} {{intake.intakeDocumentsLinks}}
- Vinbots populate the Links Fields using the DocumentIds: Using the pattern {baseurl}/docwebviewer/view/{documentId}, we populate your link fields with the same preview link native to Filevine.
- Viewing Docs:
- In the parent project, click the Doc attachment field (like usual).
- In the child projects, click the Doc link field.
Comments
0 comments
Please sign in to leave a comment.