This document provides information on how to create a cut down Project to help diagnose the issues with your Project
It is highly recommended that a backup be taken of any data that is being used so that it can be restored to its original state in the event of any issues that could occur.
When making a Cut Down Project it is essential a backup is taken to ensure the data can be restored if needed. See How To: Backup a Project.
A cut down project is a project that you create with the aim of just providing the data required to try and resolve the problem.
An example would be a project where a Model wasn’t generating in a project with large amounts of other data being produced such as documentation (Drawings, emails, etc…) that is not needed to try and help resolve the issue.
By creating a cut down project you remove the unnecessary data, giving a more focused project on the issue. Therefore, in this example you would create a group with just the Models and Model Rules captured.
The aim of creating a cut down project is to help yourselves and the people offering you technical support to resolve your problem quicker by only sending them the information that they need to investigate the problem; Hopefully reducing the time it takes to understand and resolve your project.
When working through the problem-solving process sometimes you will find that you need more captured information than you had originally selected and this is okay. Adding captured data to the project one section at a time until you have a project that replicates the problem without having excess Data is the aim of making a Cut Down Project
By breaking down the problem you are eliminating the various possibilities one at a time. This methodical problem solving method should help you, your reseller and us here at DriveWorks to resolve your issue faster.
Making a Cut Down Project
|Knowledge Base Article Ref:||KB17092602|