[David Cutler]

I may have been too quick to panic. Poked around looking to see if I had any security settings that need to be adjusted, didn’t find any, but I tried the export again and now it seems to be working… Sigh…🤣

[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.🙂

[David Cutler]

I was running out to a meeting when I discovered this issue and made a quick post to start getting the community engaged. Here is a better explanation.

I have a number of custom tools built with 5 custom columns that I need to export as a .CSV for my workflow shown in the first screenshot below. These tools work great and are the foundation of my workflow.

When I started my takeoff in the customer supplied file I noticed that they also have custom columns setup (kudos to the customer to be using custom columns). The challenge is that while the data from my custom tool is being captured, it is being displayed in other columns as shown in the second screenshot below (Item number “80” shows as Phase, Description of “18” Silt Fence” shows as Floor, Unit of Measure of “LF” shows as Area).

What makes it even more interesting is that my “standard” markups that I apply when I insert my cover sheet populate correctly, but the “Phase” item is not in the standard order as shown in the 3rd screenshot below.

I’m thinking that I can go back to the original file, delete their custom columns and then import mine. Just seems to be an additional step to have to “scrub” someone else’s custom columns to use mine.

[David Cutler]

Made a few minutes to watch the video @Vince . Very impressive setup! Thank you for the shout out as a member of the Brainery.

One quick question with your custom line types – are the widths of your lines also set to scale? If yes, how do you account for different scales on different sheets? If no, do your “Noggin Boards” measure accurately where you appear to be measuring from the edge of the lines?

Now I need to make the time to update my custom tools to keep up!

[David Cutler]

Thank you for putting the time into making the video @Vince. I look forward to checking it out this weekend.

[David Cutler]

@jaredp if you are on LinkedIn check out @Vince (Vince French)’s post “#bluebeam Roofing Take-Off”. Vince has put together some amazing custom tools in Revu that may give you some ideas on how to improve your workflow.

[David Cutler]

Hope that Monday is treating you better than Friday @troy-degroot !

Do you have a backup system in place for when things like this come up? If not, will you be developing one?

[David Cutler]

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

[David Cutler]

Great video @Vince

[David Cutler]

That’s a great suggestion @Vince

Thank you,

Dave

[David Cutler]

Thank you for the suggestion @Vince – in this case they only have a few “Cloud+” markups that I need to maintain. Then again if I flatten them I would have the information, but not have to work around them…

[David Cutler]

Thank you @troy-degroot that did the trick, and wasn’t too painful.

I guess that I will have to add “check for other custom columns/import custom columns if needed” into my workflow.

[David Cutler]

All good points @Vince

Like most endeavors one reaches a point of diminishing returns with the level of detail. If your goal is to develop a detailed parts list for off site cutting Revu is probably not accurate enough. If you’ve goal is to generate a reasonably accurate bill of materials you are definitely there!

Thank you for sharing all of this great information!

[David Cutler]

She just doesn’t understand the life of a Revu addict… 🤣

[David Cutler]

Thank you @troy-degroot for posting the link.