{"_id":"58ff170b5a5d7a2300615a3c","user":"54870d54f907080b00fc49cd","__v":0,"category":{"_id":"583e9d764ced340f00b05a5c","project":"54870ea47810260b001c36ab","version":"54870ea57810260b001c36ae","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-11-30T09:35:50.177Z","from_sync":false,"order":1,"slug":"more-features","title":"More features"},"githubsync":"","version":{"_id":"54870ea57810260b001c36ae","project":"54870ea47810260b001c36ab","__v":17,"createdAt":"2014-12-09T15:00:53.237Z","releaseDate":"2014-12-09T15:00:53.237Z","categories":["54870ea57810260b001c36af","5487116f7810260b001c36b5","548711797810260b001c36b6","548711807810260b001c36b7","548713127810260b001c36bd","548713247810260b001c36be","548713aa7810260b001c36c0","548713c2f907080b00fc49d5","548713eef907080b00fc49d9","54871a0db3441a1f00f20d78","54871b15b3441a1f00f20d7e","54871cbeb3441a1f00f20d87","548817fac178b40b00aa2eec","558a6dd975eaf50d004e4bf5","558a6e37dbe5b63700f8d1fe","56795d8c07bf6a0d0083ee9e","583e9d764ced340f00b05a5c"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"project":"54870ea47810260b001c36ab","parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-25T09:29:47.895Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":8,"body":"The 'clone' functionality is a key functionality of ArchiSnapper. Lots of architects and contractors like to start from the previous report when creating a new site report, so they see the observations of the previous report and take it from there: edit existing observations, mark observations as solved and add new observations.\n\nHere you can find more info on how this works.\n\n## Category based report vs checklist based report vs cloning\n\nWhen you create a new field report (from the App or online) there are 3 options:\n\n1. **Start from your categories** (also referred to as 'new blank report'). You can manage these categories from [here](https://app3.archisnapper.com/categories?lang=en) in your online account. Note that these categories are applicable for all users and projects. \n2. **Start from checklist**: you can create your own checklists (from [here](https://app3.archisnapper.com/checklists?lang=en)) and use these as a starting point to create new reports. This can be useful for inspections, safety audits, or even [for punch lists](https://archisnapper.readme.io/docs/how-to-manage-punch-lists-using-the-checklist-functionality). [Here](https://archisnapper.readme.io/docs/working-with-checklists) is a help doc with more info on working with checklists.\n3. ** Clone last report**: this means you start from the last report of that project (no matter if it's category based or checklist based) and take it from there. You can delete observations that are not longer applicable, or mark observations as \"OK\", or add new photos/descriptions to them, next to adding new observations to the report.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0eab4d1-Screen_Shot_2017-04-25_at_11.21.52.png\",\n        \"Screen Shot 2017-04-25 at 11.21.52.png\",\n        261,\n        519,\n        \"#969899\"\n      ]\n    }\n  ]\n}\n[/block]\n## Clone settings\nIn the App settings (both on Android and iOS devices) there are clone settings. These settings determine whether the project status, people present, photos and OK items (vs NOK items only) will be copied when cloning a previous report:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f9e92f1-archisnapper_clone_field_report_settings.png\",\n        \"archisnapper_clone_field_report_settings.png\",\n        487,\n        455,\n        \"#e0e1e2\"\n      ]\n    }\n  ]\n}\n[/block]\n## Cloning reports and observation numbering \n\nObservations from previous report will keep their unique number. For example: if you have one report for project X, and this report has one observation with number 1.1. And then you clone this report to generate the second report for this project. The new observations will be numbered 2.1, 2.2, etc but the old observation from report 1 will always keep its number, 1.1. This makes it easy to see from which report every observation origins. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/bce4026-Screen_Shot_2017-04-25_at_11.54.17.png\",\n        \"Screen Shot 2017-04-25 at 11.54.17.png\",\n        709,\n        385,\n        \"#dad9d8\"\n      ]\n    }\n  ]\n}\n[/block]\n## Tip: Popular workflow applied by ArchiSnapper users when using the clone functionality \n\nHere's a workflow that lots of our users apply when cloning the previous report to create a new one: observations that were NOT OK in the last report but that are solved now are marked as OK. In the new report these observations then appear with status OK. But as it makes no sense to keep showing these OK items also in the next reports, they delete the items when creating the next report. \n\nYou can easily delete observation from the App, by tapping on the observation name and then tap 'delete' or by swiping to the left (for iOS users):\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e59c065-Screen_Shot_2017-04-25_at_12.03.58.png\",\n        \"Screen Shot 2017-04-25 at 12.03.58.png\",\n        570,\n        442,\n        \"#989899\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"how-to-clone-your-previous-report","type":"basic","title":"How to clone your previous field report with ArchiSnapper"}

How to clone your previous field report with ArchiSnapper


The 'clone' functionality is a key functionality of ArchiSnapper. Lots of architects and contractors like to start from the previous report when creating a new site report, so they see the observations of the previous report and take it from there: edit existing observations, mark observations as solved and add new observations. Here you can find more info on how this works. ## Category based report vs checklist based report vs cloning When you create a new field report (from the App or online) there are 3 options: 1. **Start from your categories** (also referred to as 'new blank report'). You can manage these categories from [here](https://app3.archisnapper.com/categories?lang=en) in your online account. Note that these categories are applicable for all users and projects. 2. **Start from checklist**: you can create your own checklists (from [here](https://app3.archisnapper.com/checklists?lang=en)) and use these as a starting point to create new reports. This can be useful for inspections, safety audits, or even [for punch lists](https://archisnapper.readme.io/docs/how-to-manage-punch-lists-using-the-checklist-functionality). [Here](https://archisnapper.readme.io/docs/working-with-checklists) is a help doc with more info on working with checklists. 3. ** Clone last report**: this means you start from the last report of that project (no matter if it's category based or checklist based) and take it from there. You can delete observations that are not longer applicable, or mark observations as "OK", or add new photos/descriptions to them, next to adding new observations to the report. [block:image] { "images": [ { "image": [ "https://files.readme.io/0eab4d1-Screen_Shot_2017-04-25_at_11.21.52.png", "Screen Shot 2017-04-25 at 11.21.52.png", 261, 519, "#969899" ] } ] } [/block] ## Clone settings In the App settings (both on Android and iOS devices) there are clone settings. These settings determine whether the project status, people present, photos and OK items (vs NOK items only) will be copied when cloning a previous report: [block:image] { "images": [ { "image": [ "https://files.readme.io/f9e92f1-archisnapper_clone_field_report_settings.png", "archisnapper_clone_field_report_settings.png", 487, 455, "#e0e1e2" ] } ] } [/block] ## Cloning reports and observation numbering Observations from previous report will keep their unique number. For example: if you have one report for project X, and this report has one observation with number 1.1. And then you clone this report to generate the second report for this project. The new observations will be numbered 2.1, 2.2, etc but the old observation from report 1 will always keep its number, 1.1. This makes it easy to see from which report every observation origins. [block:image] { "images": [ { "image": [ "https://files.readme.io/bce4026-Screen_Shot_2017-04-25_at_11.54.17.png", "Screen Shot 2017-04-25 at 11.54.17.png", 709, 385, "#dad9d8" ] } ] } [/block] ## Tip: Popular workflow applied by ArchiSnapper users when using the clone functionality Here's a workflow that lots of our users apply when cloning the previous report to create a new one: observations that were NOT OK in the last report but that are solved now are marked as OK. In the new report these observations then appear with status OK. But as it makes no sense to keep showing these OK items also in the next reports, they delete the items when creating the next report. You can easily delete observation from the App, by tapping on the observation name and then tap 'delete' or by swiping to the left (for iOS users): [block:image] { "images": [ { "image": [ "https://files.readme.io/e59c065-Screen_Shot_2017-04-25_at_12.03.58.png", "Screen Shot 2017-04-25 at 12.03.58.png", 570, 442, "#989899" ] } ] } [/block]