Search the Community
Showing results for tags 'catalog'.
Found 2 results
We ran across an error in the Irrigation Catalog for one specific, albeit very commonly used, irrigation component. Under Outlets, Sprays, Rainbird, R-VAN Series Nozzles, the R-VAN24-360 nozzle does not have the correct Performance data tied to it. Instead of the radius ranging from 19 ft - 24 ft based on varying pressure input (see Screenshot 2 attached), the Vectorworks catalog only displays a range from 16 ft - 18 ft (see Screenshot 1 attached). This is an important fix because this is a common standard manufacturer product within the shipped VW library and cannot be easily edited by users. By not allowing for the full radius, this is disincentivizing this particular, solid performing product. I am completely capable of creating an alternative custom outlet type to correct the issue, but this shouldn't be confused for a permanent fix to this error.
When using the new irrigation tools we are trying to determine the best way to share ONE master catalog. We are a multiple station office and need to be all sharing the same resources. The current 2017 installation puts the default catalog on the local C: drive; therefore, every computer has a locally different (albeit the same content) starting catalog. This catalog is extremely extensive, but does not contain ALL of the equipment necessary that we use on a daily basis. Adding catalog data is very straight forward, but the problem I noticed is when a workgroup individual user needs to add equipment to the catalog. This information is stored in separate .txt files in the user folder, but stored separately from any working folder setup. This means that no one else can access the information created by that user without going to the effort of moving and merging that data with the data in the workgroup library. We have a working library that everyone shares, is there a way to move the Master/Default content to that location and then when ANY user needs to add equipment, they add it to the workgroup location and not their individual user folder? Otherwise it seems we have to go through what could be a troubling copy and paste methodology to store the new catalog information. If this functionality doesn't exist, consider this a wishlist request that should be addressed ASAP to allow for larger offices to control the workflow of sometimes complex irrigation catalog information collectively.