Thursday, 07 April 2022
  3 Replies
  1.6K Visits
0
Votes
Undo
  Subscribe
We have many old pre "LAFX-" blocks and I would like to transition to all new blocks. I have deleted folders in LandFX\Blocks so that Land F/X will download the new blocks; however when editing a plant in a current project, the block preview is gone and I now must select a new block for each plant. What is the process to transition to the new blocks without losing the associations for the old blocks in current projects? Should I not bother? Are there any functional differences or is it just the file name?

For example in Blocks\Graphics\Planting\Shrubs\05-Large, all but one of the blocks are named SHRUB-LRG-XXX.DWG, but one is LAFX-SHRUB-LRG-002.DWG. Other than date (2008 vs 2020) SHRUB-LRG-002.DWG appears to be identical to LAFX-SHRUB-LRG-002.DWG - and both show up in the block selector.
Franco,

For the most part we tried to keep the symbols the same, but there were some minor changes.
As for best procedure, you can generate a Plant Schedule, send it to Excel, with the Entire Palette option, and include Symbols. When you do that, it will put the symbol names in the first column. Then you can just use that to try and pick the LAFX- version of the revised symbol.

--J
2 years ago
·
#4648
0
Votes
Undo
Was hoping for a more global solution since this transition would be for our whole team. This is probably transitioning to a feature request now... Could you make it so that the plant manager knows that a "legacy" block is in the drawing and still shows it in the plant info box and in the block selector with the plant name? As it is now we have no way to transition away from the legacy blocks without impacting all current and previous projects.
Franco,

Unfortunately, we don't have the capability to do that. It's been so many years now, we did not archive the old blocks, so we don't have a reference list of the old blocks. The only realistic possibility would be if a block is missing, it could add the LAFX prefix and see if that version is available to download. But we just didn't like the idea of automatically changing a symbol assignment like that for any number of users, who may just be missing a custom block named as such.
There's a stronger possibility of adding this sort of capability to the Portal, but you have Local Data, so our hands are really tied there. But even if you did have Cloud Data, that's a fair amount to engineer for a change that happened ten years ago.

The good news, is that now we have a dedicated Content Team, and all sorts of procedures and backups. So for instance our coming change to the hatch library will learn from this, and will be able to automatically upgrade those symbol assignments after the name change.

--J
  • Page :
  • 1
There are no replies made for this post yet.