Accessing child record history
And, just in case you want to know why being able to see child record history from parent root level history:
Being able to see child date history from parent root level history is useful in a number of ways. It can provide a more complete and accurate picture of the data, make it easier to track changes over time, and help identify patterns or trends that might otherwise be missed.
For example, in a database where child data is linked to a parent record, being able to see the child date history from the parent root level history can provide a more comprehensive view of the data. This can be particularly important when there are multiple child records linked to a single parent record. By viewing the parent root level history, an analyst can quickly and easily see all of the changes that have been made to the child records over time.
In addition, being able to see child date history from parent root level history can make it easier to track changes and identify patterns or trends. For instance, an analyst might notice that a particular type of data is frequently changed or updated within a specific set of child records. This could be an indication that there is an underlying issue that needs to be addressed, such as incorrect data entry or a systemic problem with the data collection process.
Overall, being able to see child date history from parent root level history can provide valuable insights into the data and help improve the accuracy and efficiency of data analysis. By providing a more complete picture of the data and making it easier to track changes over time, this approach can ultimately lead to better outcomes and more informed decision-making.
We first released record history back in November of 2013 (really, it feels like just the other day). Since then, we have been introducing a lot of additional features for Fulcrum. One of these was the repeatable section. This special field type works less like a typical section in Fulcrum and more like an independent app which can be used to capture child records that are linked back to the parent record in Fulcrum.
Until last week, the only way to view the child record history was to export the history and view this data outside of Fulcrum. This was acceptable for some of our users who have integrated Fulcrum into their existing databases; but others wanted to be able to see this information directly inside of Fulcrum.
Users can now view the history of their child data directly from the parent record’s (root level) history page. This will even work with nested child records, aka grandchild records. Now you will find that you are able to drill into any repeatable section and see when the child record was first added to its parent record. You can also drill into that specific child record and see any and all changes made to that record.
You can check out the child record history now in your own account or get a quick demo of it in the video below. Additionally, if you have any feedback you would like to share, feel free to email us at support@fulcrumapp.com, we would love to hear it!
And, just in case you want to know why being able to see child record history from parent root level history:
Being able to see child date history from parent root level history is useful in a number of ways. It can provide a more complete and accurate picture of the data, make it easier to track changes over time, and help identify patterns or trends that might otherwise be missed.
For example, in a database where child data is linked to a parent record, being able to see the child date history from the parent root level history can provide a more comprehensive view of the data. This can be particularly important when there are multiple child records linked to a single parent record. By viewing the parent root level history, an analyst can quickly and easily see all of the changes that have been made to the child records over time.
In addition, being able to see child date history from parent root level history can make it easier to track changes and identify patterns or trends. For instance, an analyst might notice that a particular type of data is frequently changed or updated within a specific set of child records. This could be an indication that there is an underlying issue that needs to be addressed, such as incorrect data entry or a systemic problem with the data collection process.
Overall, being able to see child date history from parent root level history can provide valuable insights into the data and help improve the accuracy and efficiency of data analysis. By providing a more complete picture of the data and making it easier to track changes over time, this approach can ultimately lead to better outcomes and more informed decision-making.