Friday, 07 July 2017
  10 Replies
  2.4K Visits
0
Votes
Undo
  Subscribe
We have multiple preference sets between our offices and I have it on Sacramento's preference set but it's pulling the Irvine detail template when trying to create a new detail. I am able to save it within Sac's detail library but it still looks like Irvine's template.
Accepted Answer
0
Votes
Undo
Well the simplest would be to standardize. There really is not much rationale for having something as simple as a detail callout block be different between offices, especially as things are merging like this.
But you can also pre-define those blocks in the template, so that they are ready to go.

--J
From a blank drawing, you can go into Preferences, select the desired preference set, and then use the Open Template file button to open that detail template file.
After merging preference sets like you guys have done, the target file name probably changed.
So you rename the files as necessary, to match the one the preference set is looking for.

--J
Is there a way to know the name of the detail templates that we're using (Since we merged preference sets)? To make this work we have to copy the other office's detail templates to the local LandFX/Detail folder. It didn't work until we did this. - - This is another reason to tie the LandFX Details and Detail Template folder to the preference set.(not the local install) - Oops. I wasn't going to mention this until after September. - Try to stay cool.
The Detail Template file is already associated with the Preference Set.
However, the filename itself can vary between installations. We opted for a more simplistic file naming, of just DETL-001, incremented up for each preference set installed.
Which just means that after merging preference sets into your one cloud-based installation, it will require some template file cleanup.
The steps would be as I noted previously -- from a blank drawing, cycle through each preference set, and open each template, logging the filename opened for each.
You can then rename/copy/replace as necessary.

It is certainly an intriguing idea to have the template co-located with the detail library. However it seems some users may wish to have multiple preference sets accessing the same detail library, yet using different template files. So the need will still be there to have differently named template files. I think the method we have is still preferable to the other possibilities, of deriving from the preference set name, or using a random key number.

Note that there is a little hidden fix in there -- you can delete all template files from the folder, and leave just DETL-000, which will get copied as necessary for use by all preference sets.

--J
6 years ago
·
#1283
0
Votes
Undo
I've got the template to work now but now the tag circles and bubble callouts are pulling from ours...how does it grab the correct circle and dimension callouts for details?
Katie,

The detail callout and bubble blocks are located at Landfx/Blocks/Graphics/Callouts. You can confirm the location of your Landfx folder from the Preferences screen, "Installation and Server Info" buton.

--J
Jer,

So even if we're using the other office's template it still looks locally for the elements inside of the template? If so, How would you recommend alleviating this situation without affecting other users in the local office? One way would be to tie the detail elements to the same computer (server) name as the detail template is set to (once LandFX allows the detail template to be tied to the preference set by using the computer name and path rather than a mapped drive). Oops. Still we could use a suggestion as to how to deal with this. I can't figure out a clean way to do this, but I'm not the wizard that you are.

Seaweed
Accepted Answer
0
Votes
Undo
Well the simplest would be to standardize. There really is not much rationale for having something as simple as a detail callout block be different between offices, especially as things are merging like this.
But you can also pre-define those blocks in the template, so that they are ready to go.

--J
Yep Jer. As always, you are correct on both accounts. We are going through a standardizing process and we will have to include the block definitions in our templates. You are the Wizard! Thanks again.
By the way, it's easy to dictate standards, but to get buy-in and compliance is another story. If you think that standardizing is simple, you've never participated in a standardization committee.
Haha. That's true sometimes, but I'm not sure how funny it is. As the LA of record, it matters to me.
;) I completely agree. We're bringing four offices together and trying to standardize them. Once that's done, the LandFX program will manage the standards for us.
  • Page :
  • 1
There are no replies made for this post yet.