Skip to main content
All CollectionsDataset Tutorials
Dataset vs. Form Template Fields
Dataset vs. Form Template Fields

A help article about best practices with the Dataset and Template Fields

Updated over a week ago

What is the Dataset?

Settings > Dataset
The Dataset allows you to customize the fields available in the Client and Prospect Profile section. Depending on your workflow, you may require additional fields to collect and store specific Client and Prospect information. Within the Dataset you are able to create these fields and organize them to fit your needs.

If your goal for your template is to have it prefill with data from the client profile, you must first create the dataset (field/group/page) and from there you can copy it into the  template from your dataset.  You can pull from the dataset into any template.

Once the client has filled in data in this field on their template, it will now store in the clients profile.

A field in the Dataset

The same field on a client engagement

The field in the Account profile

Template Fields

PreciseFP allows you to fully customize any of our pre-existing templates and also allows you to create your own templates as well.

When you have a template open in the editor you can then add new elements.  

If you add an element directly onto a template that is not a connected element from the dataset then the moment the client enters data into this field, it will remain in this engagement and will not store in the clients profile.

Newly created field in a template

When in the editor for this specific element, you'll see in the connection drop down it shows "none" which means it is not synced to the Dataset which again will mean that it will not store in the clients profile.  (You can click in the drop down for connection to connect it to an element from the dataset)

To view the data the client submitted on a template that contains elements that are not connected to the dataset click on Engagements > All Engagements.

Once you find your engagement click on it, then click on the preview button.  From there you can navigate among the pages to view the data and can even print the engagement.

Once again, since this element only resides on the template and isn't a part of the dataset, in order for me to be able to see what the client input into the element I would need to access the template on the Engagements page and navigate to this page of the templates to see what they input.  

Best Practices

Quite a few of our templates are made up of Datasets so that the data from those is stored in the clients profile thus creating a KYC compliant profile (fact finders) Others, like the Risk Tolerance for example, are not mostly because it's not a good idea to store that data in the profile.  In this case, their answers more than likely will change and we wouldn't want to provide them with a Risk Tolerance that is already pre-filled out.  We want to present it to them blank so that they can really think about where they are at financially. Another example of a template that you may not want to have store in the clients profile are surveys because again, you want it to be blank each time.  

A good rule of thumb when creating new templates or new elements, groups or pages, is to ask if you want this to become part of the clients profile so that when they submit this template I am able to easily access it right within their record vs having to pull up the actual form and navigate through each page of the actual template.  

Also, data imported from an integration partner will store in the client/profile making so that when you engage the client with an integration specific fact finder, it will automatically prefill with data that was imported.

Did this answer your question?