Monday, 11 July 2016
  2 Replies
  4.3K Visits
0
Votes
Undo
I'm working on an older project that has the spray sprinklers named with S-8H, S-15H, et cetera as the naming convention. I decided to add a 12 Third to the plan. For some reason it is now referencing LAFX-S-12T as the block. I'm cool with that, but not when it doesn't bring in our already defined S-12T block. I understand transitioning to a standard naming convention, but please stop *&%*^(^*%* with our blocks. It may be just a couple of keystrokes for you all, but for my team it is costing us time and actual money fixing things that before were working before you decided to diddle with all the bits.

Edward
8 years ago
·
#628
0
Votes
Undo
Code is good, but this has happened on multiple blocks in a plan. And, coming in a project a couple months later, I generally expect the files to work and not need so much maintenance.

Edward
Edward,

The code in question will rename the existing block in question (S-12T to LAFX-S12T in this case), so it shouldn't be an issue. This is to prevent issues in the future, as some ^%#*+*^% civil may have a block named S-12T in their plan.
If this has somehow caused an issue, then give us a call and we can remote in to see the nature of your custom block situation.

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