Search the Community
Showing results for tags 'plants database catalog'.
This is a proposed change to the planting tool to make it faster. I feel like it takes too long and is always too confusing between the styles and the replacing styles, and the number of steps/clicks to finally select the plant you have in mind and move on to the next one. What if I have a planting of 50+ different plants? Is the way around this (other than the illustrated idea in the PDF) is to create a template file with common plants I use, or can they show up in the Resource Manager? Additionally, if I had a spread sheet or text file with the list of plants for a design, how could that be imported and evaluated to produce one instance of each plant in the list? From there I could copy and paste, eyedropper tool... Hoping the illustration gets the idea across!
Until 2019, Plant Catalog updates were also automatically sent to the Plant Database for updates. Now they are two separate features, and now you must either choose the catalog or the database, and only the feature you chose can be automatically updated. In other words: This is how I use to add a new variety. Open a Plant Definition (now called Style), click on Get Plant Data, choose All Plant Data, in the left field with the long list of plant names - start typing the plant - and a list of plant names begins to show up, choose the plant with the closest name you are looking for and that information migrates to your Plant Definition / Style. Now change the name of the old variety to the name of the new variety, click OK. If the automatic update was checked, the PLANT DATABASE app would open and the database would update that plant. You might even get a message saying "waiting on plant database......Do you want to insert a new record for it". This was brilliant because both the data set and the database would be essentially synchronized. Now they are separate. You can export the whole data set to the database, but not just the one new style to the database. Oh and the feature of having photos in the dataset sucks, since none of the photos in your database are in this 2019 plant data set / plant catalog. If the developers at Vectorworks, or if anyone has a workaround, please let me know. Otherwise, Vectorworks PLEASE allow synchronization between the plant data set / plant catalog, and the plant database