[David Cutler]

I haven’t tried using multiple profiles yet @Vince – Now you have me worried that I’d loose the information from my custom columns.

That actually brings to mind a somewhat related question – if you have a tool that uses a custom column, but that column isn’t displayed in your markup list, does the program continue to capture that data? Kinda one of those “if a tree falls in the woods and there isn’t anyone there to see it does it make a sound” questions.🙂

[Vince French]

I haven’t lost any information yet @David Cutler .

I’ve also done a load of mark-ups without realising that I was in the wrong profile and when I imported the correct columns all of the information that I needed was there. This however was probably something to do with the same tools being in two different tool sets e.g. oversite areas are in both my foundations and external works profiles.

[Troy DeGroot]

Great conversation guys!

The data should still compile with the markups even if the custom columns are not loaded. If the columns are choice or manually entered, those fields wouldn’t be available. I would test.

If you make sure you open the document for the first time with the correct Profile, the columns will remain in the file.

The Profile will bring the custom columns into fresh documents, however if the document is not “fresh” and already has custom columns, those will be current. The custom columns live in the document.

With all the custom profiles and toolsets I build for customers, you can imagine I have to juggle things all the time. For a best practice, I create a sub-folder for each customer within the default Profile/Toolset folder. This creates a few extra steps when switching from one to another, but it keeps the profile and all the associated toolsets together in one location rather than pilling hundreds of them into the root folder. This also makes it easy to zip and share a profile and all the toolsets.

Also, something I’ve started doing is naming the toolset how I want it to display within the Tool Chest, but when naming the actual btx file I add the customer name in front of the toolset name, this way they all group together, and it’s clear where they belong.

Sorry for the long feedback, several ideas for you guys to chew on. 🤣

[Vince French]

It sounds like you need to do a blog on the subject @troy-degroot !😆

[Troy DeGroot]

You might be right. 😁

[David Cutler]

Lots of good best practices tucked in that response @troy-degroot